Announcement

Collapse
No announcement yet.

Shared Paramaters in Families

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

    Shared Paramaters in Families

    I've been poking around the door styles that Beck has posted on bimexpert.com and am a bit lost on the shared paramter implementation. Is there something I could read through to explain it a bit more indepth or even a video or 5 - in particular the how-to side of it? I understand it in theory but am not having much luck implementing it. To wit - I attempted to make a family with a hosted panel (cabinet) and after inserting the door into the base the shared portion doesn't work. However if I insert one of the Beck doors it works fine so the issue is obviously mine and lies in the creation of my panel family.

    Thanks :beer:
    Revit for newbies - A starting point for RFO


    chad
    BEER: Better, Efficient, Elegant, Repeatable.

    #2
    It sounds like you're confusing Shared Parameters with Shared (and nested) Families. Shared Parameters are primarily, and if I'm wrong I'm sure someone will chime in, for scheduling and tagging purposes in the project. Nesting a shared family allows you to tab through the host family for tagging and scheduling purposes in the project. Not sure if that helps but it's a start!
    Greg McDowell Jr
    about.me/GMcDowellJr

    Comment


      #3
      Unless I'm completely backwards they were shared paramaters - the paramater names are all as such: Panel: Height, Panel: Width etc. I don't believe you can add a : into a paramater name unless it is shared.

      I'd also appreciate some reading on shared families as well since I might be in over my head at the moment... :hide:
      Revit for newbies - A starting point for RFO


      chad
      BEER: Better, Efficient, Elegant, Repeatable.

      Comment


        #4
        Hey cellophane-

        Just as an FYI, the doors we have on BIMExpert.com are very old, from our 2010 library... which was entirely started from the ground up for 2011. Those are posted here, somewhere. They are shared parameters in our door families, yes. They are in Shared Nested Families, as well, and are all instance parameters. What might be tripping you up, is:

        If they are Shared parameters, and the family is shared and nested, they cant be Type parameters if you are trying to tie them to the Parent Families parameters. Shared Nested Type parameters are controlled in the project, not the parent family. That might be why they work for us (instance) and not for you (type).

        Just a guess!
        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


          #5
          Thanks

          I'll poke around some more when I have some more free time. It most likely is a Type / Instance issue - I don't recall what I used off the top of my head when I was experimenting.
          Revit for newbies - A starting point for RFO


          chad
          BEER: Better, Efficient, Elegant, Repeatable.

          Comment


            #6
            Aaron...

            Are you saying you can't use a type parameter to control the Shared Nested families parameters? 'Cause this is what I'm doing with our door library. Most of our parameters controlling geomoetry are Instance in all the nested families until they get to the parent where it becomes a type parameter. I use this to then setup the family types, which drive the nested geometry.

            You made a comment in your class at AU, saying you think all doors should be driven by instance parameters. Could you expand on why you think this?

            Thanks
            Darryl Store - Associate (BIM)
            [email protected]
            Twitter: @darrylstore

            Comment


              #7
              Not what im saying at all. Im saying if the OP has Type parameters IN the Shared and Nested families, they cant be tied to the parameters of the parent Door Family, because Shared and Nested Families have their Type properties controlled at the project level, not the parent family level.

              Instance versus type... Very long discussion, and im short on time today. But i stand by it.
              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


                #8
                Ah, gotcha. :-)
                I'd still like to hear your thoughts on the instance vs type discussion. Blog post? ;-)
                Darryl Store - Associate (BIM)
                [email protected]
                Twitter: @darrylstore

                Comment

                Related Topics

                Collapse

                Working...
                X