Parks renamed fountain folders on disk without updating identifiers, and textures went missing. What should teams restore?
Select an answer to reveal the explanation.
Short Explanation
Renaming folders without updating identifiers orphans fountain textures—restore path and identity hygiene. Shop lighting and unrelated transit defaultPrims will not reconnect textures. Keep identifiers and disk layout in agreement.
Full Explanation
When parks renames fountain folders on disk without updating identifiers, textures go missing because asset identity and path hygiene no longer locate those files. USD references and shader inputs still point at old identifiers or relative locations; renaming directories without a coordinated identifier update orphans textures even though bytes moved successfully. Restoring identity/path hygiene—updating references, URI schemes, or resolver maps—reconnects fountain materials for civic presentation.
Only changing the fountain's display name capitalization updates a UI label, not texture asset paths. Fluorescent lighting in the maintenance shop is a physical facility concern. Adjusting only the defaultPrim on an unrelated transit root cannot repair parks fountain texture identifiers.
Exam caveat: Some pipelines use content-addressed or database-backed identifiers that survive folder renames; if your city uses naked filesystem relatives, renames are hazardous. Treat identity updates as part of any bulk folder migration, not as optional cleanup.
Operational check: After folder renames, run a resolve audit on fountain assets, rewrite identifiers/paths to the new layout, verify textures bind in usdview, and require a paired "rename + repath" change set in parks asset management before merging.