Announcement

Collapse
No announcement yet.

Workplane based families not maintaining height

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Workplane based families not maintaining height

    I made a whole new series of cabinets that are workplane based and not hosted to anything. When I place them in a group their heights are completely inconsistent from group to group.

    I had placed a parameter to control the height above floor for the upper cabinets. The most common distance the cabinets move is the same as that parameter. The field that keeps changing is "Offset". But it is not always the same as the height parameter. I've seen it be as much as 3 floors worth of height difference.

    Would removing the parameter to control the height above the floor fix this? It is an instance based parameter.
    ​My ID was stolen. Now I'm only called Dav

    #2
    By chance, are they linebased families?
    Alex Page
    RevitWorks Ltd
    Check out our Door Factory, the door maker add-in for Revit

    Comment


      #3
      No they are not. It is all casework with nested casework families
      ​My ID was stolen. Now I'm only called Dav

      Comment


        #4
        Originally posted by DavidLarson View Post
        No they are not. It is all casework with nested casework families
        Get rid of the workplane based function. You say these families aren't hosted to anything but they are. They are hosted to that workplane you mentioned. Groups will break and/ or do stupid things unless you put a second reference (plane) in the group and host your families to that. Too complicated imho.
        Leave that geometry hosted to the reference level inside the family and they should copy level to level fine in the project.
        If you have complex geometry that isnt built relative to family reference level you can nest into another family (with linked parameters) to get everything to move together.
        Then the hardcoded offset parameter will work as intended.
        Last edited by elton williams; April 28, 2017, 09:08 AM.
        There are no stupid questions, only stupid people

        Comment


          #5
          Most of my my families are workplane based so I'm sticking with that. Removing the height parameter worked. Now everything is working as intended.
          ​My ID was stolen. Now I'm only called Dav

          Comment


            #6
            Hate to say it, but this is only a temporary fix. If you change the heights of the levels the problem will, I bet, come back. And if you use them on another project with groups, the same thing will happen.

            Non-system hosted families don't play nicely with groups. Sometimes they're fairly easily fixed. Other times, like with line-based families, the only solution is to start over.


            Sent from my iPhone using Tapatalk
            Greg McDowell Jr
            about.me/GMcDowellJr

            Comment


              #7
              The problem I was having was hosted cabinets kept moving. One day they'd play nice, the next it would be 90 degrees and thinking it was hosted to a wall that had nothing to do with the group.
              ​My ID was stolen. Now I'm only called Dav

              Comment


                #8
                Workplane Based is not going to work (long term) with Model Groups. You can stick with it if you want, but youll continue to face (what people refer to as) "the problems revit has with groups."

                My cabinets are all non-hosted, non-workplane based, and they work perfectly with Groups in all cases.
                Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
                @Web | @Twitter | @LinkedIn | @Email

                Comment


                  #9
                  One further clarification...When you load a non-hosted family into a project it is still associated to a project level, but levels are not reference planes or surfaces. The hardcoded Offset paramater works by offsetting the family's ref. level from the project's associated level. Any further geometry manipulation you want to achieve should be based of the origin x,y,z reference planes within the family as the point that they cross is considered the origin point of the family.
                  I have complete kitchen families loaded with nested casework families for use in resi highrise, they often go into mirrored/rotated groups and it's never an issue.
                  There are no stupid questions, only stupid people

                  Comment

                  Related Topics

                  Collapse

                  Working...
                  X