Would "bottom-up" design cause resaves to occur? Are we wrong to have a component as the "subassembly"? Such that,
widget
--thingamagig
----whatchamacallit,
would cause "widget" to file often?
Whereas,
subassembly_widget
widget
--thingamagig
----whatchamacallit,
would limit how often widget...
Is there a Save option to save only changed files when doing a Save All? I'd like to not save the unchanged files again and again and would think the Save All command might go faster.
Currently running NX 5.0.6.3.
Thanks,
Atmbob
Behold the mold designers. Yes, I suppose we have even more ways to put in threads that fail than others. That's probably the source of MAylward's rant.
John, maybe one improvement that I'm sure would get MAylward's vote would be once you've selected (or reselected) 144 holes to add a thread...
Yes, that's the solution that I found. I baulked at the "Initialize Project" icon and was afraid I'd have to start anew. But that's not the case.
Thanks for the reply. It gives the method for others atleast.
Bob
Is it possible to add the second part of a family mold after the project has gone through the initialization and subsequent steps, yielded a cavity and core set, and been saved?
Bob
Is there a way to disable the generation of a preview image upon saving an assembly? It takes several seconds every time I do a save. I may wish to invoke it later after the assembly is developed, so that others can benefit from a good preview, but for now I can do without.
Regards,
Bob