You are currently viewing as a guest which gives you limited access to view attachments, ask questions and access other features. To get full access to all the features, please register for an account. Registration is fast, simple and absolutely free, so please register today! If you have any problems with the registration process or your account login, please contact us.
Does the 'Sill Height' value only report from the bottom of the opening cut, even if there is a 'Default Sill Height' dimension established elsewhere? I would like the sill height of my window to be higher than the bottom of the opening cut, is this possible?
As seen in the image below, Revit will only schedule the 3'-4 1/2" value rather than the 3'-'6"
we offset the opening cut to accommodate for our jamb & Sill thickness and this throws off Revit's Sill Height value, hoping someone else has come across this issue and found a solution.
Last edited by billiam; February 28, 2017, 10:31 PM.
I am able to relocate the Default Sill Height dimension to another reference plane. Is that not working for you? Sometimes template-default constraints will free up if you change the family to a Generic Model (change back when you are done).
I am able to relocate the Default Sill Height dimension to another reference plane. Is that not working for you? Sometimes template-default constraints will free up if you change the family to a Generic Model (change back when you are done).
I was able to move the 'Default Sill Height' dimension to a new reference plane without issue. The problem is that the default sill height value doesn't change after placing windows in the project, meaning my schedule is off.
basically there is a sill height in the project I want to use that's not linking correctly to the 'default sill height' setup in the window family
You may be better off developing a reporting parameter or other formula to get the value you need. I don't think it'll be possible to use the Sill Height parameter that is a part of the project level as you want to, as it does not translate to the family editor.
Developer at Anguleris BIMsmith Marketplace.
Previously at Sumex Design for ARCAT.com
"Default sill height" is just that, a default. The family will use that value when an instance is initially placed, and any further updates to the "Default sill height" won't change it. I believe that is true even with "overwrite parameter values" is selected when a family is reloaded.
I don't use the window family much, and when I have I haven't tried to schedule sill heights. As as far as I can tell from quick experimentation marking the desired reference plan as "Defines Origin" seems to do the trick.
Julie Kidder
Architect + BIM Director
Hartman + Majewski Design Group
You may be better off developing a reporting parameter or other formula to get the value you need. I don't think it'll be possible to use the Sill Height parameter that is a part of the project level as you want to, as it does not translate to the family editor.
I think this is the only way. My sill height & head height values in the project were off by the offset of my jamb (1 1/2") as shown in my original post. I had to make that jamb value a shared parameter and then a project parameter with a calculated value (Head Height + JambWidth) to get my schedule to be correct. Seems like a long work around though I hope i'm just missing something.
I think this is the only way. My sill height & head height values in the project were off by the offset of my jamb (1 1/2") as shown in my original post. I had to make that jamb value a shared parameter and then a project parameter with a calculated value (Head Height + JambWidth) to get my schedule to be correct. Seems like a long work around though I hope i'm just missing something.
Setting the reference plane to define the origin does change the location of the window. It's possible that only works in conjunction with removing the opening cut and replacing it with a void, but I did get a window to believe the head was the sill in therms of the sill height parameter.
Julie Kidder
Architect + BIM Director
Hartman + Majewski Design Group
Setting the reference plane to define the origin does change the location of the window. It's possible that only works in conjunction with removing the opening cut and replacing it with a void, but I did get a window to believe the head was the sill in therms of the sill height parameter.
tried this and it made the project sill value 0'-0" when loaded, even if my window was clearly some distance above the host level :banghead:
tried this and it made the project sill value 0'-0" when loaded, even if my window was clearly some distance above the host level :banghead:
I just experimented with the default window family - I had already swapped the opening cut for a void, so I don't know if that was part of the solution. I changed which reference plane was the origin a couple times and it worked. I also loaded it into the project overwriting all parameters, sice I didn't care about what was in there There might be other things affecting your windows behavior.
Julie Kidder
Architect + BIM Director
Hartman + Majewski Design Group
I have a window with a brick mould casing which required the usual simple opening cut to be replaced with void extrusions to get the proper complex opening...
I'm experiencing some difficulties trying to create a simple window with two sliding panels. I need to create one parameter to set the window height from...
I am nesting a casement family (shared) either side of a fixed window host family. Everything works fine except for the sill and head height of the nested...
Is there a simple solution to lock wall opening to the in-project host level?
I don't get it why windows families are so...
October 10, 2019, 12:17 PM
Working...
X
😀
🥰
🤢
😎
😡
👍
👎
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment