Hi, MaterialX mix node behaves differently in H20 compared to H19.5. When not-exactly-correct type is connected to "mix" then the node switches the signature to the type of this connection. This doesn't seem right as the mix should not affect the signature no matter what.
this can be fixed by changing the type:
but I do not think the mix should affect the signature at all as this is not what is being passed to the output.
the larger problem is that this breaks all hips created in H19.5 as they load broken in H20 with the mix nodes set to an incorrect type
I think you have a bad mix node. Try dropping down a new one. From your screenshot, the mix input is the wrong type. When it's the right type, float, I don't experience any auto-adapting of the signature.
Upstream, the MaterialX library removed those signature types in the version that H20.0 uses. IIRC, those signatures weren't actually supported/functional for all MaterialX shader targets.
Enivob I think you have a bad mix node. Try dropping down a new one. From your screenshot, the mix input is the wrong type. When it's the right type, float, I don't experience any auto-adapting of the signature.
when the type is right it all works. I know. H19 accepted the bad type and it worked fine, however, H20 is now not accepting it and switching the node to "float" meaning all H19 shaders have to be updated to work in H20 making project migration problematic.
goldleaf Upstream, the MaterialX library removed those signature types in the version that H20.0 uses. IIRC, those signatures weren't actually supported/functional for all MaterialX shader targets.
the "bad" connection in H19 worked fine. I understand that that things change on the material side but in this case it is the houdini node that is changing the signature to the input that should not affect it. the mix attribute has nothing to do with the node signature and should never affect it.
