Digitally signed app
The IFC for Autodesk® Revit® 2019 contains up-to-date improvements on the default IFC import and export capabilities of Revit contributed by Autodesk and our Open Source contributors.
While this app is not necessary for IFC support, it is recommended that users that depend on the quality of their IFC files download this app and keep it up-to-date, as new enhancements and defect fixes are added, for more information on IFC, please visit the building SMART website (buildingsmart.org) or the Revit wiki (help.autodesk.com/view/RVT/2019/ENU/?guid=GUID-6708CFD6-0AD7-461F-ADE8-6527423EC895).
Informationen zu dieser Version
Version 19.5.0, 06.10.2021
See the full set of release notes here: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v188.8.131.52
Zum Schreiben einer Bewertung anmelden Technische Hilfe erhalten
Old and this export does not coincide coordinates
everytime i need to import an IFC in revit 2019, i need to uninstall the app otherwise revit will not import the ifc file.
Any idea how to solve this issue?
The last two checkboxes (The ones deal with ifcType and ifcEntity) on the Advanced tab of "Modify Setup" does not seem to stay on after an export.
Is there a reason for that?
On version 19.3 of the exporter we come across an issue at the end of the export where warnings appear asking us to ungroup particular groups in our models because changes to groups are only allowed in the group edit mode. This did not happen in v19.1 so I am wondering why this is the case in this version. The instance parameter IfcGUID cannot be accessed through the Project Parameters to allow it to vary by group instance (assuming that is what is trying to be accessed). What are the implications of clicking cancel when we receive this warning (the IFC still exports OK)?
Correct, just faced the issue to. This needs to be corrected, and the IfcGuid parameter should be "Vary by Group"
I'll file an issue for this - sorry I missed this the first time it was reported. There should be no real issues with cancelling.
I'm looking into this for Angel. I can't reproduce that with a simple file with groups. Could you send a small rvt project that shows the issue? thanks.
Hi Andrew, yes I shall send it to Angel. Many thanks
Hi, is there any update on whether this will be fixed?
Hi, is there any update on whether this will be fixed?
Good app, but you must acquire some knowledge about IFC and the exporter itself to understand why it's not working or why it's so slow! It all depends on the user that's exporting the Revit file.
Low understanding/effort = Low quality guarenteed.
It seems it is not possible to export Design Options. For certain projects it's an excellent tool and not being able to export to IFC other design option but the primary seems odd.
Unfortunately, only the primary design option is currently supported.
What is the differance between V 184.108.40.206 and V 220.127.116.11 ?
My contractor Submitted the IFC file with version V 18.104.22.168 but I can not find that version here..!!
I believe that might be the "vanilla" IFC code from Revit v2019.2.
Ideal for exporting files to 3rd party contractors
Very useful but why it is not integrated directly in the Revit insall?
This is included in out of the box Revit. This only allows for updates after the software has been released.
The plugin should not export, before the Revitworker is finished calculating.
We are use Structural Connection.
Fairly quick export.
So, linked in a model and aquired coordinate system, then tried to export to ifc. Then tried to link ifc into earlier version of revit (2016) for coordination, and will not drop into the right location, no matter which coordinate export setting I choose (I've tried them all). Project is not ready to upgrade to 2019, but realise this is the obvious answer. The 2019 user can't downgrade to 2016, so we are in a bind. Have to get the ifc export to work for coordination workflow, which this is holding up. Any ideas? Thanks.
Have the same kind of problem. When exporting to IFC with "Current shared coordinates origin" the rotation becomes wrong, its true north instead of project north or if its vice versa. This problem was not in 2018 release of addin and/or Revit 2018.
I thought I mention my observation here. I have a similar issue as Klas described. I'm using Revit 2019 of course as this is about IFC 2019 plugin. The situation with problems is: I think plugin is working correctly to some extent: I have exported IFC model with IFC 2019 plugin - Project Origin set to "Current shared coordinates" and loading it into Navisworks. - Navisworks Application Menu - Options - IFC - Revit IFC - checkbox off - model is loaded to correct Shared coordinate X and Y but Z is 0. Orientation is correct. - Navisworks Application Menu - Options - IFC - Revit IFC - checkbox on - model is loaded to correct Shared coordinate X, Y and Z. Orientation is incorrect. Instead of True North, a Project North is used. I have exported IFC model with native Revit IFC export and loading it into Navisworks. - Navisworks Application Menu - Options - IFC - Revit IFC - checkbox off - model is loaded to correct Shared coordinate X and Y but Z is 0. Orientation is correct. - Navisworks Application Menu - Options - IFC - Revit IFC - checkbox on - model is loaded to correct Shared coordinate X, Y and Z. Orientation is correct. Conclusion: Navisworks implemented a fix for the incorrect position of IFC file export from Revit. If other software (like BIMsight) is used, using IFC file export from Revit with a plugin or native IFC export, IFC model will be positioned to wrong Z coordinate. Unless the other software has "Revit IFC" fix implemented. IFC 2019 plugin has no good use to me. Please, correct me if I'm wrong.
We use ifc-file from Revit to generate materiallists and price calculation. The program for we use for this calculation have "lost" the connection to beams, colums, doors, windows and all types of walls in ifc files from Revit 2019. We have to use 3 days to reconnect all the objects. I asume this accurs due to new naming in 2019 versjon. If this is correct then why, and can we expect this type of change often in the future?
I'm sorry I missed this before. Can you send a file to revit-apps with a more detailed description of the issue? I don't know what renaming may have happened in 2019, and we don't expect to do that often.
When we export our buildings we have to assing every element on a floor to that floor (ground floor, first floor, etc.), by modeling them to a certain building story in Revit. Is there a way we can add a parameter that overrides the floor it's exported to? For instance a wall is set on de building story First Floor but for some reason in the IFC we want it to be assigned to the Second floor without changing de level settings of that element in Revit?
Similar to how you can overwrite the name of a family with the parameter IfcName.
This isn't possible yet but it is something we are working on.
This plugin works only in revit is displayed in english. If i use revit in ex. italian the plugin saves an empty IFC file. It has been this way for past couple years... Please fix it!
There is a workaround for this. Go to R > Export > Options > IFC Options. Look at the name of the IFC export classes file at the top. Find it on disk, and delete it. Then press the "Standard" button. This will reload the file in your local language, and export will work.