Hi all.
This hex grid (used for DnD)
is made of many hexagonal cells with a “dot” in the center:
as required for the print service, everything is a hatch (but also the original curves are saved)…
Problem:
Doing “Save small” with Rhino 7 .3dm format create a 1.397 GB file!
If I export the same geometries to .dwg format (and each circle hatch is converted to a closed polyline hatch of 265 hatch points), the dwg file have a size of 5.57 MB … way more acceptable!
grid 7.zip (4.4 MB)
This is the .dwg , zipped, if re-saved to .3dm format takes 21MB
EDIT: grid 7 3dm.zip (4.8 MB)
This is a .3dm without the circular hatches, 5 MB. (you can re-create the hatches from the circles)
Here is the problem ^ circular hatches.
What’s even more interesting (or worse):
- .3dm , 1.4 GB file, opens in a minute!
- .dwg , 5.6 MB file, virtually same content than the .3dm, opens in 20-30 seconds!
Are hatches something similar to meshes? (If so, here some guess, if not, i’m all wrong here)
If so, I suspect the meshing of hatches from the .dwg file (with 0.6 million hatch points from the circles) is taking less time than LOADING the .3dm file (where I expect the rendermesh of the hatch is ready).
So, a lose-lose situation for the .3dm format or a win-win situation for .dwg format 
Maybe setting up so “Save small” actually save only the primitive data for hatches and not the rendermesh?
1.4 GB file I can have 3 whole projects of a full ebike, rendermesh included.
PS funny enough and obviously, the .gh used to generate the grid is 17kB, but a worded description would probably take less than 300 Bytes…