When do you think it's appropriate to design several components within one assembly vs. design several different components as their own part files then assemble them into a separate assembly file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Over the years, I've created many assembly projects that I've repeatedly revisited to create new iterations before reaching the "final" product. I've tried both methods of creating assemblies - creating them in one big assembly file, or creating them as separate "part files" which I then import into a separate "assembly file" (SolidWorks style).
I keep going back and forth between which method is better because they both have pros and cons and it annoys me that I haven't settled on one I like more than the other. It bothers me that I don't have a clear blueprint of which one I should go with until I'm several iterations into the project, then I get frustrated that I didn't choose the other method as I'm meticulously changing details that affect the rest of the assembly. "This would have been easier if I started with the other method," I tell myself, then proceed to say the same thing about a different issue when I try the other method next time.
So, I'm curious what the community thinks: When you're designing assemblies, do you prefer creating all your parts in a single file and just adding components for each new part? Or do you prefer to tackle it SolidWorks style - creating brand-new files for each new part, then assembling them together in an assembly later?