File sizes and tapped holes

[kurt_dup2]

Dear everyone,

having just been introduced to this resource I'm going to try it out to see if I can get some answers to those VW curiosities that 1) curiously make me lie awake at night and 2) those that could seriously undermine a current project to turn our entire manufacturing operation over from 2D to 3D.

Second things first - and I am cuious to figure out why we are generating such large file sizes when modelling some of our component parts that we have drilled tapped holes in. We are getting some file sizes as big as 30MB for a part with, oooh, 15 M3 tapped holes in and I'm concerned by some of the other posts that I've seen here that when we build our sub-assembly and then top-level assemblies from parts like this we are going to end up with massive files.

Any comments regarding

A) putting a tapped hole into a block of metal (we tried a number of different ways but found that subtracting a tapped shaft was the most reliable.)

B) how to yield reasonable file sizes when a number of such holes in A) are put into a component

C) guidelines on the size of files to expect when you xref a number of component files to build a sub-assembly build.

Any thoughts from those more experienced would be most helpful.

Cheers !!

[Bart Rammeloo]

About (B): use the command "make generic solid" (or something like that) to remove the construction history from your objects. I had a wheel rim with a file size of 11MB. After stripping the history it was 2 MB. Of course, after that you can't use the history tree anymore to modify your object.

Cheers,

BaRa