I'm dealing with a Nodegroup that receives the output of several Texture Map nodes. One of those nodes needs to receive the result of some calculations as vector mapping data.
I could have such calculations dangling at the left side of the involved Texture Map node, connected to its Vector input, but I intend to distribute this material among friends, so, I want something a little simpler and tidier to reduce the chance of mistakes on their part. What I'm doing is including such calculations inside the Nodegroup, too, as a sub-block that doesn't contribute to anything other than this auxiliary output to feed that Texture Map node (the attached image is a simplification. The actual Nodegroup is rather large, complex, and full of inputs).
It does work, and the results are correct.
But I don't know if it is a good idea. That kind of thick orange link looks like some kind of warning (for the life of me I can't find what it means in Blender's manual), and I'm noticing that sometimes I'm having to force a recalculation of the material by tweaking some other input field to make Blender react (I'm on Mac, so, I don't know if it's a Mac issue or a Blender-level one). The alternative is to put the mapping calculations back outside the Nodegroup, but I'd really want to spare my friends the hassle they would mean (they re-use data from a normal map, meaning more links criss-crossing the node tree).
So, my questions are:
- Is this kind of arrangement "legal" or valid?
- Is that thicker orange link a warning of some sort?
(I'm on Blender 3.2.1)