Announcement

Collapse
No announcement yet.

Visibility parameter and nested family: bug?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Visibility parameter and nested family: bug?

    Hi all,

    I have encounter an issue with a shoring equipment family we work on in my office. I won't share it here (you may understand I can't) but:

    it has 3 levels of nested elements (site category), and the problem is in the last one when we want to apply a visibility parameter to a nested (second level) component; it simply doesn't work. the element is not grayed in the family editor, and is visible when loading in the project.
    we tried it on 2 laptops, same result.
    the only way we found to solve it was to apply a visibilty parameter in the second level nested element, and track it in the final family. this way it works.

    Are we missing something? is this a normal behavior? first time for us BTW.... Thanks.
    Julien
    "Au royaume des aveugles, les borgnes sont mal vus!"
    P. DAC
    Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/
    Tags: None
    #2
    Is it possible to put in a "dummy" family for testing? Strip out all sensitive matters and replace with some random solids.
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    Comment

      #3
      Originally posted by jbenoit44 View Post
      ...
      Are we missing something? is this a normal behavior? first time for us BTW.... Thanks.
      That is the normal behaviour. You did the right thing, tying the object to a visibility parameter in the second level, then tying that parameter to another one in the last level.
      Freelance BIM Provider at Autodesk Services Marketplace | Linkedin

      Comment

        #4
        thanks for the answer Alfredo. any idea why it is like that? software limitation?
        Julien
        "Au royaume des aveugles, les borgnes sont mal vus!"
        P. DAC
        Follow me on Twitter @Jbenoit44 - Blog: http://aecuandme.wordpress.com/

        Comment

          #5
          No, it's not a limitation. Imagine this situation: the family that is nested at the second level has 2 extrusions. In the final family, you just want to hide one of the extrusions of the family that is at the second level. Then, having the ability to use individual parameters tells Revit what to hide and what not at the end. But those instructions (such as visibility parameters) have to carried until the host. The final host family is the one that Revit "reads" in the project. Any other instructions not carried out up to the last level are left behind, not "read" at the end. Oops, I hope it makes sense.
          Freelance BIM Provider at Autodesk Services Marketplace | Linkedin

          Comment

          Previous template Next

          Related Topics

          Collapse
          Working...
          X