A weaker vendor curb opinion never appears in the composed city twin. What is a likely reason the vendor layer does not take effect?
Select an answer to reveal the explanation.
Short Explanation
If the vendor curb never appears, a stronger local opinion—even an intentional empty blocker—may be winning through composition. A mesh triangle count, unrelated fountain metadata, or lowercase filename does not explain that result. Check the curb’s strength order before blaming the vendor file.
Full Explanation
A weaker vendor curb opinion may fail to appear because a stronger local opinion wins under USD composition strength. A local department layer can take precedence over a vendor package, and an explicit value or an intentional empty or blocker opinion can prevent the weaker vendor curb from contributing even when the vendor file loads cleanly. Inspecting the strength order and identifying blockers explains why a vendor layer is present but ineffective. A curb mesh with more than one hundred triangles does not determine composition strength or hide vendor opinions. Custom metadata on an unrelated fountain does not override curb value resolution across the city twin. Lowercase letters in the vendor filename do not by themselves prevent its opinions from composing when the layer is properly included and not blocked. Exam caveat: Strength order, often summarized as LIVERPS, and empty opinions are subtle: an absent value is not the same as an empty opinion that blocks weaker arcs. Practical check: Inspect the curb property stack, find the winning local layer or empty blocker, remove or weaken an unintended blocker, and confirm that the vendor opinion contributes. Document whether local blockers are intentional municipal overrides or accidental authoring.