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
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
Comment