I use a Creality Otter, and my recurring problem was what happened after scanning. Creality Scan could produce a detailed STL, but the exported mesh was often far too dense to work with comfortably in the geometry editor where I needed to design parts around the scan. I built MeshMill as the bridge between Creality Scan and downstream modeling. Open the exported STL, inspect where the geometry is unnecessarily dense, clean or crop unwanted regions, and reduce the whole mesh or selected areas before continuing the design work. It includes: Shaded, density, wireframe, and vertex displays Polygon selection and additive multi-region selection Selection-only optimization for using different reduction levels on different areas Fast QEM, density-balanced, shape-preserving, and topology-preserving algorithms Original and optimized comparison before applying a pass Undo, redo, measurements, dimensional-drift reporting, and a CLI GPU-accelerated OpenGL handles the interactive viewport, hardware selection, and density visualization. Geometry reduction runs locally in separate native workers. There is no account, telemetry, upload, or cloud processing. MeshMill is GPL-3.0. Windows installer and portable packages are available, with unsigned Linux and macOS preview builds now open for testing. It supports 27 interface and documentation languages. Source and downloads: https://github.com/make-your-own-world-project/MeshMill I’m the developer, and this came directly from my Creality Otter workflow. Feedback from other Creality scanner users would help, especially large exports or geometry that loses important detail during reduction. https://preview.redd.it/pmm23mh99kth1.png?width=1920&format=png&auto=webp&s=10c830de5d763ab6563b10d5a398142ad220e982   submitted by   /u/Zestyclose-Lead4345   to   r/CrealityScanning [link]   [comments]