I implemented ALL possible healing methods in Dynamo to help fix the geometry prior importing it to Revit… You may try to use the node called “K-Family Import” from Synthesize toolkit package…
#REVIT FAMILY SURF CODE#
I tried a lot to convince Revit team by undo of what they did until they make the new code (healable to imported geometry) and has the ability to import same wide range of geometry… but what’s made has been made… and Autodesk is… well Autodesk…Īnyways, to solve your issue, and hopefully many others. *Even if you imported (many) forms in older Revit versions, and opened them in 2022, they will disappear, or behave strangely… etc Now after Autodesk removed that old branch of code, we can no longer import the wide range of geometry that we could through the API as before… Healing has so many techniques… (Mentioned later in the post) So healing is basically detecting those errors and re-creating the surfaces and stitching them on the fly… What is healing ? well, basically, the source of troubles in Revit is it’s small geometrical tolerance, around 0.07mm … when a geometry has a surface that has an edge, of this dimension… and that edge is stitched to another one… it cannot simply import it… (Many other complex situations as well) Why ? well, the old branch of code did lots of healing and fixing to the geometry prior imporintg it, but has resulted (sometimes) in an undesirable performance impact. Well, basically a decision was made to remove an old branch of code (document.import) and replace it with (ShapeImporter) code…īenefits & Consequences ? well, better Revit performance, consistent import units… but LIMITED range of importable geometry… Thanks for the tag knew this issue will start affecting many people by time… Import it to a Revit 2022 family and you get “Mesh”. sat into a Revit 2020 family and you get a “Solid”. sat file generated out of Revit 2022 if anyone (…“cough” Autodesk employed “cough”…) wants to test and confirm this behavior. My suspicion (and this could only likely be confirmed by someone on the Revit development side) is that there was a “face count” limit placed in Revit 2022 that automatically makes that import as a mesh if the number of faces exceeds some threshold limit - leaving us kind of without much option except a clunky workaround of going back to the old version that worked in a much friendlier manner.īelow is a link to a. sat will be a solid in Revit 2020 but a mesh in Revit 2022 (in some instances). sat has changed from previous versions in that the same. sat into a DirectShape in the Revit Family or something that Revit is using to export the. Seems very difficult (getting Dynamo to operate on multiple versions of Revit simultaneously).īottom line - something either in the methodology that Revit is using to convert the. That would be awesome if someone could come up with a fix - but it would surely be complex because it would require the instance of Dynamo that is running in Revit 2022 to fire up an instance of Revit 2020 and do the family creation in that version, then save the family and have it then load into Revit 2022.
0 kommentar(er)
