Hi

Best to make the rest of the assembly a function of the rotx, take a variable through the nested components
Wrap the component within another before changing its orientation so as to protect your original axis references
Cheers
Philip

try this

I dragged it directly into sketch-up, as one should with dynamic components.

can't see a problem....what's broken?

Hi
try for Roof Z

=if(FloorPart!Copies>0,int(FloorPart!Copies)*300,0)+300

although copies reads 0, its actual value is different, ie 2000/3000-1 = -0.333333, not 0 as shown, therefore need to make integer and protect against negative

also make sure of the position of the roof component axis (right click to place whilst edit) to achieve desired outcome
cheers
Philip

Hi

Can consider this as part of solution, Three holes, rebate sides and some hidden lines plus outline

For a stop housing one need only front and one side hole, the filled end can be added to the rebate sides.
Note metric

Cheers
Philip

rebate

Stopped housing

added door division for longer cabinets, dynamic openings...swing on side only.. try mirror door as part of visible/invisible maybe solution?

added some dynamic attributes

Hi Gert-Jan

My method is to place the groups in the desired locations, then right click each one and change the axis so that I can locate a common point. Then figure out the formulas, copy the common ones through.

I updated your component to suit, also added variables to cover the width and height without directly exposing lenY, lenZ this avoids the blanks between option changes.

Cheers
Philip

base2.skp

=copy*(Window!LenZ/(Copies+1))+1/2

Try =Window!LenZ/(Copies+1) + if(copy>0,(copy-1)*(Window!LenZ/(Copies+1)),0)+1/2

the first distance + copy less one * distance + 1/2

the if statement to make zero if copy = 0, otherwise copy-1 would be -1

However this places the first and second instance @ the same position. So probably better to reduce the copies number

ie for Copies: = window!number-1
exact syn tact would be whatever you choose for the variable "window!number"

then lenZ= Window!LenZ/(Copies+2) + copy*(Window!LenZ/(Copies+2) + 1/2

Hope this helps
Philip

Hi
How about moving the position of the first instance and do one less copy.

Hi
Can set up a 2D shape with a cutting plane, Place one top, one bottom, plus a rim, refer to my DC,s @ pcmoor in the warehouse (plate with holes, cylinder / column)

It is also possible to have multiple cutters that activate on exploding the parent, leaving the children and grand kids etc, refer to the multi-cut wall opening

Philip

Hi

If you explode the door component parent, the invisible options would be destroyed leaving the chosen visible door and its attributes. this would help reduce the file size and rendering.

One could save the original file so that any changes can be made later if required, with a copy of the option chosen.

Hope this helps
Philip

Hi

each instance will work independently, but a problem occurs when you change the reference within the child to different parents or update a formula (all are updated), this can be overcome by making the component unique or by using parent! instead of the named parent component that way you can have many parents, But by using parent! you lose the automatic update reference function within the component. So depending on your requirements pick the technique to suit.

cub!lenY , cubby!lenY, big!lenY can all be replaced with parent!lenY

Note when editing or updating latter a specific reference will overwrite the parent! in all the children

cheers

0ne point I have found, the copy function within the DC does not make an instance, but another DC embedded within the group. this uses up memory, compare the file sizes of 100 normal copies compared to a DC copying its self. (note you also need to purge the file after going back from 100 to 1)

This may explain your observations

Referring to other posts, it seems that it is good practice to refer to the parent component literally as (Parent!wantedAttribute) So for shelf#1," =(Parent!Lenx)" instead of "=cub#1!LenX" or for the other "=cub#2!LenX"; works for both without problems, a much better way to go..for reuse.

"Re: copies of DC cabinet door not working properly"
Jim says.....
I also prefer to use the 'Parent' word to reference the parent component. This makes sub-components more interchangeable with other DC's, so you can change-out sub-components more easily.

we live, we learn.....

Hi

yes...

Make the shape out of a group of components, where adjacent edges are hidden, adjacent planes are deleted. Triangles are position on the changing axis so hypotenuse changes with sides. Position the axis so that changes go in the desired direction, Refer to my dynamic roof frame in the warehouse.

In theory any shape that can be contain, by pulling a more complicated form apart, thus it can then be manipulated.

Then the fun begins....
especially when changing the attributes. one has to make the changes in reference to the parent axis, if it flies of into the never never, then undo as you are probably in a child environment and change level. For the pitched components I found it easier to build and alter them in a rest position, the rotation values all at "0", otherwise one can get lost within the referencing

Cheers
Philip

Hi

I am currently creating a dynamic component based roof frame. (refer Warehouse, pcmoor) I had similar problems too, As you create each new parent, you need to make all the sub components unique as well, otherwise the child will change with the parents name, Consider cub#1 with shelf#1, made unique to cub#2 containing shelf#1, now shelf#1 has two parents and will alter as you change either parent... reference stuff-up!! Plus you remove it to another file, change it, works fine until you bring it back, then it updates itself to its original parent, or change all the other children. So copy the item within the main model, make it unique, open the "outliner",select the parent object, select all of its children, grand-children... and make them all unique. Then no problems.

Another point I discovered, is that copying within the dynamic is memory hungry. My rafter can reproduce itself, however for 100 times it makes a file of 3.5MG, whereas, copy as per normal, instances are produced, file is 300kb, 100 times different. The roof I placed in the warehouse, is 6MB, much too big...will change soon, current can get it down to 3.5 mainly because of copy within the component. I hope to combine some more elements and ideas to make it smaller.

Once the design is finally built, there will be a need to do a take-off, the one supplied with Pro, is too slow, can some one point out, or make a custom one, so one can pre-select what attributes one needs to report, units? and totals....

Also I am experimenting with hole cutting, by putting cutting planes within sub-components, moving them via the dialogue, then exploding after to leave an existing item behind. Thus you could cut a hole for a sink through a number of surfaces.

Cheers
Philip

Hi

One could place a total within the component name, description. refer to my rafter, or PFC model (pcmoor) do the take-off then hide (delete) the attributes not require or your presentation

and/or build a simple VBA control within (or independent of) the spread sheet which would total up and reformat the page. .

on another note, it would be good if the name attribute was tied to a label, similar to the blocks in AutoCAD. I created and currently use an estimating (VBA) program within AutoCAD for my work as an timber framing estimator, started playing around with sketchup, early days and time permitting.

Hi, I am currently building some dynamic components, "pcmoor", for building construction. I too have been frustrated, however I believe the problem is in editing independent of the main model. For example before reusing a previous component to build the next, copy within a main model, then make all parts unique, use the outliner to select all the sub components at once, then make unique. thus any changes will not effect similar components. Then if you want too place into another file. One day someone needs to write a book....interested?

cheers
Philip

you could put a dimension within the component on a layer that can be turn on or off