MOKSHA3D
Internal Reference

Advanced Mesh Diagnostics

Future Engineering Visualisation & Repair Environment

Future on-demand environment for deep mesh inspection, visualisation, repair preview and manufacturing diagnostics. This is not part of the current production workflow.

Development Rule
Automatic first. Interactive second.
Advanced geometry should load only after an explicit user action.
1.

Main Viewer — Diagnostic Overlays

MOKSHA3D
?
Diagnostics
Boundary Edges
124
detected
Non-Manifold Edges
18
detected
Zero-Area Faces
36
detected
Degenerate Faces
52
detected
Sharp Edges (> 60°)
215
detected
Inverted Faces
0
detected
Thin Walls (< 1 mm)
0
detected
Self-Intersections
0
detected
Overhangs (> 45°)
0
detected
Display
Opacity80%
XYZ
Vertices: 1,248,532Faces: 2,497,104Components: 3Units: mm
Engineering Results
Boundary Edges
124 detected
Non-Manifold Edges
18 detected
Zero-Area Faces
36 detected
Degenerate Faces
52 detected
Sharp Edges (> 60°)
215 detected
Selection Info
Type
Non-Manifold Edge
Count
18
Length
42.38 mm
3.

Region Isolation

4.

Measurements & Section

92.45 mm
60.31°
5.

Repair Preview

Repair Tools
□ Close Holes
□ Remove Zero-Area
□ Remove Duplicates
□ Weld Vertices
□ Fix Non-Manifold
□ Fix Orientation
□ Remove Islands
6.

Manufacturing Overlays

Opacity70%
Concept heat map only — future validated manufacturing data

Development Notes

Load on Demand

Do not impact the performance of the standard STL workflow.

Modular Architecture

Each diagnostic overlay should remain an independent module.

Performance First

Large meshes must remain responsive and browser safe.

Accurate by Design

Visualisation must reflect validated numerical results.

Future Ready

New engineering diagnostics should be addable without redesign.

Safe Repairs

Preview all repair operations before changing geometry.

Export & Report

Future support for screenshots and engineering reports.

Current Decision
Reference only. Do not implement yet.

Continue building the validated engineering intelligence first. Advanced geometry visualisation becomes valuable later when real users demonstrate a need to locate, inspect or interact with the reported engineering conditions.

Build → Test → Validate → Measure → Refine.