Bernard Kwok

A customized code generator was "approach 1" I mentioned above and seems the better long term approach. This may or may not be a large undertaking so I was wondering...

@emackey , @jstone-lucasfilm I believe we can close this now. I have finished both import (this issue) and export (distillation) in my own repo here which uses the Autodesk contributed...

I am curious for thoughts on how integrations which do not use code generation parse these and handle interop? For instance, I'm working on the Khronos glTF representation of graphs...

FYI: As mentioned in the TSC sync : The `nodegroup` meta-data tag reliance can be seen [here](https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/source/MaterialXGenShader/ShaderNode.cpp#L302 )for instance in code generation, and would hence "break" if `procedural2d` and `procedural3d`...

Don't really have time to continue pursuing this. Wil close for now.

@ld-kerley , @jstone-lucasfilm, @niklasharrysson : The "fallback" case for unspecified defaults I'm not sure about as it was not discussed in the Slack thread. Add or correct the description as...

There is this related Slack thread started by @hybridherbst which encompasses `geomprop`: https://academysoftwarefdn.slack.com/archives/C02HJH53RN3/p1705501236612989

Hi @Cinifreak, No need to apologize -- I only did a quick look with some possible suggestions :). I will leave some thoughts (not work!) for other shader models since...

Missed this. Put in a fix.

Moved to 1.39. @jstone-lucasfilm : The deprecation logic seems bit inconsistent based on the example you gave. - The C++ has no fallback to call the old method but the...