Symptoms and scope
Use this guide when the returned mesh does not reflect the intended current design, expected production files are absent or a scene export is being confused with merged output. Begin with file identity and intended purpose. Do not assume that the receiver opened the correct revision.
Record which object was reviewed, which file was sent and which file the receiver actually opened. Preserve the earlier package. An unlabelled replacement makes it harder to distinguish a stale output from a different export selection.
Vendor-documented save distinctions
exocad describes merging as creating output meshes saved with a _cad.stl suffix and a .constructionInfo companion in the project directory. Saving a scene records the design state; Export scene to mesh exports visible objects with group selection. Its manual also describes removing merged parts and re-merging when returning to design changes.
These are different operations, not interchangeable evidence that every output is current. The guide does not claim a software bug or guarantee that a particular CAM application reads the companion information. Confirm the intended receiving deliverable and installed controls.
Diagnostic sequence
- Identify the intended task: continue a native scene, inspect selected visible objects or receive merged manufacturing outputs.
- Compare the actual delivered filename and revision with the file the receiver opened.
- Inspect the saved scene state and output list in the documented workflow; note whether changes occurred after output generation.
- Follow current vendor guidance for any authorized re-merging, then identify replacement outputs explicitly.
- Test the intended receiving task and repeat the review affected by changed files before release.
Build an output reconciliation note
| Item | What to record |
|---|---|
| Scene | Saved state identifier and intended revision |
| Merge result | Actual generated output list |
| Export choice | Visible objects or merged deliverable purpose |
| Companion data | Required by the agreed receiving workflow or not |
| Replacement | Exactly which earlier files are superseded |
Illustrative note: “The reviewer inspected scene R06, while the receiver opened output R05. We are reconciling the package; no new design decision has been authorized.” Dates help investigation but should not be treated as the sole approval record.
Limitations and Louie validation
Louie should reproduce scene saving, selected-object export and merged-output regeneration with an authorized practice case in the actual release. Record what each operation creates and verify the intended receiver’s use. Behavior and any recovery are locally unverified.
Do not rename an old output to make it appear current. If the package is reconciled but the discrepancy persists, provide non-patient reproduction details to support. This page does not prescribe manufacturing parameters or treat a completed merge as production approval.
Source notes
Primary documentation checked October 6, 2026. Software details describe the cited product documentation; the handoff frameworks and illustrative examples are original editorial guidance. Confirm current version and account requirements with the publisher.
Prepared by Pristine Dental Design · October 6, 2026. Guidance for professional case communication and review. Actual prescriptions, manufacturer requirements and receiving-team approvals govern design and production.