Transit finds an incorrect relationship on instanced platform lights and must clear it without exploding instances. What should they do?
Select an answer to reveal the explanation.
Short Explanation
Bad wiring on shared lights calls for a careful patch, not pulling every fixture off the wall. You can clear the relationship with assembly-stage overrides while keeping instancing intact.
Full Explanation
When transit finds an incorrect relationship on instanced platform lights, clear it through assembly-stage overrides that respect instancing constraints. Relationships on shared light instances can affect lighting links, collection membership, or fixture metadata across a station, so the override should correct the composed result without turning every light into a unique mesh. Duplicating each instanced light and removing the relationship from every copy destroys sharing just to make a relationship edit. Muting all station sublayers only hides the problem temporarily and may remove critical station content; it does not surgically correct the relationship. Replacing UsdLux with camera lights changes the lighting model and avoids, rather than fixes, the relationship issue. Exam caveat: relationships and instancing interact closely, so do not assume a relationship can be cleared without respecting instancing constraints; the appropriate assembly-stage override preserves the intended shared setup. Practical check: identify the incorrect target, apply the override, recompose the station stage, and confirm the lights remain instanced where expected and that lighting links and collections resolve to their intended targets.