Hi all,
I have a “meta proposal” to update USD object modeling guidelines and seed several other, more specific proposals to follow. It addresses problems people have encountered with how USD encodes important scene “metrics” information (e.g. metersPerUnit, upAxis, …) by proposing a change from layer metadata to prim applied schemas, with rationale.
Here is the PR - feedback preferred in the PR, but OK here, too - thanks!
Thanks Spiff. One question I have is your take on the impact on “internal” references and inherits/specializes. I think it likely has the same risks as sub root references and are commonly used as source scene description with instancing.
Hmmm… I’m not sure I see the same degree of risk for those, since you are (I think?) working “on the same stage”. Sub-root (external, most especially) references are unique (well, for payloads also) in that you’re “piercing the integrity” of a remote asset whose author couldn’t really plan for this kind of use. With internal references and even sub-root inherits, the stuff you are targeting is all on the same stage, so you at least can immediately see what you might be missing. But you’re right you may still wind up missing stuff!