Nested Structural Column Family is not placed in the correct reference level

Nested Structural Column Family is not placed in the correct reference level

ale8Y7G6
Contributor Contributor
1,936 Views
10 Replies
Message 1 of 11

Nested Structural Column Family is not placed in the correct reference level

ale8Y7G6
Contributor
Contributor

Hello everyone, I'm pretty new to Revit and I was trying to create a component for my window framing.

 

Everything works properly but the family is always being placed on the main floor even when I'm picking another level. For some reason, the header is the only thing that seems to work.

 

I'm attaching some screenshots.

Thanks in advance for your help!

0 Likes
Accepted solutions (1)
1,937 Views
10 Replies
Replies (10)
Message 2 of 11

ToanDN
Consultant
Consultant

Can you select it and change Base Level/base Offset and Top Level/Top Offset?  Or just share the family here.

0 Likes
Message 3 of 11

ale8Y7G6
Contributor
Contributor

I can change it but the only thing that moves is my Header. Or if I select Main Floor and Roof Level it also works but of course taking into account both levels.

 

Here is my nested family, do you need the separate families?

0 Likes
Message 4 of 11

ToanDN
Consultant
Consultant

I think you would need model the nested columns from Generic Models template (do not use the two-level template), then change to Structural Column category..

Message 5 of 11

barthbradley
Consultant
Consultant
0 Likes
Message 6 of 11

ale8Y7G6
Contributor
Contributor

Hi, thanks for the video! This helps with the problem of the height for the columns but my columns are still being placed on another level.

0 Likes
Message 7 of 11

ToanDN
Consultant
Consultant

Structural columns and beams that is shared and nested in another family never work right in the project.  There are several ways to do this:

- use Generic template (any generic except 2-level based) for those and change the category if you want them to schedule under Structural columns

- create the whole thing as a truss family and assign members in project

0 Likes
Message 8 of 11

ale8Y7G6
Contributor
Contributor

This might work but I would need to do different types for the different wall heights right?

0 Likes
Message 9 of 11

ToanDN
Consultant
Consultant

@ale8Y7G6 wrote:

This might work but I would need to do different types for the different wall heights right?


Not at all.

- If you go with #1: the main family can still the same as you have, controlled by the base level and top level, but the nested families are constrained to ref planes that in turn, constrained to the levels

- If you go with #2: you can control a truss height by an instance parameter or attach it to a floor or ref plane in the project to change the hight

0 Likes
Message 10 of 11

ale8Y7G6
Contributor
Contributor
Accepted solution

I ended up doing everything in a generic model, from my initial family to my nested family. I drew a reference plane to create a parameter for wall height and linked it inside my nested family. It's probably not the best way to do it but it worked.

 

However, I had to do different types for my different wall heights which are usually 9' or 7' always, so no big deal.

0 Likes
Message 11 of 11

ToanDN
Consultant
Consultant

@ale8Y7G6 wrote:

I ended up doing everything in a generic model, from my initial family to my nested family. I drew a reference plane to create a parameter for wall height and linked it inside my nested family. It's probably not the best way to do it but it worked.

 

However, I had to do different types for my different wall heights which are usually 9' or 7' always, so no big deal.


Set the height parameter in the family to Instance parameter, not Type parameter, then you don't need different types for different Heights.

0 Likes