I’m new to DCs, and looking for some “best practices” suggestions. Are there any reasons I should always use sub-components instead of groups within my parent DC? I’m starting off with a simple base cabinet, that I can resize (the width only, i.e. scale on the X-axis) without the side panels changing thickness. So I’ll have side panels, top and bottom panels, toe kicks, stretchers, etc. within the DC. Should those be groups or components?
You can use groups safely at the lowest level, however groups holding DC groups causes problems, unless they are made unique on copying.
If you are using OpenCutList, then for “L” shapes and other compound panels, then groups for each lower part is essential as they will not be read as part of the takeoff.
I recommend using solids for these as one can outershell or union when required.
If using other reports or native one, then best to stick to Components and clean the file when required
Note:
Eneroth’s “deep make unique” is best used straight after copying if you want to build on existing DCs, this is to avoid reuse of definitions that will default to their first loading. (see other posts)
What Philip said. Really it’s in the name, Dynamic Components. I don’t use groups at all.
Dynamic Components work with groups and components. However, copying a sub-element inside a Dynamic Component can lead to inconsistencies if that component is subsequently duplicated… (duplicated sub-group work if the DC is unique…)
The problem with duplicated components is their proliferation within the model. You also cannot choose to constrain the handles using the Scale tool if it is a group… which is inconsistent.
So the solution is to use groups, and components when duplication or deformation is involved.
It’s not a major issue—you just need to adopt good habits—but Dynamic Components haven’t been improved since they were first introduced.