F. Sebastian (spiff) Grassia

@kwokcb, assumption #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" the...

@ld-kerley , I'd argue that you should not be able to add new nodes to NodeGraph instances, which is why I encouraged thinking about them as instances rather than references......

Good opportunity to say... we anticipate all of the doxygen/developer documentation to be eliminated from the SchemaRegistry in favor of userDoc/userDocBrief, in time. Since solving this problem in a nice...

We're working on it - stay tuned, please!

I'd like more information on 3 and 4, specifically: * Is 3 just saying we stop putting all shaders into a separate scope and instead just inlinging them into each...

So what you are describing for 4 seems like a reasonable fallback behavior, but looking at [standard_surface_brick_procedural.mtlx](https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/resources/Materials/Examples/StandardSurface/standard_surface_brick_procedural.mtlx), I would have assumed that the Material interface would be constructed from all...

Thanks, @1danielcoelho ! We don't yet have a timeline for addressing this, but please advise if this becomes a workflow impediment.

Reality Composer is going beyond what is supported by the USDZ spec, and I believe even if MaterialX “normally” supports movie files as textures, in Storm it is Hydra’s texture...

OK, had a look at your scene. There are two issues, I think. One, as you've noted elsewhere, the Mtlx Time node (or any time/frame substitution) is not supported in...

Hi @ld-kerley , we've been discussing the latest changes, and realizing that since the new data we're adding will potentially affect the network that gets built, it will, for _instanced_...