Want To Move Family on Elevation from Level but Keep Nested Families at the old height

[jamiemarshallWRH9M]

Hey all

I'm really struggling here and I hope someone has done this before.

Essentially I've got a family with two nested families inside of it. I want to be able to move the family up to 1250mm, but keep the two nested families down at 600mm

"Easy" i thought, just take the elevation away from the elevation and add 600, but you can't access the elevation height!

Has anyone solved this before?

[RDAOU]

@jamiemarshallWRH9M 

It depends on the category of the host family and the nested one, how the host family is modeled, how many elements are directly modeled in it, and how they are constrained.

An easy approach is:

• Instead of having two nested families within a host that also contains 3D modeled elements, nest all three into a 4th family that serves only as a host/container for the assembly.
• Use the "Elevation from Level" or "Offset from Host" parameter to control the height of the components.

If you post the family you have, I’m sure you’ll receive several valid suggestions from forum members.

[jamiemarshallWRH9M]

https://we.tl/t-F0ChJtAcW3 - Revit 25 link to the family

I don't think nesting it into a fourth family would do much. Changing the "Elevation From Level" would still globally change the height for everything in the family.

I need the nested families to always stick to their predetermined heights, in this example 600mm AFFL.  Nesting them into a fourth family, moving that up to 1200mm with Elevation from level would then make my 600mm heights really at 1800mm, even though they display as 600mm

[RDAOU]

@jamiemarshallWRH9M 

See attached ... you need to work more with reference planes. Kit extrusion hosted and constrained to ref plane which the 2 nested boxes contelled by associating their Elevation from level to a parameter in the host

[jamiemarshallWRH9M]

Thanks for this

It is unfortunately the method I was trying to avoid using if possible. It avoids the hassle and issues with getting people to use a certain parameter for some items in the library, whilst others are still on the old system. Not to mention if things are manually moved the data becomes inaccurate (Manually moving the elevation of 0 keeps things at the same distances in the family, but it isn't correct in the project)

Its a good shot at this though. I'm not fully sure it is ever going to be possible to detach that link between elevation in level and nested items.

[RDAOU]

---

@jamiemarshallWRH9M wrote:

Thanks for this

It is unfortunately the method I was trying to avoid using if possible. It avoids the hassle and issues with getting people to use a certain parameter for some items in the library, whilst others are still on the old system. Not to mention if things are manually moved the data becomes inaccurate (Manually moving the elevation of 0 keeps things at the same distances in the family, but it isn't correct in the project)

Its a good shot at this though. I'm not fully sure it is ever going to be possible to detach that link between elevation in level and nested items.

---

@jamiemarshallWRH9M 

what old system? You had random components with practically no constraints or associated parameters. The built in reference planes of the specialty equipment template were unpinned, renamed and moved around from their original location. So I’m slightly confused now! how were you trying to avoid this approach when the family u posted was not even close to what have been suggested? 

Can you elaborate on what exactly isn’t correct in the project when you load the family? Are you sure you are using it correctly? and maybe you can also explain what do you wish to detach exactly? Moreover, if you do not enter the parameter values manually, can you specify what other method of parameter value input you have in mind? as long as it is not Telepathic, it should be doable.

[jamiemarshallWRH9M]

Well thank you for your help anyway.

It is a theoretical solution to the problem i'm having. Whilst it isn't an exact solution to wanting to still use the "Elevation From Level" parameter in the scene to raise the height of the family, whilst still maintaining the original Nested families height, it is a solution of sorts.

I'm sure other users searching for this in the future will find your post helpful. Again, thank you for your help and time on this.

[SteveKStafford]

Sounds like you should be grouping these individual families instead of nesting?

[TripleM-Dev.net]

Hi,

Nested families are relative to the Host, so if the host moves then the nested families move along.

If you need the nested families to have a offset from it's host built parameter in it to offset them.

Those can be type or instance. so moving the Host up, you can fill a instance parameter that keeps them at another elevation height (relative to host)

From the reactions I see, this is a similar answer.