Light Mesh Class
Kai Knospe
we would like to have a lighter mesh class for 3d viewing/measurements.
On our smaller products we get a memory usage around 4GB on an assembly where jt2go just took 900MB, on a large product it is 13GB to 4GB. Seems jt2go is much more effective on memory handling with meshes
1
Comments
Hi Kai,
Once the entity is on screen you can easily empty Mesh.Vertices, Triangles, Normals and Edges arrays to save memory. As a consequence some features will lead to a crash. Without vertices you cannot zoomfit, Without triangles you cannot do geometric selection, etc.
Alberto,
the request was a light mesh class without all overhead existing, not to crash the program while using...still wondering whats happening here...
Kai
Try the Mesh.LightWeight= true flag + empty Normals and Edges array once the Mesh is on screen.
this is not solving my issue but i give up...
Kai, in this way you save memory and maintain all the functionalities. Why are you giving up?
Another option is the no-frills FastMesh we are implementing for v2021, floats instead of double will cut the memory needs in half.
Alberto, with meshlight on we loose possibility to select edges, needed for doing measurements.
the new mesh you are talking about might be an option, but we do not know much about it. what would be the resulting mem usage with the full product we provided to you?
Kai, are you doing measurements on vertices or edges? Normally, vertices.
Alberto, we get the triangle close to the mouse, find a sharp edge close to the mouse and use this to determine if it is part of a circle (edges surrounding current one could form a circle by three points with same diameter), a curve or a straight line. So we need edges and vertices...and to determine sharp edge also the normals.
we need to recover base geometry even if we have meshes
Kai, with an additional effort, you can do this even without edges. FastMesh will not have edges as well.
Alberto, can you describe this more in detail? also sent you a video on how the measure looks like
You need an additional data structure to navigate the mesh. For example, unique triangle sides connected to unique vertices. With this data structure, you could easily get the edges on the fly without relying on our edges. We do this for all meshes, maybe you could do it only for the ones involved in measuring and trash everything when you close the measuring command.
...but i planned to save space not dispose your edges and creating mine myself...
Please sign in to leave a comment.