Skip to main content

Reduce

The Reduce tool decreases the number of triangles in a surface mesh through intelligent decimation algorithms, creating a simplified approximation of the original geometry. This operation is essential for optimizing mesh complexity for visualization, file transfer, and downstream processing.

Overview

Mesh decimation systematically removes vertices and retriangulates the affected regions to reduce overall triangle count while minimizing geometric deviation from the original surface. The tool provides three distinct reduction strategies, each optimizing for different quality criteria:

  • Smart triangle reduction: Preserves topology and overall mesh quality
  • Feature-based triangle reduction: Maintains geometric features and edges
  • Triangle reduction by joining nearby points: Consolidates vertices within a distance threshold

Effective decimation enables:

  • Faster rendering: Reduced triangle counts improve visualization performance
  • Smaller file sizes: Critical for data transfer and storage
  • Downstream processing efficiency: Many operations scale with triangle count
  • Level-of-detail creation: Generate multiple resolution versions of the same model

Accessing the Tool

Navigate to the Surface ribbon tab and locate Reduce in the Edit section. Select one or more surface objects before activating the tool.

Target Specification

Each method supports two ways of specifying the reduction target:

Desired Percentage

Specify the percentage of triangles to remove from the original mesh:

  • 75% reduction: Removes 75% of triangles, keeping 25% of the original count
  • Range: 1% to 95-99% depending on method

This approach is intuitive when you want consistent reduction across multiple surfaces or when absolute triangle counts are less important than relative simplification.

Desired Triangles

Specify the exact target triangle count for the output mesh:

  • Range: 1 to 999,999,999 triangles

This approach is useful when you need precise control over output complexity, such as when targeting specific performance budgets or file size limits.

Reduction Methods

Smart Triangle Reduction

The smart method uses quadric error metrics to identify which edges can be collapsed with minimal impact on surface geometry. This algorithm:

  • Evaluates each edge: Calculates the geometric error that would result from collapsing it
  • Prioritizes low-impact collapses: Removes edges that contribute least to surface shape
  • Preserves topology: Maintains the overall structure and avoids creating holes or inversions

Parameters:

  • Reduction percent (%): Default 75%; range 1-99%
  • Target triangles: Alternative specification for absolute triangle count

Characteristics:

  • Excellent preservation of overall shape
  • Maintains mesh topology (no holes created)
  • Produces well-shaped triangles in output
  • Automatic handling of complex geometry

Best suited for:

  • General-purpose decimation
  • Organic and smooth surfaces
  • Visualization and rendering optimization
  • Creating level-of-detail models

Feature-Based Triangle Reduction

The feature-based method incorporates edge sharpness detection to preserve geometric features during decimation. This approach:

  • Detects feature edges: Identifies edges where adjacent triangles meet at significant angles
  • Constrains decimation: Prevents removal of edges along detected features
  • Preserves geometric character: Maintains the defining edges and corners of the model

Parameters:

  • Feature angle (°): Threshold for feature edge detection; default 30°; range 0-180°
  • Reduction percent (%): Default 75%; range 1-95%
  • Target triangles: Alternative absolute specification

How feature angle works:

The feature angle determines which edges are protected from decimation:

Feature AngleEffect
All edges considered features (minimal reduction)
15-30°Only sharp edges protected
45-60°Moderate edges protected
90-120°Only very sharp corners protected
180°No features protected (maximum reduction)

Lower values protect more edges; higher values allow more aggressive decimation.

Best suited for:

  • Mechanical and CAD models with defined edges
  • Architectural geometry
  • Models where sharp features define the design
  • Mixed geometry with both smooth and sharp regions

Triangle Reduction by Joining Nearby Points

This method consolidates vertices that are within a specified distance of each other, effectively merging nearby points and removing the resulting degenerate triangles. Unlike the other methods, this approach is distance-based rather than count-based:

Parameters:

  • Nearby point distance (mm): Maximum distance for vertex merging; default 1.0 mm

Mechanism:

  1. Identifies vertex pairs within the specified distance
  2. Merges nearby vertices into single points
  3. Removes degenerate triangles (zero area)
  4. Retriangulates as necessary

Characteristics:

  • Result depends on vertex distribution, not target count
  • Effective for meshes with many nearly-coincident vertices
  • Can significantly reduce mesh complexity when vertices are clustered
  • May have minimal effect on well-distributed meshes

Best suited for:

  • Meshes with duplicate or nearly-duplicate vertices
  • Cleaning up Boolean operation results
  • Post-processing CAD imports with tolerance issues
  • Meshes with locally over-refined regions

Practical Guidance

Choosing the Right Method

ScenarioRecommended Method
General simplificationSmart triangle reduction
Mechanical partsFeature-based reduction
Organic/anatomical modelsSmart triangle reduction
Cleaning redundant verticesJoin nearby points
Maximum control over featuresFeature-based with tuned angle
Fastest processingSmart triangle reduction

Reduction Guidelines

The appropriate reduction level depends on your use case:

Use CaseTypical ReductionNotes
Real-time visualization80-95%Prioritize performance
Web/mobile viewing70-90%Balance quality and file size
3D printing0-50%Preserve detail for manufacturing
CAD export20-40%Maintain precision
Archival storage0-20%Preserve maximum detail

Iterative Reduction

For aggressive reduction (>90%), consider iterative approaches:

  1. Apply moderate reduction (50-70%)
  2. Evaluate result quality
  3. Apply additional reduction if needed
  4. Repeat until target is reached

This allows you to identify the threshold where quality becomes unacceptable.

Quality Verification

After decimation, verify the result:

  • Visual inspection for artifacts
  • Measurement comparison with original
  • Check for topology changes (new holes, inverted triangles)
  • Verify feature edges are preserved if required

Use the Diagnostics and Fixes tool to identify any mesh issues introduced by aggressive reduction.

Technical Considerations

Topology Preservation

The smart and feature-based methods preserve mesh topology—they will not create holes in closed surfaces or change the number of disconnected shells. The join nearby points method may alter topology if merged vertices belong to different triangles.

Edge Cases

Certain geometric configurations may limit reduction:

  • Very small surfaces: May not have enough triangles for meaningful reduction
  • Already-minimal meshes: Highly reduced meshes resist further simplification
  • Complex topology: Surfaces with many holes or handles may have reduction limits

Processing Performance

Decimation performance scales with input triangle count:

  • Smart method: O(n log n) typical case
  • Feature-based: Slightly slower due to feature detection
  • Join nearby points: O(n²) worst case; depends on spatial distribution

For very large meshes (millions of triangles), processing may take significant time. Consider processing subsets or using the fast method for preview.

Reversibility

Decimation permanently removes geometric information. Unlike smoothing, which adjusts vertex positions, decimation removes vertices entirely. Always preserve the original mesh when experimenting with reduction settings.

Common Issues and Solutions

IssueLikely CauseSolution
Sharp edges lostUsing smart methodSwitch to feature-based; lower feature angle
Visible facetingExcessive reductionReduce less; accept higher triangle count
Holes in surfaceTopology errorUse lower reduction; check input mesh quality
Minimal reductionToo low feature angleIncrease feature angle
Unexpected resultWrong method for geometry typeTry different method
Slow processingVery large meshProcess in stages; use preview settings first