Emergency management wants temporary barricade geometry materialized for Hydra during drills without shipping full mesh assets. Which customization fits?
Select an answer to reveal the explanation.
Short Explanation
Barricades for a drill are pop-up tents, not permanent buildings. A SceneIndex plug-in can materialize that temporary geometry straight into Hydra when you need it.
Full Explanation
Emergency-management drills often need barricade geometry visible in Hydra without shipping full mesh assets in the published twin package. A SceneIndex plug-in can materialize temporary barricade prims for the imaging pipeline during the drill window, then omit them when the plug-in is inactive. That matches temporary civic logistics: pop-up control measures for an exercise, not permanent street furniture committed to every layer.
Deleting KindRegistry before each drill does not create barricades; it breaks kind-based classification and tooling assumptions across the municipal stage. Storing barricade meshes only as USDA comments never yields renderable Hydra prims—comments are documentation, not geometry. Forcing barricades into UsdGeomCamera types misuses camera schemas so Hydra treats them as views rather than obstacle meshes, defeating both visualization and any spatial queries that expect geometry.
Exam caveat: Temporary SceneIndex geometry must not be mistaken for authoritative as-built content in after-action exports; separate drill overlays from the legal digital twin record.
Operational check: Run the drill with the SceneIndex enabled and confirm barricades appear in Hydra without additional mesh files in the package; deactivate the plug-in and confirm barricades disappear while the underlying emergency-management stage remains intact and publishable.