ND Stack
Pro 3.0 workflow: the default target-aware production path is Asset Compiler followed by Ship Gate. This page documents an advanced or manual Pro tool that remains available alongside the compiler.
The ND Stack (non-destructive stack) is for iterative pipelines where you want to preserve a source mesh and tune processing without committing destructive steps too early.
Concept
- Keep a source mesh as the “truth”
- Apply quadify/cleanup as staged operations you can adjust
- Commit only when you’re satisfied
When to use ND
- Scans / messy imports where you may need multiple recovery attempts
- High-value assets that will be iterated over time
- Team workflows where repeatability matters more than speed
Common pitfalls
- Stacking too many aggressive operations at once (hard to debug)
- Changing scale late (breaks density and export expectations)