Parks needs a temporary wayfinding displayColor on one plaza bench instance for photos. Which choice keeps the rest of the park's benches shared instances?
Select an answer to reveal the explanation.
Short Explanation
Instance proxies are read-only, so one bench cannot be tinted through its proxy. Deinstance just that bench in a weak override layer and color it there, so every other bench keeps sharing the prototype.
Full Explanation
Plaza benches are shared components: one bench prototype supports many placements. OpenUSD scenegraph instancing does not allow edits through instance proxies or on descendants beneath an instance, so a per-bench color needs that single bench to stop being an instance. Because instanceable is metadata on the instance prim, a stronger layer can set it to false for just that bench, after which displayColor can be authored on its prims. Put both opinions in a clearly named override layer so that when the shoot ends the layer can be muted or removed without touching the published catalog. Editing prototype mesh points to add a UV set misunderstands sharing: prototype geometry is common, so the edit affects every bench that instances it. Converting the plaza pointInstancer into a single merged mesh collapses efficient instance data into unique topology and makes seasonal layout changes expensive. Removing the instanceable bit on the bench component asset deinstances every bench in every park that consumes it, an agency-wide impact for one photo callout. Exam caveat: if the benches are PointInstancer instances instead, per-instance appearance is handled with per-instance primvars rather than deinstancing. Practical check: reopen the plaza stage with the photo layer on and off, confirm only the target bench changes, and confirm the shared bench asset file is untouched in version control.