create-proxy

Generate a USD proxy sibling for a high-resolution prim hierarchy using decimated meshes or bounding-box stand-ins, wiring USD purpose tags so Hydra and usdview automatically select the correct representation.

Set up render and proxy purpose swapping by tagging the source prim with the render purpose and the generated proxy sibling with the proxy purpose, optionally authoring a displayPurpose variant set to flip representations without duplicating assets.

Yes, you can use deterministic bounding-box stand-ins by selecting either a single axis-aligned bounding box for the entire hierarchy or an individual AABB per leaf mesh to serve as LOD stand-ins.

Avoid edit target and composition arc conflicts by following pre-flight validation checks for missing meshes, existing proxy collisions at the predictable proxy path, and correct edit-target layering before authoring the proxy geometry.

No, USD proxy generation does not replace the original mesh data; it creates a sibling prim at a predictable path and tags it with the proxy purpose while setting the source to render, keeping both representations available for swapping.