Replies: 2 comments 2 replies
|
Thanks for offering to contribute. The current STL command deliberately exports the cleaned scene geometry but does not claim printability, so this remains a useful separate track. A production-friendly first PR should stay narrower than automatic repair: add a pure mesh-validation pass on the cloned export scene, report non-manifold edges, degenerate triangles, open boundaries, and final bounds/scale, and cover it with small wall, opening, slab, and intentionally broken fixtures. That gives us measurable acceptance criteria without silently changing architecture. Orientation, unit/scale selection, and opt-in repair can then follow once the validator proves what each transformation fixes. Please avoid mutating the live Three.js scene; the integration point is the prepared export clone used by |
|
This shipped — #701 and #703, both merged 2026-08-21 — and it landed close to the validation-first shape I described above, so it's worth being precise about what you actually get. There's one new action in Settings, Export 3D print files, alongside the unchanged GLB/STL/OBJ exports. It produces 3MF rather than STL: millimetre units, Z-up, split into per-level parts, architectural structure only, at 1:100. 3MF because it carries units and orientation in the file instead of relying on slicer conventions, which removes two of the four problems in your original list outright. On the other two: shells are compiled with Manifold in a worker, and preflight reports disconnected components, winding, thickness, and unsupported geometry. Anything that fails blocks the download and shows you the diagnostic rather than handing you a file that dies in the slicer. That's validation, not automatic repair — the split you and I discussed above. Repair is still a reasonable follow-up now that the validator exists to prove what each transformation fixes. The classic STL export is untouched and still makes no printability claim, which was the honest starting point of your report. Closing as delivered. Two threads left open if you're still interested in contributing, and both are more valuable now that there's a baseline to measure against: opt-in mesh repair, and exposing the print-STL path (it exists internally as a format but isn't surfaced in the UI, since 3MF is the better default). Thanks for the original write-up — the framing of "exports exist but aren't print-ready" is what made this a separate track instead of a tweak. |
Uh oh!
There was an error while loading. Please reload this page.
Feature Request
Problem
While the editor can export STL files, they are not production-ready for 3D printing. Current exports often have issues like:
This limits users who want to create models, 3D print them, and showcase the physical results.
Related Issues
This builds on the broader import/export discussion in #145, but focuses specifically on making exports print-ready.
Solution
Add a dedicated "Export 3D Printable STL" option that generates valid, production-ready STL files with:
Benefits
Interest in Contributing
I'm interested in contributing this feature to the project! I'm opening this discussion to gather feedback and inputs from the maintainers and community on:
Looking forward to your thoughts and guidance on moving this forward!
All reactions