Good morning.
I have the following problem:
I have obtained all the beam geometries from my document and I have obtained their geometries, then I have joined them into a single solid this solid I try to send it to revit as a massa instance family, then I am using the node “ꟿ FamilyInstance.ByGeometry” from the spring package but it returns an error and I don’t understand why it returns that message and what it refers to… I would be very grateful if you could help me understand what is happening and how to solve it… thank you very much.
What is the geometry type you are providing the node? It appears to be a mesh according to the warning.
Post lines 120 to 122 of the Python - need to see what the call is that is expecting a solid, and then confirm if it is a solid or if there is a conversion issue.
Does FamilyType.ByGeometry followed by FamilyInstance.ByPoint (using the new family type and the min point of the solid) work?
It may be that the import of the SAT is creating a mesh in Revit as the complexity of the geometry is causing a point to not place correctly leading to an open shell which cannot be used in the family environment.
You might have to settle for individual solids or multiple families… that said I question the need for this workflow as you already have elements, why strip out all the intelligence?
I’m about to make a video about Chinese traditional temple.I use importance of geometry created in dynamo and also I use geometry in dynamo to create revit family instance.
See the roof is imported directly from dynamo.I use OOTB nodes to do that.But it’s only an importance which has no material nor information.I don’t recommend that.
The rest parts are revit families belong to differen category like column,wall,doors…
So I’ll show the difference in my YouTube channel in the future.I don’t recommend import geometry directly from dynamo.
2 Likes
Here I leave an example of the geometry that gives me an error, thanks for your help
ERROR_GEOMETRIA.rvt (2.1 MB)
ERROR_GEOMETRY.dyn (18.6 KB)
¨Hi @AM3D.BIM.STUDIO you could try play around with k family insert and see if it could work, if i understand 
1 Like
Thanks for the suggestion but I don’t have the “K Family Insert” node in which package it is located…??? and I can use it in DYNAMO v.2.13
1 Like
Synthesize toolkit…guess it should work in all verson
Your Revit file is 2023, which means you should be on 2.15. If you’re seeing 2.13 you’re missing an update with some security patches. Best to install them ASAP - there is literally no reason not to.
I was worried this would be the case, but when you export and then import the SAT the resulting shape in Revit isn’t valid for joining a solid and as such can’t be used in a family as a form. If you export the geometry to an SAT and review the results you’ll see the ‘aligned faces’ with one normal pointing towards the other, Revit won’t permit that as a solid.
You may want to look into a custom importer. There are no certainties that you can make this work either, but if you do look at the brep builder or the tessellated shape builder classes if you go that route.
Alternatively you’ll have to look into generating each of the solids in the family (remove the union function), and letting each portion of the solid live in the family as an individual form element.
Thanks for your comment… but tell me what the process is to be able to update to the versión you mention. …¡
Which? I can try to explain one or the other in detail so you can try to build them out. However both are fairly involved and more than I have time to build at the moment.
Good morning.
I have the following problem as the NODE “ˢᵀᵒᵒˡˢFamily.KFamilyInsert” gives me the following error, how can I fix it.
I am using DYNAMO v.2.13
Thanks
Dynamo 2.13 indicates you’re in Revit 2023.0 as Revit 2023.1 includes the update to Dynamo 2.16. Revit 2023.0 means you’re missing multiple software updates (current is 2023.1.5), including at least one publicly disclosed security advisory.
Update Revit to get current and see if that resolves the issue.
If you need IT to get the update installed forward them the link above and they will likely take action quickly to get everyone updated.
1 Like
yeah seems you are in in a old version there need upgrade…but for synthezise try install version 12.7.5 for 2022/2023 not sure but try it
Good morning.
I still have the same problems when sending the geometry to REVIT as a mass type object, the “FamilyInstance.ByGeometry” node fails to convert the geometry to REVIT and instead returns a message that the object is not a geometry but a MESH, in that sense I would like to know the following.
1° What method can I use to identify which objects are a mesh and thus be able to separate it and give it another treatment or see the geometry corrections.
2° I was trying to download the Revit 2023 update to the latest versions but I have not been able to find the download file.
Thank you very much, I look forward to your comments.