Dental Ortho Staging

Step a treatment through its stages and show what moved. Two ways in, and which one you have decides how the plate behaves. ONE MESH PER STAGE — what aligner planning software exports: drop stage_00 through stage_25 and a visibility channel shows exactly one per frame, so the transport scrubs the plan as it was delivered. Nothing is computed and nothing can drift from the plan. ONE SEGMENTED ARCH, POSED PER STAGE: a transform channel carries a position and rotation per tooth per frame, addressing sub-objects by dotted path, so a single import stages instead of twenty-six copies of the same arch. THE POSES HAVE TO COME FROM SOMEWHERE — this plate does not compute tooth movement, and no plugin here does. They arrive from the treatment-planning export or from an assistant writing the channel into track state. A plate that appeared to plan orthodontics would be the single most dangerous thing in this catalog. STAGING IS DISCRETE. Frames land on authored poses and never between them, the same as the joint channel that drives a robot. Tweening would invent intermediate tooth positions no clinician approved, and on a crowded arch the invented frames are exactly the ones that look like a collision. A channel shorter than the clock holds its last pose. WHAT MOVED, MEASURED: drop the start and the end scan as two meshes and the clearance map paints every vertex of the first by its distance to the second, in millimetres, with the range and the mean in the readout. That is a surface deviation field, not a per-tooth movement table — it tells you where and how far the surface went, not which tooth rotated how many degrees. Do NOT reach for versioncompare here: it matches parts by node NAME and calls "modified" a bounding-box drift, so two scans of one arch come back as one removed plus one added. Measurements are in millimetres, imports keep their own coordinates, and there is no ground grid. Sections cut every mesh at once, tooth labels park at the frame edge with a leader line, and isolate reaches one tooth only on a file that has per-tooth sub-objects. THE COMPARISON PRINTS. A PDF deviation report names the two meshes compared, the sign convention, the minimum, maximum and mean, the contact area and how much of the surface sits outside the budget — and carries the same caveats on the page: a surface deviation field rather than a per-tooth movement table, a contact area that under-reads on a coarse mesh, and no pass or fail anywhere on it, because a threshold here is a display band and not a clinical limit. NOT HERE: any prediction of where a tooth should go, root or bone (an intraoral scan has neither — that is CBCT), and collision checking between adjacent teeth during a move.

Supported file formats: STL, PLY, OBJ, 3MF, GLB, GLTF, STEP, STP, IGES, IGS