F. Sebastian (spiff) Grassia

If that flies with the #wg-usd-materialx community, it sounds good to me. Looks like you've already begun discussing and that @JGamache-autodesk may add thoughts here, also?

@JGamache-autodesk , I wanted to respond to this: > The way the loader transfers all input parameters to the UsdMaterial is also strange. The UsdShade node, via its SdrShader reference...

I personally like the idea of just improving the behavior unconditionally, but we're also not using MaterialX in production yet, so no archival issues or overrides to worry about. Maybe...

Deciding which approach to take seems to depend on whether we think the MaterialX-USD-integration is mature enough that people are expecting the "archival document" promise of MaterialX to apply to...

Hi @theblackunknown , we would like to consider this for one of the shortly upcoming releases, so yes please, could you resolve the conflicts (which came about from our added...

Yes, @theblackunknown ! There's not enough time in the 25.05 release that we are wrapping up this week, but we have it queued for the release after that - thank...

Those are great points, @jakeanq ! Given our other priorities and roadmap, this is something we might not get to for awhile, but we'd be very interested to look at...

Hi @tymonpitts , what I can share right now is that it is a project we anticipate starting when the work to deboostify our python wrappings completes, which will _likely_...

Apologies for joining the party so late, but my _hope_ would be that the schemas' scoping to UsdUI would (self and explicit) document that we should only be using it...

From my POV, it would be good to keep the scoping tighter for now... there's just some meaty problems to talk through and solve if we start allowing it to...