there can some lag due to extra processing, so double component wrapping and using groups is advantageous
with the above example, say copy the main group say 25 times, orbit and move around… now explode the whole selection twice, to destroy the group and the wrapper… so we have 375 copies of the original component, then you will notice the lag as each component (“file”) location and properties is recalculated
It has also be noted in other posts how inefficient the inbuilt copies formula is,
So in it current form a DC is poor use of resources, even with wrapping and grouping,
Even the file size can be an issue. Some have created DCs that are over 1Mb, that hold hidden geometry…
So a method of simplification, to one level components that contain the relevant data is proposed, that can be reinstated if further editing is also required. A manual routine of explosion/outershell of the sub-components can accomplish this. It is possible to create a script to do this, delete hidden parts, outershell. explode,. moreover it can be made to change the DC options to read only.
I don’t know the extent of your use, whether you like to pursue this further, but as I promised before,
I have attached an amended version of your component within the file uploaded below, so if first open this and right click this DC and use saveas to your component folders. Now modify the DC via the options to a different size, Now viewing this in outliner, the first sub is called outershellme, right click this, menu select outershell, right click the highlighted remain “outershell” and explode. exit back into the model. You now have a DC fixed to a set size, you can copy this to build the stage, if you require to edit then right click menu swap with the previous saved one
or drag it in from the folder, or locate through the component broswer.
After purging the file the file size is greatly reduced,( In the home tab of the browser, before the purge you may have noticed the leg components, generally I would have these parts made from groups to avoid having to purge the junk)
test stage.skp (343.1 KB)
let us know (or any one-else) if you are interested in such a workflow