Quote from psychoboy852 on 26. February 2024, 11:02Hi, I was trying to use QuiltiX to generate some basic mtlx files to use for Houdini. When I saved the file out of QuiltiX, it wouldn't read few nodes in Houdini. I looked at the mtlx file in the editor and noticed that "separate3" was saved as a type "float" but Houdini expected it as type "multioutput". And also the nodes that used outputs of "separate3" namely "absval" and "power" had wrong input-field info. Is this a bug or is this just due to how new all of this is or is it because different DCCs use different naming conventions, although shouldn't they be standardized based on MaterialX spec sheet?
I've attached the files for you to have a look.
Hi, I was trying to use QuiltiX to generate some basic mtlx files to use for Houdini. When I saved the file out of QuiltiX, it wouldn't read few nodes in Houdini. I looked at the mtlx file in the editor and noticed that "separate3" was saved as a type "float" but Houdini expected it as type "multioutput". And also the nodes that used outputs of "separate3" namely "absval" and "power" had wrong input-field info. Is this a bug or is this just due to how new all of this is or is it because different DCCs use different naming conventions, although shouldn't they be standardized based on MaterialX spec sheet?
I've attached the files for you to have a look.
Uploaded files:Quote from RichardF on 6. March 2024, 12:55Sounds like it's the same problem as mentioned here: https://github.com/PrismPipeline/QuiltiX/issues/34
A fix for that is available in a separate branch, but needs a bit more testing before releasing it.
Sounds like it's the same problem as mentioned here: https://github.com/PrismPipeline/QuiltiX/issues/34
A fix for that is available in a separate branch, but needs a bit more testing before releasing it.
