ShaderScope lets you experiment with shaders in real time while seeing every phase of your render pipeline. Every intermediate pipeline state, off-screen render, and color attachment can be updated instantly, their cameras moved independently, and your shader parameters and values tweaked constantly, all with no build/deploy step. Just click the Recompile button and keep on experimenting.
Watch an overview video to see how ShaderScope worksTo experiment with your shader idea, you can import assets like 3D models and textures into your project and connect them to parameters in your shader code. To write your shaders you can create pipeline states and either build on the starter code that comes with them or replace them with your own shader code and proceed from there.
Once your shader code has the parameters you like, you can connect the 3D models and textures you've imported to them and see the results immediately in that pipeline state's view.
If your shaders have parameters that take numeric values, you can add a numeric shader input control to your project, connect it to your numeric parameters, and use the slider to change the value that is fed to your shader. When you change the slider value, you can see the changes in any relevant pipeline state and render pass in real time; no recompile necessary.
If you have shader parameters whose value should change over time, you can add timer-specific shader parameters and connect them to a timer shader input control. With that control you can set any duration you'd like, and there is a speed control in case you want to experiment with variations to your initial settings.
Render passes can be added as a draw destination for one or more render pipeline states, and can even handle multiple color attachments. These can represent your offscreen renders and your final render. The free version of ShaderScope allows one render pass per project, and the ShaderScope Multiple Render Passes in-app purchase removes that limit and allows as many as you like.
ShaderScope Compute adds support for compute/kernel shaders. As with rendering shaders, you can write your own code, including setting your own parameters, and quickly connect textures (including the off-screen output of a previous render pass), numeric values, and timer-specific values.