You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless something is missing from the references example, it doesn't actually copy the reference prim, it just creates an xform. For example, making a cube mesh as the internal target path, the example simply makes xforms.
So generally would be nice to have a copy/duplicate example, and if the best practice is to use instances, than put that next to the references and payloads example.
The text was updated successfully, but these errors were encountered:
The explanation on this variant example sounds like instances or references.
https://docs.omniverse.nvidia.com/dev-guide/latest/programmer_ref/usd/variant-sets/author-variant-data.html
https://docs.omniverse.nvidia.com/dev-guide/latest/programmer_ref/usd/variant-sets/create-variant-set.html
https://openusd.org/docs/Authoring-Variants.html
There is examples for references: https://docs.omniverse.nvidia.com/dev-guide/latest/programmer_ref/usd/references-payloads/add-reference.html
But nothing for instances. Which are said to be A light-weight and less manipulable copy of a prim.
Unless something is missing from the references example, it doesn't actually copy the reference prim, it just creates an xform. For example, making a cube mesh as the internal target path, the example simply makes xforms.
So generally would be nice to have a copy/duplicate example, and if the best practice is to use instances, than put that next to the
references and payloads
example.The text was updated successfully, but these errors were encountered: