Flexing family mystery

[jo_3_]

Hi All,

I'm hoping someone can help solve a mystery: I have two 2D workstation families, A and B (see attached.) In each, I have a length instance parameter ("TOWER DISTANCE FROM WALL") to move the tower location, and it flexes properly in the family files. If I load them into separate project files, they also flex properly. But when I try to load them into the SAME project file, only one, or the other will work, not both. Any thoughts/suggestions would be greatly appreciated. Thanks!

[Andre Carvalho]

I think it has to do with the fact that all elements on your families are shared. Loading one will replace elements in the other one. Do they all have to be shared?

Andre Carvalho

[Ning Zhou]

use reference planes to control parameters, don't know why creating 2 seperate families instead of 1?

[jo_3_]

All elements have to be shared because they each need to be separately tag-able. In reality, I have 4 workstations, A-D, all of which flex properly in family. But again, when loaded into the same project only two will work, and two will not. Sometime when I load into a different project the other two will work and the first two will not. But it's always the same two that are working together (i.e. A and C or B and D. Never A and D or A and B.) All elements in all workstations are shared.

I have to have different families; there are many more situations that need to be accommodated.

I have also tried using Ref.Plane to Ref.Plane, Ref. Plane to Ref.Line, Ref. Line to Ref.Line, Ref.Plane to object, object to object, etc. It doesn't seem to make a difference.

[Elmo]

Would have to agree with Joe.zhou. You have family A and B which is exactly the same. You might aswell make 1 family with 4 different types, if the are exactly the same. Is C and D different from A and B? Are you only looking to adjust the distance for the tower?

[jo_3_]

Families C and D do contain different parts, so I can't make 4 types of a single family. Even if I could (which would be great) it doesn't really explain the issue at hand.

What I've done as a workaround is copy family A three times, edit/load/delete parts as necessary, and save out as families B, C, and D. Now at least they will either all work, or all not work when loaded into a project file.

I am also copying family B three times, and saving out as families A, C, and D in a different folder. We're using these families in a number of project files, and people will just need to load in the version that works for them until/unless I find a fix.

Thanks for all your help!

[Elmo]

Can you post C and D for me please. I want to have a look at all of them and see where things could be going wrong.

[jo_3_]

I had originally only posted A and B because a solution to those two would probably be a solution to C and D as well. But if it helps, I've attached C and D.

Good luck!