hi Billiam,
One issue I came across recently was shared nested and reporting parameters. Basically, I used a reporting parameter to obtain the width of the nested family to report to the host so that it could be used in a calculation. However, when i used the family type parameter to remove/exchange the shared nested to another, the family parameter failed (probably because the family I was reporting from was no longer in the host family).
Anyway, I thought I'd mention it as you said above that are using Family Types Parameters to swap things out. So I was thinking that your issue could be something similar to what I encountered.
Kind Regards,
Ben
[Edit due to my terrible grammar!]
-
Casework? I recall Aaron was mentioning something recently about some freaky behaviour he'd been seeing with casework... he even did a video, but damned if I can find it.Originally posted by billiam View PostLeave a comment:
-
thanks for the reply, Alex! I was able to do as you suggested and link all the parameters through the nested families.
Everything works as it should EXCEPT for when I first load the family into the project. The parameters are reverting the nested object dimensions to when I first placed them, as shown in the first photo. However as soon as I change a single parameter in the project everything looks as it should :crazy:
any ideas? why does revit forget the linked parameters when placing the family?
thanks!
Last edited by billiam; May 10, 2016, 07:28 PM.Leave a comment:
-
I only lock onto refplanes the origin axis of the nested component and always link through the parameters. You might have to make some "calculation" parameters to link the nested families too....
Been doing it that way for about 10 years now!
Making them type parameters won't work if they are shared....leave them as instance and youre good to go.Last edited by Alex Page; May 12, 2016, 12:45 AM.Leave a comment:
-
Nested Families Breaking Constraints
After searching around this seems to be a hot topic with tons of information why this may be happening. In my case I'm wondering if it is because I'm using all instance parameters to drive the shape of my nested components, then align-snapping them to work planes in the host family. Does this method normally cause issues? The parameters that I overwrite instead seem to work better and break less, it's just harder to make that work for each one.
What I am trying to do is make a cabinet frame where I can swap out certain components using a <family type> parameter and an assigned label. And this might be overkill but almost every component is modeled separately, then loaded in so that we can keynote each piece.
Each nested component's dimensional shape is driven by laying out reference planes and using instance parameters, then I load them into an assembly family and snap those instance parameters to another set of reference planes. Would it work, or be better if I made these dimensions type rather than instance and overwrite using the host family parameters? any other suggestions would be greatly appreciated.
thanks and hope that wasn't too confusing to follow along. I've attached some screenshots to show how things get nested and assembled.
Leave a comment: