Thank you for your feedback and for raising this important point about mesh data management within the project. We understand your frustration, and we want to clarify the current design philosophy and assure you that your data is not lost.
This behavior is not a bug, but a specific design choice made to optimize performance and workflow efficiency for the majority of our users. Here’s a breakdown of the reasoning and the solutions available to you:
1. The Rationale: Performance and Project Integrity
-
Performance Optimization: High-resolution meshes can be extremely large files. Keeping them loaded in the active project memory at all times would significantly slow down the software, consume vast amounts of RAM, and make handling complex projects with multiple scans very cumbersome.
-
Streamlined Workflow: The primary workflow is designed around processing the scan data (the point cloud) to generate a mesh, and then immediately exporting that mesh for its intended use (e.g., in a CAD program, for 3D printing, or for archival). By not automatically saving the mesh internally, we keep the project file lean and fast.
2. How to Preserve Your Mesh Data
While the mesh isn’t stored within the project file itself, we provide rich and flexible options to export and save your work at every stage. You can easily preserve your generated mesh by exporting it to a standard, universally recognized file format.
The EXStar hub software provide you with two ways:
1.Click “export the scan” at the right side of the “In progress” page, you’ll see the “save mesh locally”, you can choose to save the mesh into stl/obj/ply format onto your local computer, we suggest you create a file that is specialized for saving meshed data so you can quickly find them when needed.
2.Below the icon of the “export the scan”, you can find the access to export the meshed data onto SKetchfab or Shining3D digital cloud, you can also choose to manage your meshed data in these two systems.
We genuinely appreciate you highlighting that this “in-project” mesh saving is a feature you rely on. While the current system is designed for optimal performance, we are always listening to user feedback to improve the software.
We will definitely forward your strong request for an optional way to keep the mesh within the project tree to our development team for serious consideration in future planning.
In the meantime, we recommend using the export function immediately after meshing to secure your data. This ensures you have a persistent copy without affecting the performance of your ongoing project.
Thank you for your passion and for helping us make our product better. Please don’t hesitate to reach out if you have any other questions or suggestions.