QUADIFY
By Anvil Interactive Solutions
Services Our Work Shop The Anvil Store ← Home

Quadify Ultra

Quadify Ultra is the adaptive automation / decision-engine edition. Its defining job is not simply to add another remesher: it analyzes the mesh, compares compatible processing strategies, exposes confidence, and routes unfamiliar assets toward an appropriate workflow.

Ultra vs Pro: Pro 3.0 is the dedicated Asset Compiler / Ship Gate workflow. Ultra is the decision-making and adaptive-routing tier. Choose based on the job you need, not price alone.

Requirements

Ultra requires Blender 5.0 or newer. Some remesh engines use bundled or separately configured binaries; see the relevant algorithm page and the installed package for the exact current release requirements.

The Ultra decision engine

  1. Analyze geometric structure and mesh condition.
  2. Classify the topology problem.
  3. Reject or de-prioritize incompatible methods.
  4. Score viable strategies and expose confidence.
  5. Route toward conversion, reconstruction, local cleanup, or a full-remesh workflow.

Why Ultra exists

Once a retopology product contains several recovery and rebuild methods, the difficult problem becomes deciding which method should be tried first. Ultra is designed to reduce that trial-and-error, especially across mixed sessions containing hard-surface, scan, generated, and organic assets.

Core capabilities

  • Geometry classification and method compatibility analysis
  • Confidence-based routing and manual override
  • Hard-surface recovery strategies
  • QuadriFlow / transfer and voxel-based reconstruction workflows
  • Full Remesh through QuadWild where appropriate
  • Local cleanup for targeted Edit Mode fixes
  • Topology QA and result reporting
  • Batch processing with per-object strategy decisions
  • Optional ML/community-model features in builds that expose them

Important

Ultra's UI and routing logic have evolved across releases. If an older documentation page names a control that is not present in your installed build, use the installed version's panel labels and changelog as authoritative. The stable workflow is: Analyze → choose/route strategy → run → inspect result → try an alternative when confidence or quality is weak.