UWZ / Developer documentation
Validation & troubleshooting.
Prepare practical UWZ integration checks and learn where to start when an interaction or cleanup path behaves unexpectedly.
Guide contents · Prelaunch guide · Release information
Integration checklist
Validate in your project.
- Confirm the released engine version and package scope.
- Preserve the original baked district setup and visual result.
- Check target selection before tuning visual destruction.
- Check repeated direct hits, overlapping radial impacts and already-promoted targets.
- Confirm effect activation and cleanup happen once per projectile.
- Measure frame time, active debris and concurrent effects under representative loads.
Troubleshooting direction
Isolate the failure.
Then tune the result.
The wrong instance responds.
Inspect world/local-space selection, candidate transforms and instance identity before and after HISM mutation. Visual proximity alone does not prove the selected index is correct.
An impact processes twice.
Trace duplicate collision events and ensure that original instances and their promoted LiveMesh replacements are not both counted.
Effects end too early or remain alive.
Review actor lifetime alongside Niagara completion and decal lifetime. Hiding a visual mesh does not destroy the actor; destroying the actor removes attached components.
Large impacts cause frame spikes.
Capture the test scene, candidates, promotions, active physics actors and concurrent effects. Evaluate correctness and performance separately before changing budgets or batching.
Practical tutorials
A release guide built
around real workflows.
The release guide will pair these architecture notes with package-specific installation, district-extension and child-projectile walkthroughs. Use the architecture pages to evaluate the approach now, and follow the community for release documentation.
Ask an integration questionEmail UWZ support