Hi All,
I created a counter top w undermound sink family a few months ago and all was working well.... last month someone changed something in the family and the sink no longer moves with its reference plane -_-
We wanted to be able to stretch the counter using the arrows (strong reference plane with instance dimension in between) and then do the same with the sink.
It works fine when in the family, but once inserted into a project the sink doesnt move. The arrows move but not the sink. I'm a bit perplexed.
See attached family.
Gelöst! Gehe zur Lösung
Gelöst von ToanDN. Gehe zur Lösung
Are the parameters locked or unlocked in family? Is the sink constrained properly?
...Instance not type Parameters?
Length parameters are both unlocked and instance parameters, sink is alligned and locked to the reference plane.
Alright, I opened your family and messed with it. Loading the nested sink as a non-shared family works.
ok... but that means that any information in the sink family wont appear in any schedules right?
Here is a revised version. Nested sink is still shared. Screencast added to show the nested sink and the stretching in project.
The 6" dimension from the wall to back of sink is not to a reference plane of the sink family, but to a geometry. I add a reference plane in the nested sink family to fix it. Also, I have no idea why the sink manufacturer add a redundant center reference plane while the family already has one.
I'm positive I would have checked everything you did, Toan; this is Revit 101 stuff. What did you find?
...nevermind. I see. didn't catch the redundancy.
It's weird. In the family I can drag the reference plane and the sink follows like an obedient puppy. But when I alter the Sink Location parameter, then the sink breaks away from the reference plane. And I haven't even got to the Project yet.
@barthbradley wrote:
I'm positive I would have checked everything you did, Toan; this is Revit 101 stuff. What did you find?
Not sure if you typed this one before or after my post above.
@Sahay_R, what weirder, is that I had no problems once I made the nested family not shared.
Funny story: when I first started using Revit, I had a similar problem: couldn't get the grips to move the sink. I tried everything but I couldn't get the darn sink to move! Then I discovered that the sink had been moving all along. What I had been seeing in Plan View was the symbolic line not moving (obviously poorly constrained)! The geometry itself, which was set to be invisible in Plan View, was moving all along. I just didn't see it in Plan. Stupid me.
@barthbradley , @ToanDN , @Sahay_R
Thanks everyone, I'm definitely no expert yet on families and what to do when they have issues but you guys always seem to have the answers!
Thanks a bunch.
The rule of thumb is always constrain to reference planes or reference lines, not actual geometry. Constraining to geometry may work is most cases but it can bite you where and when unexpected. I bet your vanity family worked before because the nested sink wasn't "shared", so constraining to geometry had no consequence., just as @barthbradley has proved.
I totally agree Toan, but that agreement not withstanding; constraining the geometry can be the only solution in some cases, IME. I would not rule it out.
the revit sink must be set up for complicated mep. I want to put down a counter top with 2 sinks. It just defies simple common sense.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.