UWZ / Developer documentation
Districts & environment content.
Understand UWZ’s permanent HISM district baselines, content organization and extension workflow.
Guide contents · Prelaunch guide · Release information
Baselines & extensions
Keep the starting point stable.
Five baked districts.
A clear extension boundary.
DL_EE_01 through DL_EE_05 are permanent baked HISM district configurations. Preserve their original HISM meshes and visual result.
Organize project additions separately so the original district remains a predictable reference for integration and regression checks.
Content organization
Model states and naming.
- Static mesh state pattern
SM_*_N/SM_*_SD/SM_*_D- LiveMesh pattern
LM_*identifies the interactive asset family.- Scene vehicles
- Included civilian vehicles form static environment content.
- District content
- Architecture, interiors, roads, courtyards, props and vegetation.
State suffixes describe asset naming; runtime state mappings belong to the individual LiveMesh configuration. A complete naming reference will follow the final content registry.
Practical walkthrough / Planning
Extend a district.
- Identify the required district configuration and preserve an unchanged reference.
- Organize additional scene content outside the baked baseline.
- Identify which content needs interaction and which can remain instanced.
- Review the impact and LiveMesh integration contract for interactive additions.
- Compare the original district setup and visual result after integration.