Warning for incompatible shader nodes ⚠
Nodes should show some sort of indication that they can't be used with the selected render engine. For example, the Shader to RGB node can't be used in Cycles, the Hair shaders can't be used with Eevee, and the Toon shader doesn't work in Eevee. However, there's no way for a user to know that this is the case until they run into unexpected behavior when switching between engines. This is common if Eevee is used for quick material tests and then the final render uses Cycles. Turning the node red when an incompatible render engine is chosen would be very helpful.
2 Comments
Great Idea
@jlampel Yes I think that is a good idea.
For an example I just want to experiment with shader nodes to see how it works. And I cant figure out why it doesnt work for me. Then I search for answer on internet and found out that is the render engine limitation. That is very typical situation for me and it can be time consuming if I want to fast prototyping a shader.
What I suggest is a colour indication on the text background or the text itself of the node when you create it by (shift+A). For example like (Green is Eevee only) and (Orange is Cycle only) node and no colour change for those node who works for both render engines. (Of course colour should be able to customise in the "Preference-Themes"). And maybe the node also have same colour patter when you see them in main board of the shader Editor.