Setting up a system of Dynamic Components

Im working with a company here in NC that designs and builds climbing Towers all across the US. Up until now I’ve been doing models containing many components without any attributes.
I believe that I can add attributes to the components we develop and use in our design models such that a take off can be "easily " developed.
My problem: dont have much of a clue how to do this and am looking for a reasonable way to get this done. I’m a self learner and have an in depth Sketchup knowledge. Been using SU since V2!

Do you guys have any suggestions for good resources, books, videos, seminars, etc? Any input would be very appreciated.

My suggestions include

Decide on a common axis, insert point, a line simplification view, making it easy to link objects

Use a version of Mitchel’s place, scale and orientate script, extend this script to pick from your common DC folder, or embed the DCs in a template

Use the instance name for identification, do not use the name attribute in the DC, this will assure uniformity in the model outliner and label, plus the DC label.

Have a system of simplification of the DC. It reduces the file size, protects the result from change or intellectual loss. This is required for label of a parent otherwise the label reports the sub components. The actions once sorted can be done with a script.

Use a standard attribute for layout text, then no need to search for data for each component

Link a table that is in a layout template to each report

A VBA script may be required to transfer the data to a customized takeoff list

You can private message me for more detail and support

Thanks for your response. I have to admit you lost me pretty much after the first paragraph. Kind the inverse of “you had me at hello.”
How do I private message you? Sounds like what I need.
I look foward to your input, etc


Im not the original poster but my dynamic components are become very heavy and are crumbling under their own weights. Much of what you said seems helpful but I dont understand how to apply it.

From what I understand there are four places where there can be a name for the component.

  • Instance
  • Definition
  • Component info > name
  • Dynamic component > Object name (double click top left)

From my experience, there is only the “Object name under dynamic component” that you can reference. The “Component info > name” is only displayed in the component options, no? Its only for the user or the reports? Its purely aesthetical , isnt it?

How? Can you elaborate on it? Provide a simple example?

Once again, what do you mean? At what point? Are you talking about “component info > description”?

That being said I really could use some help with my crumbling under its own weight dynamic components. If you were up for a hangout or something along those lines that would be great!

Thanks for the clarification!

  1. The instance name changes with user input, so a DC can retain a common marker in the outliner, option title box, attribute dialog header, the text label (if one level, simplified) and report under entity name and in layout as well. This does not at first appear to work when you create a component, only after you put a new instance into a file and add a notation. If you use the name attribute or change the attribute title this relationship is broken. Otherwise if the user renames the instance say from Col 1 to Post 3, then the DC updates as well. All the references are consistent.

  2. As code is generally downward, the lower levels of a DC can be changed without causing an error, like unwanted hidden geometry options deleted, parts either outer-shelled or exploded to make a whole. In most cases this greatly reduces the file size after purging. This crippled DC can still be re-activated again by swapping it with its definition. This is based on data being retained in the parent or a level before the simplification. My beams on my warehouse page uses this technique. This is best used where there are many, complex internal copies in the DC as this method of copying is very inefficient, so exploding them all will reduce file size after a purge.
    To do this manually can take time, so a script that follows a coded attribute can do this for you and change some of the options to a benign state as well.

  3. Common attributes in each DC helps with reports and its so with layout, once selected the label tool will continue with that attribute.

Can you share an example of yours, then can see if possible to reduce its weight.

Yes, its in that Thread link, use the link in the original post.

where is the script!! .pls let me know. Thanks