Bernard Kwok

> If you have a nodegraph with inputs, and you want to have different "instances" of this with different input values, how is that any different from defining a proper...

> [@kwokcb](https://github.com/kwokcb), assumption [#2](https://github.com/AcademySoftwareFoundation/MaterialX/issues/2) is interesting.. we do **not** make that restriction in UsdShade, leaving it to downstream consumers (e.g. Hydra) to deal with consequences, i.e. needing to potentially "split"...

Sug as possible first issue ?

Note: Unit test was with a local build. Runtime was downloaded from CI. e.g. sha256:15d2f881a380992512ce6138f8136caee4b27c031600492a382f63997e3c1432 in https://github.com/kwokcb/MaterialX/actions/runs/14821582878. @ld-kerley , I'm not sure if it's you latest changes for the build....

Hi @dbsmythe , I actually logged this a while back and it did behave like this but seems to have regressed? The logic was added for safety for the editor....

This is another port from my editor. For now there is no way to support colorspace transforms via C++ thus images do not consider input space. Let me know what...

This no longer has color background logic. I does do the same traversal discovery required for #2025 though different UI interface.

This has been sitting here for a very long time. Is there interest in adding this in. If not I will close this as I already have this in my...

Note that I wrote the logic for traversal in this PR. I did not hook it up to any hot-keys. The traversal mechanism I put in was via the property...

I wasn't sure if this was going to be tackled but I've added hot-key (left / right arrow to the PR I had).