Transition visibility not working

[ReneBogersREBO]

Hi all,

I have build a family for transistions between pipes.

The parent family contains another familie, which is used twice (visible yes/no, depending on size big to small or small to big).

In my 3D view and floorplan (detail level: course/medium) all goes wel.

BUT in my floorplan (detail level:fine) it shows both instances instead. So the visible is show AND the not visible is shown.

Any clues? Hope I made myself clear.

[iainsavage]

Upload the family please.

[ReneBogersREBO]

Family added 😉

[iainsavage]

I can't explain that behaviour. Someone like @fabiosato @robert.klempau @L.Maas would probably be better at helping with this.

[L.Maas]

Not exactly sure why it has this behaviour. But a quick glance at your family indicates to me you have an unstable situation.

If I look at the nested element (lijmring). I see that the ring is linked to visibility parameter TypeB

In the host family you get this

You set the visibility of the element to off. However you set the TypeB to true.

So on the one hand you ask it to hide on the other one you want to make it visible.

In my opinion this results in unexpected weird behaviour.

[ReneBogersREBO]

L. Maas,

I'll try to make myself clear in English 😉

The nested family (lijmring) I have two other nested families (typeA and typeB), those visibilities are set by parameters (TypeA / TypeB). This is depending on the dimensions and been pulled out of the lookuptable.

In this nested family I moved the fittings top-typeA / top-typeB for better overview. When all works ok, I will move them back to the right positions.

In the host family the nested family (lijmring) is present 2 times. Each family-visibilty is set by parameters (richting_groot-klein / richting_klein-groot). This is depending if the pipe-size increases or decreases.

I included my famalies and project files.

In the project the view "Level 1 - FINE" displays the error. COARSE and MEDIUM are shown how also FINE should look like.

Hope I am clear? 😉

[ReneBogersREBO]

and the other files

[ReneBogersREBO]

the project

[L.Maas]

I had a look at it. I can not easily resolve it in the configuration as it is now. The nested components and then the different visibility on off setting seems to trip Revit up. As mentioned in my prevous post, this might create an unstable situation, causing this bug pop up.

While I doubt it, it also could be that this particularly family has an issue and when you rebuild from scratch it works ok.

What I would do is to look at the nested families. For example you could try to split the lijmring family in three separate families it removes one level of nesting which might help. You could even consider going one step further and just model the whole thing in a single family and not use nesting at all.

And of course consider if you need this level of detail in your model at all.

[ReneBogersREBO]

Still not working like supposed 😞

I changed some things but still the same $%*#)$%*#

The host family contains 2 diffentent families (for both directions a single family).

This is in REVIT2020. I also tried it in 2023, but acts the same.

My head is turning over on this one. gggrrr 😉

[dmiller_SCE · Accepted solution]

The behavior of the family does seem odd. Still, I think you can achieve what you need by moving the visibility parameters into the nested families and mapping them to the host family parameter. This will make working in the host family a little tricky as one of the nested families will not be visible depending on the family settings. Another option is to make the nested families shared families.  I have attached both examples for you. I hope this is what you are after. Option 1 is moving the visibility parameter into the nested families, and option 2 is just making the nested families shared. 

[ReneBogersREBO]

Hi there,

Thank you very much! @Anonymous: also thanks to you a lot!

I go for option 1, cause I don't want/need the nested shared.
It works like I want, but still confused why one of the nested families needed "NOT visible".
Or it's a bug in REVIT or it's a bug in my brains! hahaha

[ReneBogersREBO]

This is what it became! 😉