Post title may be more specific than necessary. Essentially, I am looking for the syntax to use in a parameter's formula that causes it to calculate its' value from the specific object/face/line snapped to.
When placing the family in the project the interface clearly finds the midpoint snap which logically indicates that the endpoints are a known and hopefully accessible value. This same paradigm should apply if I can snap to an endpoint vertex as well.
I'd like to be able to place an array family by clicking on the midpoint snap and have the array length automatically populate with the distance from that midpoint to either endpoint of the object/line/face I am placing along.
Gelöst! Gehe zur Lösung
Gelöst von ToanDN. Gehe zur Lösung
I think it is easier to include a drawing as well, because your explanation can be interpreted in many ways. From what I understand is that you want a line-based family, is that correct?
@ToanDN wrote:
Create two identical arrays from one point running in opposite directions in the family.
I am already doing this because I am using a face based family and need to snap to ceiling edges. It is nearly impossible to reliably and efficiently snap to the end point of ceiling corner at the face but is very easy to snap to the midpoint. Furthermore, the family I am placing should correctly have a member at the midpoint of the ceiling (placing soffit kickers). I am thus mirroring the array to go both directions from the midpoint.
At any rate, the information I seek is not so use case specific. I need my family to have formulaic language that detects the length from the snapped midpoint to either endpoint and populates a parameter with that value. This concept would be applicable far beyond this one use case.
I am otherwise having to use strong reference planes for shape handles which is not even close to as efficient.
@Avaris. wrote:I think it is easier to include a drawing as well, because your explanation can be interpreted in many ways. From what I understand is that you want a line-based family, is that correct?
My question was intentionally broad as the concept is to get a value from the Revit interface into a parameter regardless of the specific use case. I have outlined in another post the specifics (face based, ceiling edge at the face).
My thinking is that if the midpoint can be found by the interface then the dimension to the endpoints is also known. I want that dimension to be captured by a parameter. Seems this should not be overly specific to the family type, use case, etc.
To be most clear the workflow I am envisioning is clicking the mid point of a ceiling edge and kickers automatically arraying from that point to each corner.
I have evolved the family to the point now that I can click the mid point of the ceiling edge to place a mirrored array with a shape handle to drag to the edge. I am trying to eliminate the dragging step as I consider that the program knows the midpoint and thus also knows the endpoint and I should be able to access that in my array length parameter rather than manually imitating that value by dragging shape handles.
Revit in itself is not smart enough to match a family to the length of the ceiling edge, unless you are using some specific system family such as slab edge, fascia, gutter.
Using the method I have said you could pick the midpoint of a ceiling edge to place the array, then pick one endpoint to set the extent, the array would populate to that endpoint end the other endpoint to fill the entire edge.
But I am having trouble understanding why you can just place a line base array, or an adaptive family by picking 2 endpoints?
@ToanDN wrote:Revit in itself is not smart enough to match a family to the length of the ceiling edge, unless you are using some specific system family such as slab edge, fascia, gutter.
Using the method I have said you could pick the midpoint of a ceiling edge to place the array, then pick one endpoint to set the extent, the array would populate to that endpoint end the other endpoint to fill the entire edge.
But I am having trouble understanding why you can just place a line base array, or an adaptive family by picking 2 endpoints?
I am interested in how to configure the family such that I would snap to the midpoint and the family would not place until I had also picked an endpoint. That seems a reasonable compromise. As it stands the family places on the first click.
I suppose I could go back and rebuild the families to be line based or adaptive and use the same techniques to leverage the midpoint snap. I had initially shied from line based because I had not yet figured out how to ensure a member in the center. I had stayed away from adaptive because of a whole new learning curve.
@jeremy_taylor wrote:
I suppose I could go back and rebuild the families to be line based or adaptive and use the same techniques to leverage the midpoint snap. I had initially shied from line based because I had not yet figured out how to ensure a member in the center. I had stayed away from adaptive because of a whole new learning curve.
You supposed correctly. Only line based or adaptive families allow you to control placement with 2 clicks.
Okay, I rebuilt the families using generic all the way to the final nest which I made line based and it does work as advertised. It irritates me that Revit doesn't make the distance from mid point to endpoint accessible for placing in a parameter. There is no snap at the end the ceiling corner (interior cutout corner) like there is for the midpoint so it is still somewhat subject to imprecision and obviously doubles the amount of effort at a minimum over just clicking the midpoint. Failing having access to what should be known by the program this will have to suffice.
I've attached the family for anyone interested in placing soffit kickers at inset ceilings. It's going to be a huge help for our coordination effort on this project and many to come as these things are often overlooked or underestimated for their impact.
To use, place at midpoint of the lower ceiling and click at the right corner. You can configure the ceiling thickness to correctly bring the bottom of the vertical member to the plane of the low ceiling but it will default to zero placing it on the top of the lower ceiling object. Otherwise you use the RCP to dial in the ceiling differential and the difference between deck (or attaching structure) and the high ceiling plane. Kicker angle is ostensibly adjustable as well though I have not really tested that.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.