A parks pavilion flickers between visible and hidden in the twin. What authored cause best explains the unexpected visibility?

A parks pavilion that flickers between visible and hidden in the twin is best explained by conflicting visibility opinions across composed layers. One layer may author visibility as inherited or visible while another authors it as invisible; opinions may also vary through time samples or session overrides, making the composed result change as stronger layers, mutes, or variant selections shift. Identify which layer should own the pavilion’s visibility, then remove contradictory weaker or accidental stronger opinions. Too many triangles may stress performance, but they do not inherently toggle a mesh between hidden and shown. A pavilion filename without a .txt extension is unrelated to composed visibility. Custom metadata alone does not replace the visibility attribute and does not always force invisibility. Exam caveat: the stem’s emphasis on unexpected visibility makes conflicting authored opinions the composition-first explanation; do not infer that metadata itself controls visibility. Practical check: inspect the visibility property stack on the pavilion prim, identify contributing layers, mute or edit the offending opinion, and confirm the owning department layer’s strength order. Scrub the twin to verify that the pavilion remains consistently visible or hidden as intended for parks review.