I have a family containing geometry that has it's visibility associated with a Type Parameter. This family is nested into another family, but for some reason the button to allow this type parameter to be associated with another type parameter of the host family is missing. I was not aware that there would ever be an exception to this functionality?
Nested families have to have an instance parameter assigned to them.
The only family that this works for being a type are profiles.
Hi..
1. Parameters can be mapped in a few ways.
a. Instance Parameter ( Once the family is nested in another Revit Family, or loaded in the project, particular instance
parameter can be mapped to Local Value/parameter)
b. Alternatively, you can use the " Shared Parameter". There's only one Shared Parameter File ( notepad )
If you are using this feature then Shared parameter helps... The shared parameter can be used in many families and
used for company-wide consistency of parameters.
c. Also, make sure when there is nested family.. keep " shared " switched on... otherwise Revit doesn't allow those
particular nested family to assign any parameters..
Shared " keep switched ON " for Nested family..
@Corsten.Au wrote:
c. Also, make sure when there is nested family.. keep " shared " switched on... otherwise Revit doesn't allow those particular nested family to assign any parameters..
This is not true...Shared makes the family available in the project as well as the family it is nested in. You can make a family nested and assign parameters if it is not shared.
thanks for that...
Am sure you know what you are talking.
There is no blanket rule cause there's gentle difference between
1. Revit Family, loaded in another Revit Family. and
2. Using a Revit Family as Nested Family...
To clarify what I was saying in this...
Shared family and nest family..
I'm not sure I'm following either one of you guys. Type and Instance can be associated. Shared or not shared doesn't matter. My guess is that the parameter is controlled by a formula in the nested family.
Yeah, @barthbradley it's a vast topic... impossible to cover in few threads.
I think OP should just go through a couple of Solved Post to get the idea.
I found this interesting... There are so many ways things can go wrong while editing Revit Family..
many posts are written and solved by you...
https://forums.autodesk.com/t5/revit-api-forum/retrieve-nested-families/m-p/8190955#M32748
https://forums.autodesk.com/t5/revit-architecture-forum/nested-family-woes/m-p/8473027#M223063
I get where you are coming from now, @Corsten.Au. You're right. I'm wrong. Sorry.
... I just read some of the threads you posted Links to, and indeed, many of them are ones I replied to. Some of my replies were even marked as the accepted solution. I guess that proves it. I'm getting dumber -- not smarter. If this keeps up, I'll be a "newbie" again in no time. HA!
Revit crashes when self-referenced....
I can see where @barthbradley you are going... ![]()
The Curious Case of Benjamin Button...
My only point was a nested family does not have to be shared...but if you assign a family type parameter to the nested family then it is best to be shared, else all families have to be loaded into the parent family and you pray nobody purges your project. (How my doors were created when I first started Revit 15 years ago...shudder...I did some stupid things back then that I would smack myself today for doing it that way)
@barthbradley...yeah...forgot you can associate parameters under the Type Properties. I'm so used to just having a single type, like door frames and panels, that I forgot to look one step further than just the Properties window.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.