SHADERed VS ssgl

If you specifically want to learn shader programming then https://shadered.org/ is a lot more practical than Shadertoy.

I recreated this shader in SHADERed, and if you're interested, you can view its implementation and experiment with your own parameter values and textures. The project can be downloaded here.

There's http://shadered.org/ but it's abandoned now.

That’s why I recommend https://shadered.org/ instead for people who want to learn to use shaders in common contexts.

https://github.com/dfranx/SHADERed (useful tool for debugging shader code, has a bit more functionality than doing it in Godot directly)

https://shadered.org/ spent much time on basic editor features like Intellisense and now it seems to be dead. The time would have been better spent fixing/improving the core features like the awesome debugger. Only very late they added a (basic) VSCode integration.

Hi corysama, thankx for the comment, there is some truth to that yes for sure. As in, in games you writes more vertex / pixel or "surface" shader and then geom, compute. But I have to somehow disagree in terms of lighting. Sure this is raymarching so geometry is procedurally made in the shader, whereas in game shader it is passed with polygonal 3d model. But the lighting / colour shading calculation are the same as with polygonal geometry (ndotL for diffuse pow(max(reflect(dot(-ld,no)... for specular, calculating normals on fly in shader, etc...) so in that respect it will help for game dev style of shaders. Also I would argue that a lot of animation technique and vfx technique in raymarching shaders are similar / useful / reusable with polygonal geometry, like yanimation based on clamping sin and doing easing etc. Therefore doing raymarching shaders is good for becoming vfx artist / technical artist I guess. You are right though to point out the difference, that's clear. Good shout about shadered.org as well. Cheers!

BTW: https://shadered.org/

Hi, is there a plugin that supports using SHADERed IDE to write unity shaders? It has a lot of functionalities than a standard editors and I it can save a ton of time for me. Have already searched the google but have not found anything.

It's here. I made a post about it too, there's some details in the comments on how this works.

Here I'm doing GLSL and running it via OpenGL on top of my own helper library (the main branch of the code repo explains it pretty well). For me it's the easiest way to code for a GPU by a wide margin, but I guess that's to be expected. For performance, the most important things here are using shared memory and persistent threads so there are less global reads and especially atomics (I wanted to do a local reduction on the end result but for whatever reason subgroup operations don't work on 64-bit integers and I didn't bother to write it out with shared memory)

Some of it is fine-grained control, some is how it’s nice to be able to treat shaders as separate entities, some is just different preference. But no actual limitation, in fact I built a thing for that on top of OpenGL.

Include is probably your best bet there. Personally I use this system that I made, which borrows the single source programming model from CUDA so that shaders are just reinterpreted C++ code that can sit within the rest of the program. This means I can call the same functions from C++ and the shaders, and includes work just like any other includes.

I also already have a library that gives compile time errors, by having the shaders just be a part of the C++ program :) This would also benefit slightly from having embedded files, as I wouldn't need to do the runtime hacks that are currently in place.

As a side note, you may be interested in this library that someone posted on /r/GraphicsProgramming awhile ago. Haven't used it, but it seems like it might fit in with your general design philosophy.

Because mine is the most faithful reproduction of GLSL I've seen. Almost all features work the same in C++ as they do in shaders -- the notable difference is that you can't pass swizzles by reference, and inout arguments have to be defined with a slightly wonky syntax.

The culmination of my attempts at wrapping OpenGL is ssgl, which foregoes basically all binding and lets you write shaders along C++ with semi-automatic lambda capture. The underlying implementation is filled with dragons, but from personal experience it's just bonkers how much nicer it is to work with compared to any other approach I've used.

I have a library that due to its nature (it defines a domain-specific language within C++) has to define macros for a bunch of words that some standard headers use as variable names. This causes the standard headers to completely break if my library headers are included before them, and the errors are less than intuitive. Is there a simple way to produce a meaningful error (like "library header must be included last") if a standard header is included after the library headers? Googling didn't help much, and at a quick glance standard headers don't appear to contain too many extremely common names that I could #define to static_assert or something. I'm fine with the sensible error being limited to a few of the big standard implementations, so the option of just going through the headers and finding enough such names is doable, but it'd be nice to have a cleaner solution.

Yeah, the state machine aspect does make debugging cumbersome, and it's very easy to forget some option in the wrong setting. But I don't fully agree with "a collection of spells", I think the steps to achieve something are (mostly) pretty straight forward. Though maybe memories go sweeter with time, I haven't written any binding code after making ssgl :-)