a locked re-sizable nest family lost its position in host family

[heichan88]

Hello,

I made a re-sizable child family which is locked to reference lines and works well, this family can be resized according to a instance L parameter. Then I nest it to the host then lock to new reference line （say floor level), and assoctate L in the host to the nested.

Then when I change the size of L, the nested family is re-sized (bigger) but it is unable to lock to the reference line any longer. The error meddage "constrains not satisfied"

Please advice

Thanks

 

 

[Rab_i · Accepted solution]

Are you able to post the family so we can take a look?

It appears from you description, that you are changing the size of the nested family with a parameter. Are you using  but this same parameter L  to drive the location of reference planes? Perhaps using L parameter to wire to the dimension parameter separately from the reference planes will work. Only one reference plane to lock its location. No size lock. Size can be driven by wire parameter from parent to child. 

[heichan88]

Hello Rab_i.

Please find the RVT, the project parameter L is the leading parameter which will re-size all other elements , including nested families and locaion of reference lines

Don't understand "wire to the dimension parameter" and the last sentence. Could you elaborate that a bit more?

Thanks

[Rab_i · Accepted solution]

Now that I see your Revit file, I think the questions related to families and nesting is not really what it seems. I noticed you are using families inside a project and locking them to the Project Level. Is there a particular reason you are doing this? Once the families are hosted in the Project Level, you can change the parameter in the properties window for "Offset from Host" or "Elevation from Level". 

There is no need to lock it to the Project Level. 

If nesting of families is important then perhaps inserting these two families into one Parent family would solve your issue. This also makes them more manageable.

If on the other hand you want these families directly in the Project environment then perhaps they are not nesting but dependent on each other families. Perhaps then driving their location (elevation) using a Global parameter may make more sense. 

In either case I don't recommend locking these families to the Project Levels. Generic models like you have automatically are associated with the Level you add them into. I hope this makes sense.

Thank you! 

[heichan88]

 

Hello Rab_i,

AFter I unlock A from level alone, then it works (resize and stick to level). But,

If I LOCK the other upper nested family B to the below nested family A, then A move along with B and deviate from level. 

I suppose A should not move around along with B which dependently lock to A. 

is it related to the formula inside  nested A?

Thanks

[RDAOU]

@heichan88 

Host bottom family to level and top family to face

[heichan88 · Accepted solution]

Hello,RDAOU

Yes follow your advice, those "normal" (vertical and horizontal) nested families are working well, (re-size and stick to locked location). But when testing this nested by rotation and locked to the intersection of 2 axis, a sub-family within this nested family has error. See RVT

Any advice. Thanks

  

 

 

 

[RDAOU · Accepted solution]

---

@heichan88 wrote:

Hello,RDAOU

Yes follow your advice....

---

1. No you did not follow the suggestion I gave you in the previous reply... 
   • The bottom family is still Work Plane based...you did not change it as per previous GI
     • 
   • The top Family is still hosted to a reference plane ... not the work plane at the top face of the Bottom family
     • 
2. Your original question was/is related to constraints not satisfied when changing the Dimension, not the rotation. And this has been addressed in my previous reply
   • Bottom Family does not need to be work plane based and should be hosted to Level 
   • Top family should be hosted to Work Plane @ the top face of the bottom family (see highlighted contour)
     • 
3. The rotation should also be resolved
   • When the top family is hosted on the highlighted work plane, it will move with that plane
   • After placing and aligning it into position, you do not need to lock it => not being locked will allow you to rotate it using the space bar

Alternatively: Rotation may be implemented in the family 

[heichan88]

Hello RDAOU and all,

now by setting worplane to be "pick plane" then  all testing works well, this nested system is approching being practical for customized 3D printing production.

many thanks!

[heichan88]

Hello RDAOU

BTW could you send back the rvt file you have modified? for my study

Thanks