Announcement

Collapse
No announcement yet.

Nested family and Ref Lines

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

    Nested family and Ref Lines

    So, what is the secret of getting a nested item to align and track with a Ref Line driven with an angle parameter? I seem to be able to get it to work sometimes, and not others, I for the life of me I can't figure out what I am doing differently. :banghead:

    Thanks,
    Gordon

    EDIT: Now I did find this from the Revit Clinic blog. It certainly seems to address the issue, but there are two things in the video that I wonder about.

    1: He dimensions directly to geometry, not to ref planes with associated geometry. I am assuming this is just expediency for the demo, but in that case I would expect a comment to that effect. Anyone of the opinion that the old "Never parameterize directly to geometry" rule no longer applies?
    2: Nested parameters as type parameters? I could have sworn it was required than any nested parameter driven by a parameter in the host had to be an Instance, as you can be driving any combination of parameters and yet you only have one instance in the nested family. And yet this obviously isn't the case. Anyone know when this rule changed? And what , if any, ramifications there are?

    Thanks!
    Gordon
    Gordon Price
    Administrator
    Last edited by Gordon Price; February 20, 2011, 12:44 AM.
    Pragmatic Praxis

    #2
    Gordon,
    As for the angle driven nested components: I think this is the exception to the rule. I didn't get it to work with alligining to the refline either. Or, it did in the session I created the family (and I've got proof) but as soon as I save, close Revit and restart (or anyone else opens the family for that matter) it blows up. Don't know whether it's a bug or not.

    Check out the clock, it uses both instance and type nested parameters. For instance, the hours/minutes/seconds are instance based. But the dimensions of the legs are type based nested parameters. I honestly don't know when this changed, but you're not loosing it. I didn't know you could nest type parameters before this challenge too. I don't see any downside to using this feature, but I'm loving it! Nesting components always ment you would have to make all nested parameters instance based, even if you didn't want this. Now you have a choice...
    Martijn de Riet
    Professional Revit Consultant | Revit API Developer
    MdR Advies
    Planta1 Revit Online Consulting

    Comment


      #3
      You can use Type parameters *IF* the family isnt Shared. If its shared, you can only tie the instance parameters to the parent, since the types are driven from the project environment.

      Regarding angles and reference lines.... I tend to make the nested component WPB, and set its work plane TO the reference line. No constraints needed.
      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


        #4
        ahhh, and yet again my head is filled with more knowledge about the wonders of the Revit Universe... Thanks Aaron, that one slipped my mind.
        Martijn de Riet
        Professional Revit Consultant | Revit API Developer
        MdR Advies
        Planta1 Revit Online Consulting

        Comment

        Related Topics

        Collapse

        Working...
        X