ZBrush topology recovery
DCC ZBrush Subdivision Recovery Guide
Direct answer: Use Dynamic Subdivision for reversible preview, convert or duplicate to PolyMesh 3D before destructive topology work, capture Project Details onto compatible geometry, and run Reconstruct Subdiv only when lower levels can be recovered without changing vertex order. Preserve staged tool versions so failed projection or reconstruction can be rolled back.
Dynamic SubdivisionPolyMesh 3DProject DetailsReconstruct Subdiv
1. Duplicate tools before topology recovery
Save an incremented ZTL and duplicate the SubTool before projection, subdivision reconstruction, or conversion. Record ZBrush version, active subdivision level, layers, morph targets, polygroups, UVs, symmetry, and vertex count. Export a neutral reference mesh if recovery is high risk. Recovery operations can alter point order or topology, making layers and targets unusable, so a reversible checkpoint is mandatory before the first button press.
2. Convert primitives at the right moment
PolyMesh 3D creates an editable polygonal tool from a parametric primitive or other non-sculptable source. Confirm primitive dimensions and initialization controls before conversion because those controls no longer drive the result afterward. Rename the new tool immediately. Converting does not create production topology, UVs, or subdivision history; it merely permits polygon editing and sculpt operations. Avoid converting the only copy of a carefully parameterized source.
3. Preview form with dynamic subdivision
Dynamic Subdivision displays smoothing, thickness, and crease behavior without committing permanent subdivision levels. Set SmoothSubdiv, QGrid, crease, and thickness options deliberately, then inspect silhouette and hard borders. Use it for shape evaluation or low-resolution modeling, not as proof that a downstream exporter receives the same mesh. Before baking or delivery, decide whether to apply the preview, recreate equivalent subdivision elsewhere, or export the cage under a documented target policy.
4. Test whether lower levels can be reconstructed
Reconstruct Subdiv works only when current topology plausibly derives from a lower level by regular subdivision. Duplicate the SubTool, move to the lowest available level, and attempt one level at a time. Triangulation, deleted faces, changed point order, hidden insertions, or irregular topology can block reconstruction. Compare silhouette, border layout, and vertex counts after every success. Stop when the recovered cage becomes structurally wrong even if the command still completes.
5. Prepare source and target for projection
Keep the detailed source visible and the retopologized target active. Align scale and position, divide the target gradually, and store a morph target before projecting. Use polygroups or isolated regions to prevent nearby surfaces such as lips, fingers, eyelids, and clothing layers from cross-projecting. Begin with a short distance and increase only where proof shows misses. Projection cannot invent clean correspondence through intersections or large silhouette differences.
6. Project detail in stages
Run Project Details at each subdivision level rather than projecting all high-frequency information onto a coarse target. Inspect silhouette and folds at low levels, then pores and small marks at high levels. Use a controlled blur or smooth pass only on isolated spikes. Check both sides of thin surfaces. If layers are required, project into a named layer when point order remains stable. Save after each accepted stage so one bad high-level pass does not erase earlier work.
7. Work a damaged-history recovery
A creature sculpt has only its highest two levels, and animation needs a manageable cage. On a duplicate, Reconstruct Subdiv restores one valid lower level but the next attempt folds the mouth borders, so recovery stops. A new retopology is subdivided progressively; Project Details transfers silhouette first, then wrinkles with lips and eyelids isolated. Dynamic Subdivision previews the animation cage, while the original sculpt remains the immutable source for comparison.
8. Identify operation-specific artifacts
Exploding polygons during reconstruction indicate incompatible topology, not insufficient memory. Double surfaces or spikes after projection indicate ray hits on nearby parts or excessive distance. Lost sharpness under Dynamic Subdivision points to missing creases or incorrect preview controls. A tool that cannot be sculpted may still be a primitive rather than PolyMesh 3D. Layers grayed out after an operation usually indicate changed point order or subdivision state; return to the checkpoint instead of forcing edits.
9. Build a recovery evidence set
Provide original and recovered ZTL files, version and point counts per level, topology screenshots, projection distances, isolated region list, morph-target status, layer compatibility, and deviation renders. Include wireframes at recovered base level and close-ups of thin or adjacent surfaces. Acceptance requires a usable low cage, no folds or spikes, preserved silhouette within tolerance, deliberate crease behavior, and an archived source from which the result can be repeated.
Multilingual production vocabulary
| zh | en | ja | production meaning |
|---|---|---|---|
| 动态细分 | Dynamic Subdivision | ダイナミックサブディビジョン | non-destructive preview smoothing |
| 多重网格 | PolyMesh 3D | ポリメッシュ3D | editable polygon tool |
| 投影细节 | Project Details | 詳細を投影 | transfer surface relief |
| 细分重建 | Reconstruct Subdiv | サブディビジョン再構築 | recover lower subdivision levels |
DCC ZBrush Subdivision Recovery Guide FAQ
Can Reconstruct Subdiv recover every missing level?
No. It depends on topology that still corresponds to regular subdivision. Triangulation, deleted faces, or changed point order can prevent or corrupt recovery.
Is Dynamic Subdivision real geometry?
It is primarily a non-destructive preview until applied. Export and baking plans must state whether the preview becomes geometry or remains a display aid.
Why does Project Details create spikes?
Projection rays may hit nearby surfaces, use excessive distance, or start from a target with a mismatched silhouette. Isolate regions and project incrementally.
What does Make PolyMesh 3D preserve?
It preserves the current visible primitive shape as editable polygons, but parametric initialization controls no longer drive it and it does not add production topology history.