Exploding blocks ABSOLUTELY increases file size. But consider-
The block was only a mechanism to bring your group into the new file. The entities were intended to be individual elements of the new file in the 1st place. There's nothing "majic" about exploding blocks and increasing file sizes.
As to editing blocks in place- yes. I've found ALOT of value in this. AND it allows you to group your objects in a similar manner as groups, without giving up the ability to edit them as needed. The added feature of file size really comes into play when your assembly begins to grow in part count. Now here's where it begins to get pretty cool-
Lets say you build your assembly and its getting a bit complex as your part count increases. Lets say that some of those parts are really sub-assemblies themselves, and so now your part count is really starting to grow. AND lets say that some of those subassemblies are still "growing" themselves...
So- Inserting them as X-refs might take on some interest here, and may be where the value begins to creep in, but I've found it a bit cumbersome to add the extra management layer of X-Refs to my already complex task of creating the assemlbly and managing its growth in the 1st place. So-
I'll insert as hard (unexploded) blocks, those subassemblies and components. I'll GROUP them as appropriate, keep file sizes down (as far as I'm able) by not exploding where possible, GROUP them as operating sub-systems for the assembling and ANIMATING of my assembly, and LET MY DESIGNERS CONTINUE TO WORK on the components and sub-asseblies, as I manage the integrity of the top assembly. I can make internal edits where necessary, my people are working unhindered on their portions, Blocks are nested and managed effectively, and operating sub-systems are GROUPED in the top assembly where appropriate, and this thread is maintained all the way down to the individual component, WHOEVER is working on it, with updates continuing along by REINSERTION, _ONLY_ when aappropriate, and not necessarily at every start up (as with X-Refs) !
The macro's cool, and works as advertised ! I like the one posted just above ! I suppose I should have considered something of the sort some time ago, but you know how it goes- you get into a flow, and sometimes interesting new ideas come along as you progress !
Good luck with your modeling using BOTH Blocks and Groups. They really work together as an effective way to manage the growth of your design assembly, 2D OR 3D.
Sometimes both- I have Engineers who don't do ANY 3D. They LOVE laying out their ideas, grouping and blocking as above, and with the help of a capable design staff, group and block and animate and motion-study, etc. , working out issues as their engineered product progresses, working closely with Design staff, who work back and forth in both directions (Engineer-Designer-Detailer-Designer-Engineer...) in a really dynamic design environment. The integrity of the engineered design is thus maintained, and prototype iteration is kept to an ABSOLUTE minimum, keeping design cycles short, making design-to-market shorter, and increasing quality of the delivered product, thus enhancing comapy revenues, and getting everybody raises in the process !!! Who would have guessed ! Ok, I'm having a little fun with it, but you get my point .
Post back with progress? I think there's a group of us who are interested in how this is going for you, and getting some interesting ideas from each other in the process !
Good luck-
C.Fee
