@kleinnagelvoort which Revit version you are working on? maybe units conversion from feet to meters is required, please attach the script so I can troubleshoot it.
@Elie.Trad this script is created with Revit version 2022.
The location of the points are also strange, i dont know how these are gained.
WB_WIP.dyn (237.2 KB)
Would i need the location of the parent family to then localize the location of the nested family? Iam also not quiet sure how anyone should approach this.
@kleinnagelvoort it will work only if the nested family is a Shared family, I do not think it is possible to get the location of a nested non-shared family, maybe I am wrong:
The python script is found within the following link:
WB_WIP_1.dyn (31.7 KB)
@john_pierson any chance to fix the ʳʰʸᵗʰᵐ|FamilyInstances.RetrieveNestedComponents so it can get nested families out of families found in links?:
maybe. linked elements get very odd quickly. I would say to open a github issue and reference the code here: https://github.com/johnpierson/RhythmForDynamo/blob/8381eb1a24d49f0e53282ab47938c469e4340af7/src/Rhythm/Revit/Elements/FamilyInstance.cs#L154-L194
1 Like
By changing the family to shared it definitly changes something but still not in the right way.
Could it mather this family is nested into a nested family? both nested family’s are set to shared
@kleinnagelvoort Can you share the parent family ? 
@Elie.Trad am gonna have to ask the creator of the family if Iam allowed to share the.
I will get back to you after the weekend as the next couple of days are holidays here.
Thank you very much for the effort you already took.
1 Like
@Elie.Trad iam currently troubleshooting this with the content creator, i will keep this thread updated if there is any outcome.