Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Parameter Controlled Array For Louvered Grill Not Working

5 ANTWORTEN 5
GELÖST
Antworten
Nachricht 1 von 6
Anonymous
976 Aufrufe, 5 Antworten

Parameter Controlled Array For Louvered Grill Not Working

I'm trying to create a louvered grill that I can adjust the width and height to any size to use for various grills for a trailer.  I've gotten everything to work except for when flexing the width after adding the array.  With one louver, all the flexing works fine.  After I create the array, the width doesn't work properly.  My height changes fine and even the formula for how many louvers to ad as the height changes works, but I can't get the width figured out.  Some help figuring out what I'm doing wrong would be greatly appreciated.  I'm attaching the family as well as a screencast of what I'm doing.  Thanks in advance for the help.

 

 

5 ANTWORTEN 5
Nachricht 2 von 6
SteveKStafford
als Antwort auf: Anonymous

I haven't looked at your file yet. I avoid this sort of family quite often by using THIS Technique, a curtain wall type that provides the basic appearance of a louver assembly without any family editing effort.

 

Generally, making arrays work in families is often easier to accomplish when they are built with nested families, with the basic array being a child (nested) to a host parent that then flexes the array (child). In your case the width doesn't behave because an array also uses the group concept and new members of the group (when the array is flexed) didn't exist earlier. That newness lies outside the constraints of the array for width. When the array family is nested Revit seems to cope with this condition better. I have found that if a family has the maximum number of members of the array set in advance that the array can behave more reliably. Again, the nesting technique generally resolves it without doing that.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

Nachricht 3 von 6
Sahay_R
als Antwort auf: Anonymous

Model the louver as a generic model. Give it basic parameters - length, width, whatever you need. Nest it into the destination file, associate parameters with corresponding parameters in the parent file. THEN create the array.


Rina Sahay
Autodesk Expert Elite
Revit Architecture Certified Professional

If you find my post interesting, feel free to give a Kudo.
If it solves your problem, please click Accept to enhance the Forum.
Nachricht 4 von 6
SteveKStafford
als Antwort auf: Anonymous

I've attached a quick example (v2015) of what I described (and the other reply too) using a nested louver family. I left the louver and the array outside of the opening just so it easier to see. You'll find you can flex the opening width and height and the louver will play along. Notice the louver's parameter values have been assign to parameters in the host family.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

Nachricht 5 von 6
Anonymous
als Antwort auf: SteveKStafford

Thank you for all the assistance.  It seems odd that you have to use a nested family to make it behave correctly.  Seems like Autodesk could make the grouped pieces act like a nested family.  Anyhow, after creating the louver as a nested family as suggested.  The array seems to work and flex properly.  Thanks again for the help.  I'm attaching the updated family for anyone who cares to see it.

Nachricht 6 von 6
SteveKStafford
als Antwort auf: Anonymous

The nested family's width is assigned to be equal to the host width. Each copy of that family that is generated by the array shares that understanding. Discrete extruded or swept forms that are part of an array can be constrained using their first and second member of the array. Each new member however doesn't respect the constraint (align/lock) associated with the first and last or second part of the array.

 

Yes, there is probably more they could do to make these arrays easier to constrain without a nested family. Either it hasn't been a big enough priority for them or the workaround (nested family) is elegant enough because it resolves it easily as well as provides us with a reusable family for use in other related kinds of families.


Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
EESignature

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report