I'm trying to change a component in a family by using a formula.
Simply put I'm trying to create an IF statement where it would result in changing (or not changing) a component into an other.
I however do not know how to "describe" a specific family type in a formula.
Solved! Go to Solution.
Solved by ovidiu_paunescu. Go to Solution.
Maybe this is what you are looking for
https://www.linkedin.com/pulse/add-choices-your-revit-families-family-type-parameters-paul-aubin/
That is the thing I want to adjust, but I want to adjust it with a formula rather than just clicking and selecting another one.
This should do the trick
Also here's a useful link to overcoming inconsistencies when using formulas
Here's a quick example of this:
Is the idea that you put all instances in the same position and set some on invisible based on an IF statement?
Yes, that's the idea.
The IF statement can be about any family parameter (e.g. the width of a framing element).
If you don't need an IF you can just save the family types with the Yes/No parameters checked/unchecked.
Tags is one example where multiple labels are overlapped and the visibility is controlled by Yes/No parameters.
I can now turn on and off the visibility of certain elements but it still shows them, I have checked it in projects as well, but that doesn't matter (as I think I remember to have read that everything is always visible in the family editor). Next to that I'm getting the issue that it says there are two similar elements are overlapping, which does happen, but one shouldn't be active.
Any idea what I'm missing here? Thanks in advance!
You can use preview visibility to view the elements like they would look when loaded into the project.
More on that here:
If you're using conditions to control the Yes/No params, check that you have defined them correctly.
You can ignore errors of overlapped elements in the family editor (if they are shown) if one of the element will be hidden
Check out the following information on controlling the visibility inside families:
I managed to solve it, the trick was to set the visibility within the nested families instead of the "main" family file.
Thank you!
Can't find what you're looking for? Ask the community or share your knowledge.