Have an alert when you are using a node that does not work in eevee.
Something that has sometimes happened to me (and I guess to others as well) is to have a node that for some reason does not work. This may be because you are trying to use a cycles node in eevee. It would be great to have an alert that says "This node is not supported in eevee" or something like that when it is placed.
Currently there is one node (of the environment ones) that does have this function.
Well, something like this but for other nodes like: bsdf hair, bsdf ray portal, bsdf toon, bsdf glossy, etc.
4 Comments
I completely agree with this. A node or output that doesn't work in the current renderer should label itself as such. Or at least be categorized into a separate menu listing, or include (Cycles Only) in it's title bar.
Sounds like an improvement to me. However, I don't agree with showing an alert message. These are super annoying, because they always need to be clicked away and can only be shown once so don't help when returning to an already existing node setup.
It would be better if an unsupported node would just show a visual indication on the node (and the above laying groups if available) if it's unsupported. Like coloring the node header background red.
But even better would be to (be able to) prevent this, like @thorn wrote, so next to the above, have blender show some indication on nodes in menus/node search results showing if these are compatible with the renderer you're currently in.
Yes, that's what I meant, that's why I attached the picture of how the small visual indication on the sky node looks like.
Ah okay. So looks like we're on the same page. You literally used the word 'Alert' in your subject line though, that's what I reacted to. An 'Alert' is a term many developers use for popup boxes (an 'alert box') and some languages even has it as exact function name to let one popup. So knowing now you don't mean that it would make sense to change that word of the subject line of your request into something more accurate to prevent confusion.
Thad said; I think that something stronger than just a text inside the node is needed to indicate an incompatible node so we can quickly see a node is invalid for the renderer, also when the node is closed. Something like a big cross over it or the whole node flashing red or something. Because especially when having larger node setups it's impossible to see otherwise. Also when it's active inside a group the group should indicate something is invalid too.