Does anyone have experience with bloated part or assembly files? Is there a way to reduce them the size?
SW2015 uses a different algorithm for saving the files and does accomplish almost 40% savings in file size. Also in the past 2 years there is a feature which allows for semi-automatic purging of extra info from underused configurations. This can save considerable size. When I first started using SW (1997), a trick for sending a part file to someone was to make the last feature in the tree a cube which enclosed the entire part. You would send the file with instructions to delete the last feature (extruded cube) after the recipient opened it. This does save size.
SolidWorks files store a ton of data. A portion of which is the graphical and blob data. This is what allows you to rotate a model during the open process prior to all of the feature data being loaded. Depending on the complexity of the part, putting a extrude cut on the geometry can have a significant impact on the file size. In many cases though, this "trick" doesn't help too much. It also cannot be used with PDM controlled files.
I agree, with SW2015, the file sizes are indeed smaller. But with the size and speed of current hard drives, are we STILL worried about file sizes?
But with the size and speed of current hard drives, are we STILL worried about file sizes?
Our company mainly has issues emailing the files because of various email provider attachment size limitations.
You can dramatically reduce file size of *.sldprt files by rolling up the feature tree, but the recipient on the other end has to understand to unroll the history.
I'm not seeing why saving a part with an extruded cube as the last feature doesn't work in PDM-controlled files?
Thanks for the replies. We have an automation process with suppression states. Once the right components are selected through equations, we purge the unused models out. The resulting model tends to be very slow as when compared to what it should be. We use Teamcenter as our PLM which is not helpful because lightweight and speedpack can not be reliably used.
I will try out the ideas. Thanks for the new knowledge!
Retrieving data ...