parameters of unknown origin overriding window placement

parameters of unknown origin overriding window placement

daveNPUCB
Observer Observer
608 Views
11 Replies
Message 1 of 12

parameters of unknown origin overriding window placement

daveNPUCB
Observer
Observer

Hey all, 

 

I have a window family I created for a structural team that is basically just an opening that they can use to match opening sizes for their model to allow for header & hold-down placement. The head height parameter is set to type based since its fairly consistent in the project.

win snip1.JPG

 

Once brought into their project, these basically go out the window and they are forced to set the windows via sill height per the parameters shown below.

 

win snip2.JPG 

While the sill height parameter is correct, the head height one is obviously not and unnecessary / confusing. Can someone help me remove this parameter / get it to report accurately? Moving it to the constraints portion of the parameters would also be a bonus. Its not associated with the family and they don't have a shared parameter file or global parameters to remove it from that I can find. 

 

Hopefully someone on here has run into this before and found a way out. 

 

Thanks in advance,

Dave

0 Likes
609 Views
11 Replies
Replies (11)
Message 2 of 12

AGGilliam
Collaborator
Collaborator

Windows have built-in instance parameters called Head Height and Sill Height, if you added your own type parameter for Head Height it would be found in the type parameters window (click Edit Type near the top to access it). I would recommend removing that parameter though to avoid confusion. You can use one of the families included with Revit as a reference to see how they built theirs.

0 Likes
Message 3 of 12

ToanDN
Consultant
Consultant

- Set the Level Reference Plane in the family to Origin

ToanDN_1-1635790582195.png

 

 

ToanDN_0-1635790557592.png

 

0 Likes
Message 4 of 12

barthbradley
Consultant
Consultant

It looks like you made the Top Reference Plane in the Window Family the Origin Ref. Plane.  Uncheck "Origin".  

0 Likes
Message 5 of 12

daveNPUCB
Observer
Observer

Bottom reference plane is set to origin, (might be redundant with level there) the sill parameter continues to work. @ToanDN ignoring the lower head height value has also been my workaround but it would be great to not have it there at all.

0 Likes
Message 6 of 12

ToanDN
Consultant
Consultant

Share the family.

0 Likes
Message 7 of 12

barthbradley
Consultant
Consultant

@daveNPUCB wrote:

Bottom reference plane is set to origin


 

It's a Window Family Template?  You don't need to indicate an "Origin" Ref. Plane.   

0 Likes
Message 8 of 12

daveNPUCB
Observer
Observer

Here's the file, rough w & h parameters drive. 

 

I think its more of an issue with the project file though which I cannot share. 

 

@barthbradley my thoughts exactly but I figured couldn't hurt to see if it made a difference. 

0 Likes
Message 9 of 12

AGGilliam
Collaborator
Collaborator
Built-In parameters can't be removed, if you need to use the type parameter over an instance parameter your best bet is to ignore the instance parameter like mentioned above or re-build the family as a wall-based generic model which wouldn't have the same Built-In parameters.
0 Likes
Message 10 of 12

ToanDN
Consultant
Consultant

I thought you want the governing parameters be the Opening Head Height and the Opening Height, not the Sill Height.   Am I assuming incorrectly?  

0 Likes
Message 11 of 12

daveNPUCB
Observer
Observer

@ToanDN Ideally both head and sill height would, at the very least, report accurately. Currently, sill height reports accurately and head height (type based) is accurate on placement (which would also make the sill height shown accurate). But there is the head height parameter that is in the "other" subcategory in the properties window that is just reporting sill height. Not sure if I'm explaining it well enough but its tough telling folks to just ignore something which is what I'd likely have done in the past.

0 Likes
Message 12 of 12

ToanDN
Consultant
Consultant

I think the reason being you created this window from a different template then changed the category to window.  I suggest recreating it from the window family template instead of fixing this one.

0 Likes