Housing unit nested opinions never appear in the assembly stage. What asset-load failure commonly explains that?
Select an answer to reveal the explanation.
Short Explanation
You’re right to start with the reference: if it fails to load, nested opinions from that asset cannot compose into the assembly. A float instead of double for a non-geometry attribute, a building name string in CustomData, or an SVG logo on the website won’t cause that failure. Fix the reference first, then check that the nested opinions appear.
Full Explanation
Housing unit nested opinions that never appear in the assembly stage commonly indicate that a reference failed to load, so nested opinions from that asset never compose. Broken paths, resolver failures, or missing packages can leave the assembly without the unit’s interior opinions—materials, fixtures, and kitchenette extents—even while sibling prims from other successfully loaded references appear. Fixing the reference load restores the nested composition graph for the housing authority twin. Using float instead of double for one non-geometry attribute is a typing nuance; it does not prevent an entire reference arc from loading. CustomData containing a building name string is ordinary metadata, and an SVG logo on the housing authority website is outside the USD stage and irrelevant to reference composition. Exam caveat: a reference can appear to succeed as a prim yet bring in empty contents if its defaultPrim or internal composition is wrong; when nested opinions are wholly absent, still start by checking load and resolve errors. Check payloads too when deferred loading is in use. Practical check: open the assembly stage, inspect unresolved references and asset-resolve errors for the housing unit, repair paths or resolver context, reload, and verify nested opinions appear under the unit root before promoting the assembly to the city twin.