I have a Door Family (1) which has 7 Types.
That Door Family contains a Shared Nested Door Family (2).
That Door Family contains a Shared Nested Generic Model Family (3).
When i use FamilyInstance.ByPoint to place the Types from
Door Family (1) in my project it creates a ‘ghost’ duplicate of the
Shared Nested Generic Model Family (3)!?! Which lead to warnings.
What causes this? Is this a bug?
How can i prevent this from happening?
Do you get this warning just by placing the Door Family (1) in Revit normally? It sounds like it’s maybe an issue with the third family being shared by both the nested family and the original family, leading a new instance of the door to contain two shared instances of the double-nested family.
It looks like your script create 7 new instances but you only have warnings for 4 of them. Can you identify which instances are causing the warnings and maybe determine if there’s something different about those 4?
Can you recreate the issue with a basic example family using the same structure?
What do you mean by this. This Family was pretty basic.
The Generic Model is controled by a Visibility State. It is a synbol for Fire Rating
and Self Closing .It is only turned on for some Types.
In this case the Types with FR30 in their name.
Also, maybe more then one duplicate gets created?
Some IDs appear in multiple warnings.
Only the ones in warning #3 are unique by the looks of it.
Can you either share the families in question or create a super basic version of a family that works in the same way? We can only guess without seeing the family.
Can you determine which instances are creating the duplicates that show up in the warning box? I would expect 7 instances of the same family to cause 7 warnings for duplicate elements if the issue was with the node creating the elements.
Fact remains it is ONLY an issue when the Family is placed using Dynamo.
I’ll upload the orignal Family for now and will strip it down (simplify) after
and upload a stripped down version afterwards
(will probably be tomorrow - been a long day already ).
Okay. It is 100% how the Family is build in combination with Dynamo.
No issues with the stripped down version with just one type and
the Generic Model visible.
I know have to figure out when or why it goes wrong .
Thanks for pointing that out @Nick_Boyts.
I thought that would’t be the cause. Should have known better .
EDIT3
So it might not be the family. See later posts.
I was able to run the script with the original families in a new project with no issue. See if you have the same luck. I’m guessing you’ve just run the script too many times or have other instances of some of those families already in the project.
I also need to test it with another family having
the same shared nested families i guess.
That may be the root of the problem.
Got some more digging to do.
Check element bindings first… The ‘previously placed’ shared nested instances might be getting orphaned during binding updates, which would be a new bug for me.
@jacob.small
You might be on something / be right. It might got something to do with element binding.
When i run the script with Family loaded into a new (EMPTY) project then there is no issue.
When i run the script with multiple Families sharing the same Shared Nested Family into a new (EMPTY) project then there is no issue.
However, when i run the script a second time the Families get placed, BUT the previous
placed Families get removed (b/c element binding).
However i didn’t get the duplicate issue in that new (EMPTY) project.
I loaded every Door and Window from my original project and loaded them into
a new (EMPTY) project. Again no issues.
Als good to know;
I am testing with simplified script of (my original script is way more complicated).
So my guess the problem got something to do with my original .dyn or
the project (or a combination of).
My orginal script places all Families, which are actually placed,
…on x rows puts them
…on the correct Workset,
…on the Phase
…creates Sections for each row
…Tags the Doors and / or Windows.
EDIT
Tested my orginal script in the new (EMPTY) project. Again no issues.
Couldn’t test everything. So only if the placement would give me issues.
So no tagging and some other stuff.
The bindings in your .dyn are unique to particular GUIDs in particular projects… as your next project won’t have the same GUID as the one which is already bound you can’t ‘recreate the issue’ without starting over and recreating the entire process which lead to the issue. I’ve tried a few things with a sample file to do so, but I can’t manage to do so (congrats you’re in uncharted territory somehow). Any ‘new file’ that reproduces it will require you do whatever was done before.
And so to reproduce the issue and help directly we’d need the stripped down .rvt file itself - yes the actual project with the families already in it. Nuke all other model elements (i.e. delete all [walls, floors, levels but one, views but one, materials] and purge 3x, ect.). Then post the .dyn and the .rvt.
That said I don’t think we need the file. Clear out the Element Binding and then see if you can reproduce the issue.
I made a detached model of the original
(don’t know if that would matter for the test).
Removed the bindings in the .dyn.
Ran it and i got the issue again.
Also gonna try it on a project i never
used my .dyn on yet.
.
).
.
.
.
