Parks sculptors moved fountain basin points in the civic USD asset. What should they refresh next?
Select an answer to reveal the explanation.
Short Explanation
Basin points moved—refresh the fountain's extent next so bounds follow the sculpt. Street dictionaries and citywide camera focal lengths will not fix a stale basin box. Geometry edits and extents travel as a pair.
Full Explanation
After parks sculptors move fountain basin points in a civic USD asset, they should refresh the fountain mesh extent attributes next. Basin sculpting changes the spatial envelope; without updating extent, twin tools may show outdated selection boxes, mis-frame cameras, or cull the fountain incorrectly during park reviews. Keeping extent synchronized with basin points is standard geometry hygiene for municipal assets.
Refreshing only the fountain's audio metadata addresses sound, not mesh bounds. Updating only the county's street-name dictionary is GIS naming work unrelated to fountain geometry. Changing only the default camera focal length citywide alters viewing optics globally and does not repair a stale basin extent.
Exam caveat: If the fountain is referenced under transforms, world-space visualization depends on both local extent and parent xforms—update local extent first, then verify composed bounds. Time-varying sculpt caches need extents covering animated ranges when applicable.
Operational check: Recompute fountain mesh extent after basin edits, inspect bounds overlays in the parks stage, compare against a surveyed basin footprint, and reject the asset from the civic library until extent and points agree.