So if you recall from two posts previous, the issue was this: We needed the angle "Theta" to generate the arc length in the trig formulas. Now, for whatever reason (can anyone efficiently articulate what we call the "Revit behavior"?) we are able to constrain the Reference Lines to the springpoint of the arc, and to the intersection of the center reference plane, and the T reference plane. This flexes perfectly... Right up until we assign Parameter Theta to the angle dim between the ref line and the center ref plane. Once we do that, it tries to hold the value, and prompts us to remove the constraints. Boy, would it be nice if we could make the constraints override a value that isn't derived by any other incidental. So, we needed to derive Theta in some fashion other than with the angle dim.
James quickly realized that he could obtain Theta as follows: The sin of "Half Theta" is equal to 1/2 Chord, divided by Radius, if we look at the triangle produced. (SOH CAH TOA anyone?)hehe). So, having created parameter Half Theta, he used an arcsin function in his formula for Half Theta "=asin((0.5*CHORD) / (RADIUS)) and achieve Half Theta, and obviously he then made Theta = twice Theta. We obviously could have achieved this in one parameter, but Half Theta came about while exploring potential ways around our math problem. Now, we obviously don't need Theta (or Half Theta) to actually be used as a label in the family itself, as I've shown it in the first image, since its being driven by the math, and not by the reference line now.
What a fun refresher about High school Math this has been. Anyone else starting to think they've lost a little bit in our old age? (lol)
1 comment:
Are you creating the arc in two segments for the top and two segments for the bottom? I find that you can create a very stable arc this way without any convoluted process.
However making an arched window as you show where the trim has an adjustable thickness that can both be a perfect half circle and later become a flatter arc really makes Revit mad.
I have always attributed this to the fact that the intersection between the arc trim and vertical trim is manageable at the outside edge but it doesn't maintain its location on the inside corner. It moves up and down.
Interestingly a sweep will do this quite happily for the vertical arc but not if you include the bottom skirt. So creating them separately and using join geometry resolves it.
Bottom line, I lack the math prowess to mathematically provide the correct values for Revit as you guys have been working on. I'm proud to know you! The last time I was working on such a window I didn't take the next step to track down some mathematical assistance. I built a half circle and a flat arc version of the family and moved on 8-).
Now I know who to call!
Post a Comment