The Dimension Views by Category is a little quirky when dimensioning curtainwall elevations.
When the ‘Tie Condition’ is set to ‘Elevation: Tie to All…’, the dimension string to the levels are either partially placed or not placed at all, depending on the selected ‘References’ option.
Both ‘References’ options: Mullion’s Centerline & Mullion’s Width produce inconsistent output, and also varies depending on the Curtainwall’s Base Offset = 0 or > 0.
@nbassett Thanks for letting us know about this, I’m sure @Miguel will look into it ASAP.
May I ask - do your CW mullions use custom profiles? We have encountered issues dimensioning these in the past when using the “Mullion’s Width” setting. Also, if you have a screenshot of the results you’re getting that you are able to share, it could help us resolve the issue.
Could you post some examples of the outcome? Sometimes, the crop region of the view hides the dimensions created by Glyph. Additionally, when the “Far clipping” setting is not set to “Clip with line,” it will capture other curtain walls in the view.
Are you getting better results when the “Tie condition” setting is set to “None”?
In the screenshot below, Level(s) do not have Dimensions when the following settings are applied…
Glyph Task settings:
Annotation Collision Avoidance: Off
Wall Dimension Options:
Elevation: Curtain Wall
References:
Elevation: Mullion’s Centerline
Tie Condition:
Elevation: Tie to All Levels Intersecting the Dimension
Offset (ft): 3
View settings:
Far Clipping: Clip with line
Far Clipping Offset - extends beyond the Curtainwall element
The Curtainwall settings:
Base Constraint: FIRST LEVEL
Base Offset: 2’-0"
Top Constraint: Unconnected
Height: 13’ 0"
If you change the Task’s References to: Elevation: Mullion’s Width, The Dimension to the Level is placed on the Level above, but not the CW’s Base Constraint (First Level)
Thank you for your response! This is currently working as expected:
In your first example, the dimension line (red) always matches the size of the curtain wall, which is why the dimension line intersects with the “First level.”
We have a feature on our roadmap that will allow you to “Tie to the base constraint level” instead of using the “Tie to all levels intersecting the dimension.”
In addition, I see that there is a ‘0’ reference in the first example. This will be updated by Glyph 2.3."
Hope this makes sense, and thank you again for your feedback!