I'll grant it's not obvious which is the primary input if you're in compact material mode and it's a pain in the arse that on occasion the primary node is hidden by the UI in non-compact mode. but... The primary input is defined by the subgraph you're connecting to - If when you made your own graph the application overrode…
It seems the main problem is inconsistent "Primary" input . Many material nodes have diffuse as primary and since you don't use it usually in metallic workflow the nodes totally stop to transfer scale factor properly . Still nodes like "base material" that I use a lot actually don't let you use diffuse color input at all…
I'm struggling to understand what you're saying tbh.. But If you mean things don't always connect up right then it'll be naming that causes it. You need to match usage, identifier and name up on input and output sides. It will also split the connections up by group name The extra channels are available so the nodes can…
I am trying to use this "compact material" approach for years and it always turns into non-stop puzzle solving. Isn't it supposed to be a great time saver? Guess the custom made input /output names should be matching perfectly to standard naming system . Nevertheless nodes are misses connection in half cases or do weird…
Yes, I expect them to guess , It's not an AI they have to do for that. Just simple if >> then kind of code . It's not an unsolvable issue, it's just a bad system making user prone to mistakes and having zero indication of that. With all that graph inside of a graph it turns into an utter mess you spent hours to debug. All…
In fact I have already remade once all default nodes into my own, removed all non-metallic kind of channels, set height primary everywhere. Did wrap ,slope blur, bevel etc adding another pair of input /output without damn "exposure", just with a slider. Took me years to weed out all the naming and other small errors to…