yes or with shared depends, but all should be doable in one run, ..play around with it
Try FamilyType.ByGeometry instead, and wire it into the familyType input of a FamilyInstance.ByPoint node.
I find I get better error reporting this way, and you have better control over the content long term as it’s not a directshape.
1 Like
right, i had bad experience with direct shape before, besides, FamilyType.ByGeometry is “updated version” of direct shape if i recall correctly
Not necessarily updated - it builds the shape in a different way as it’s in the family environment though, which makes it a bit more robust. 
1 Like