Array problem

[spoonkim]

Hi

I have a little problem making array items. As you see the image below and the file, it doesn't allow me to drag it upwards to make the box taller.  When it's locked as single object it works but after using array it doesn't work. Any idea how to fix? The file was created in Revit 2024

[mhiserZFHXS]

I generally don't array extrusions. I would make the extrusion in another family and nest it into this one. That's what most folks around here would accept as best practice.

It'd also help to actually dimension those reference plans and assign parameters to them rather than just dragging it.

[Mike.FORM · Accepted solution]

As @mhiserZFHXS said when arraying it is always better to array a nested family.

However for a simple extrusion you can assign the height parameter to the extrusion end property instead of locking it to the ref plane. The ref plane can still stay there if you are wanting it for an instance grip.

[spoonkim]

Thanks for your advise. That's a good solution I was looing for. Is there any perticular reason why 'always better to array a nested family' ??

[TripleM-Dev.net · Accepted solution]

Hi @spoonkim,

It's not so much as "always" use a nested family, but more "use parameters to drive size, and not lock to control size, only position". Also nested families are easier to control, also in position.

Imagine creating a Family and have it's height controlled by a instance parameter (with reference planes), if this family is used as a nested family and the bottom and top (refplane) of the family is constrained to refplanes in the host family, you would still encounter this issue when creating a array group.

Instead link a host family parameter to the family to control the height (type or instanced based, depending if the family is shared or not, for shared use instance parameters!)

This could also be used on the extrusion (depending on how it's made), by attaching a parameter to the Extrusion End, see sample below:

[Mike.FORM]

When arraying an object it needs to have any and all items (ref planes, ref lines, dimensions) used to constrain the objects shape and size need to be part of the array.

Outside of the array the only constraints required are the ones controlling position as @TripleM-Dev.net said.

If you build the arrayed object as a nested family it makes it easier to control these constraints. It also lets you have helper parameters be part of the nested family which makes the host family less cluttered when brought into project because those helper parameters won't be visible to the user.

Nesting the family also lets you take advantage of family type parameters which allow you to swap between multiple different nested families for the array.

[ToanDN]

Why is it better to use nested family to array?

Because your only constrain one element in the array instead of multiple components.

[spoonkim]

Thanks guys! That was a great advise and still lots to learn though. 😃