Stl Exporter For Revit Download
Dibe Naro
Now I have assisted a user that got this problem. The user works in Revit 2020. The project is places on BIM 360. He used the built-in IFC exporter but it have some limitations so we upgraded to the latest relese on GitHub, -ifc. After the installation Revit crashed when he tried to use the Export IFC. I renamed the file 0_Enscape.addin in the 2020 addins folder and restarted Revit and now it works. On his computer 2020 is the latest Revit version and the Enscape version is 3.2.
A client of ours uses Enscape, and had issues when using the IFC-exporter as well. It doesn't seem to be localized to only 1 Revit version however. My client has this issue in Revit 2021, and I've been able to reproduce in both Revit 2021, and 2019 (currently installed on my machine).
The crash seems to happen when the IFC-exporter tries to open a settingsfile from the IsolatedStorageFile. When it goes into line 25, it gives the CLR-crash that John described. Because even though the file-reading fails, it should be catched by the Try-catch block and return a new "Rect" object.
- Now what seems to happen is a Stackoverflow error after failing to read the settings file by the IFC exporter. It ends up in the Enscape.Common.dll where it get's in an infinite loop. I presume some kind of Revit event handler that isn't handling some edge-case correctly.
- As we could see in the stacktrace, the FirstChanceException handler is added here, which will be thrown on any exception within the AppDomain, which is kinda dangerous in my opinion. Because every plugin in the whole Revit installation can throw this event, which will end up in Enscape event handler. So I can only assume that this would cause conflicts with more add-ins than just IFC-exporter.
MartijnKalecSoftware , that sounds exatly like the issue we have. We run all the revit versions from 2018 to 2022, depending on the project, and it seems like it appears on all the versions. If we rename the Enscape .addin (manifest??) for one version it seems like the issue is fixed for that version, but it remains on the other versions.
Basically what seems to happen is:
- Another addin besides Enscape throws an error, that it normally would handle by itself. In this particular case, IFC-exporter tries to open a file, that's not in the system.
The reason for this is that the Enscape addin is "subscribed" to any event where an error happens within Revit, even other addins. And Enscape didn't handle this certain case with IFC-exporter properly, which makes sense, because you can't really know what you are going to get, when another addin gives you an error to deal with.
I already talked to Autodesk support about it and talked it about the IFC Exporter developer with it and nobody can really understand why its like that on my PC ( Even after giving literally all Revit related folder administrator rights on Windows it still crashes when launching revit not as Admin)
I am excited to try out the native .rvt export option in AC 25, however, I sent a model to my engineer and they reported back that the whole project opened with only 1 level in Revit. The full model is visible, so it is not just exporting one story. I looked, but didn't see any settings related to this in the save options. Does anyone know if this is just the way .rvt gets saved, or is there a way to include those stories?
If this is just how the exporter works, has anyone developed a workflow to exchange the stories? My initial reaction is to default back to IFC to set up the story levels in their Revit file, then import the .rvt into that. Any thought?
Thanks everyone.
hey, if they are using revit, they can author it how they like. Just ask them to send a "ducts only", "equipment only", "outlet/switch/fixture only", and "waste/supply plumbing only" files. They should never be sending files that have your walls back to you. This way you can import each IFC separately, put them on their own layers and isolate them (you could even ask to separate supply and return air for GO based color coding). As long as your walls are classified as walls/slabs as slabs/roofs as roofs/etc, and they are using the IFC for Revit importer from Graphisoft, they should be able to attach using whatever families they are familiar with. Its on them to isolate out the parts and get you a file that YOU can use... goes without saying, just make sure your building doesn't get repositioned from it's 0,0,0 relationship, then the IFC for MEP/Structural/etc. all come in and snap right into place... you'll really be screaming along when you have find and select criteria baked into your template to semi-auto run collision detection between those IFC files!
However, when we talk about site plans, a 1:400 would be desired therefore a 250% scale in cura would be ideal, however the site is a little too big for that, so, we will go back to revit and readjust with the section box.
I am a pix4d, licensed drone pilot with a surveying/civil engineering company as well as having my own business designing residential and light commercial buildings. I am also a certified 3d laser scanner technician and very familiar with point clouds, revit, and civil 3d.
What we have done in the past as well as the present, is to process the files and export the DTM (for surveying), and a point cloud for modeling into revit or civil 3d. once the point cloud has been exported as an LAS file, we then bring into recap and save it as a recap file. from there, we use or attach a recap file (which is a smaller file than the LAS) to use in cad and easier to handle than the LAS file. large LAS files can be cumbersome and bog down cad.
Is it possible to export revit elements to .SAT by first converting them to Geometry then exporting this Geometry. By not using a view. With Dynamo this is possible by converting the element to geometry using the Element.Geometry node, then convering it to .SAT with the ExportToSat node. No seperate view is needed for this export.
@eric.craft.MH we are prepping a new release that may remedy this problem, we found some issues with how the paths of linked models were being treated by the exporter. Crossing my fingers that it passes our internal review process soon and reach you this or next week!
08ab062aa8