You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugging shaders is notoriously difficult and the common advice is to use colors to debug. This isn't super helpful if you're a beginner, stuck getting your first shader to even run at all.
I came across this plugin that offers shader debugging, but it requires using a file type I've never heard of (.sprj), seems to be proprietary. I think adding breakpoint-debugging to the shader-toy extension could really help make it stand apart from the shadertoy website.
The text was updated successfully, but these errors were encountered:
This is way out of the scope of this extension. It runs simple a simple pipeline in a webview using WebGL 2.0 and SHADERed uses a proper full pipeline. It's a complicated piece of software made for complicated work. If you need that kind of power you are probably better off using the dedicated plugin for it.
Debugging shaders is notoriously difficult and the common advice is to use colors to debug. This isn't super helpful if you're a beginner, stuck getting your first shader to even run at all.
I came across this plugin that offers shader debugging, but it requires using a file type I've never heard of (.sprj), seems to be proprietary. I think adding breakpoint-debugging to the shader-toy extension could really help make it stand apart from the shadertoy website.
The text was updated successfully, but these errors were encountered: