02 May 2019

Revit IFC v19.2.0.0 Open Source Code Released

Autodesk’s Angel Velez mentioned on Twitter the Revit IFC 2019 source code was just released with many bug fixes and 2020 is coming.

“The long awaited Autodesk Revit IFC v19.2 released ((link: https://bit.ly/2PKzt9C) bit.ly/2PKzt9C)! Lots of bug fixes, and working on getting 2020 open source out the door also (with even more fixes, many of which will be back-ported to v19.3). App store soon.”

RELEASE NOTES 19.2.0.0

General:• This is generally a bug fix release with some new IFC functionality.

New Export Functionality:• IFC Exporter now supports IFC Spatial Container assignment override using IfcSpatialContainer parameter. Valid values are: "IFCSITE", "IFCBUILDING", or name of the Building Storey• Improved detection of Door operation type using the 2D swing symbol (arc). The improved version detects range of angles (not limited to 90, 180 or 360 degrees only)• Added support for IfcCivilElement• Replace IfcRelConnectsPortToElement with IfcRelNests for IFC4 export as recommended in IFC4 specifications, allowing non-IfcDIstributionElement to participates in the connectivity• Added support for RampFlight and Run from generic models or family representing more complex Ramp for export to IfcRamp and IfcRampFlight• Added various property Calculators• Improve performance when exporting a large mesh• Enable IFC Property Templates• Allow multiple Property Template mapping from txt• Projection improvement• Enable site and project property creation• Utilize Site GlobalId method• Add multilanguage support files for German language (DE)• Provide a complete list of all Shared Parameters used by Revit on export including ALL properties defined in IFC PropertySet Definition for both Instances and Types. The lists are included in the installer and will be placed in the install folder: IFC Shared Parameters-RevitIFCBuiltIn_ALL.txt (for the Instance parameters) and IFC Shared Parameters-RevitIFCBuiltIn-Type_ALL.txt (for the Type parameters).• Improve consistency for setting the object direct attributes, support IfcObjectType[Type] special parameter to drive instance ObjectType parameter from the Type, update the shared parameter definition files (now for [Type] parameters we will also maintain the GUID as long as it remains)• Incremental work towards IFC4RV 1.2 MVD

Export Bug Fixes:• Consistent ExportAs entity and its PredefinedTypes• Export fails when there is no associated Plan View to a level• Additional fix for error getting 2D data when there is no Level associated to the FamilyInstance• Various fixes related to missing geometry and export failures• Fixed performance issue in IFC2x3 export due to error in creating types• Fixed issue with slanted Pile• Fixed issue related to element that is split into parts• Improvement in handling level of Part Override• Some improvements on classification (issue #31)• Improve voiding of IfcMappedItem representation (issue #9)• Fixed issue on Composite curve tolerance (issue #5)• Fixed issue where element is still exported even though it is set to not-exported in the mapping table• Bugfix for incorrect cylindrical hollow core Beam export in IFC4RV• Fixed for issue #51• Bugfix based on Pull request #52 for MEP connector, and a few clean-ups• Fixed minor issue to ensure generic element exporter will generate consistent GUID for the instance• Fixed issue when OverrideElementContainment is used but the Site does not have site geometry (from Topography surface)• Add support of OverrideElementContainment also for SpatialElement (Room/Space/Area). This enables export to place IfcSpace directly to IfcSite for example, which is useful for outdoor spaces• Refactored the handling of valid entity and type and fixed a few defects related to it (Github issue #68)• Fixed issue with Stair Landing that is offset far away from the supposed location• Fixed issue with missing geometry when assigning IfcExportAs to the Spatial Element (Issue #23) However, in IFC4RV or DTV, there is a fixed list of valid entities that will be enforced, entity such as IfcExternalSpatialElement will be exported as IfcBuildingElementProxy.• Fixed performance issue when there is a large triangulated geometry for export to IFC4RV• Fixed issue of exception raised during export when "Export schedules as property sets" option is selected, and the model contains ViewSchedule from the template• Update Source/IFCExporterUIOverride/IFCExporterUIWindow.xaml.cs (issue #59)• IFCBooleanOperator.Union don't work! (issue #32)• Fixed issue in exporting IfcBuildingElementProxy that assigns an invalid enumeration for CompositionType in Ifc2x3 export• Fixed issue related to opening that cuts through multiple walls (note that this is not yet 100%. In some cases, due to the extended body of the opening (that is defined in the native code) there may be more cut than it should for a few cases• Fixed issue with changing GUID of Window or Door when it is in the context of the opening that cuts multiple walls (issue "IFC Guid on family" in SourceForge)• Fixed IfcWindowLiningProperties, IfcWindowPanelProperties GUID issue• Improve handling for multiple meshes in a tessellated geometry that causes missing some surface body.• Fixed issues of UserDefined propertysets that fails to recognize the Pset assigned to a Type. Also improve the handling for Conditional Pset (by PredefinedType)• Fixed regression issue #70 missing toprail for IfcRailing on export• Fixed issue with "runaway" flex duct with "Keep Tessellated Geometry as Triangulation" option selected (issue #58)• Fixed regression issue (issue #96) IfcZone ObjectType not exported• Fixed issue of Naming override/default value, and issue of Qto_ properties are not exported• Fixed issue on a wrong enumeration for the SweptArea (it was set to .CURVE., should be .AREA.)• Fixed for orphaned entities and wrong footprint information due to incorrect projection direction for IFC4RV requirements. IFC4RV Beam (Arch) is now without error in the automated test• 1st fixed for issue related to runaway parts in "export only elements visible in view" (there are still situations that may cause a wrong rotation, but the test case reported in issue #86 so far looks good)

Comments

Revit IFC v19.2.0.0 Open Source Code Released

Autodesk’s Angel Velez mentioned on Twitter the Revit IFC 2019 source code was just released with many bug fixes and 2020 is coming.

“The long awaited Autodesk Revit IFC v19.2 released ((link: https://bit.ly/2PKzt9C) bit.ly/2PKzt9C)! Lots of bug fixes, and working on getting 2020 open source out the door also (with even more fixes, many of which will be back-ported to v19.3). App store soon.”

RELEASE NOTES 19.2.0.0

General:• This is generally a bug fix release with some new IFC functionality.

New Export Functionality:• IFC Exporter now supports IFC Spatial Container assignment override using IfcSpatialContainer parameter. Valid values are: "IFCSITE", "IFCBUILDING", or name of the Building Storey• Improved detection of Door operation type using the 2D swing symbol (arc). The improved version detects range of angles (not limited to 90, 180 or 360 degrees only)• Added support for IfcCivilElement• Replace IfcRelConnectsPortToElement with IfcRelNests for IFC4 export as recommended in IFC4 specifications, allowing non-IfcDIstributionElement to participates in the connectivity• Added support for RampFlight and Run from generic models or family representing more complex Ramp for export to IfcRamp and IfcRampFlight• Added various property Calculators• Improve performance when exporting a large mesh• Enable IFC Property Templates• Allow multiple Property Template mapping from txt• Projection improvement• Enable site and project property creation• Utilize Site GlobalId method• Add multilanguage support files for German language (DE)• Provide a complete list of all Shared Parameters used by Revit on export including ALL properties defined in IFC PropertySet Definition for both Instances and Types. The lists are included in the installer and will be placed in the install folder: IFC Shared Parameters-RevitIFCBuiltIn_ALL.txt (for the Instance parameters) and IFC Shared Parameters-RevitIFCBuiltIn-Type_ALL.txt (for the Type parameters).• Improve consistency for setting the object direct attributes, support IfcObjectType[Type] special parameter to drive instance ObjectType parameter from the Type, update the shared parameter definition files (now for [Type] parameters we will also maintain the GUID as long as it remains)• Incremental work towards IFC4RV 1.2 MVD

Export Bug Fixes:• Consistent ExportAs entity and its PredefinedTypes• Export fails when there is no associated Plan View to a level• Additional fix for error getting 2D data when there is no Level associated to the FamilyInstance• Various fixes related to missing geometry and export failures• Fixed performance issue in IFC2x3 export due to error in creating types• Fixed issue with slanted Pile• Fixed issue related to element that is split into parts• Improvement in handling level of Part Override• Some improvements on classification (issue #31)• Improve voiding of IfcMappedItem representation (issue #9)• Fixed issue on Composite curve tolerance (issue #5)• Fixed issue where element is still exported even though it is set to not-exported in the mapping table• Bugfix for incorrect cylindrical hollow core Beam export in IFC4RV• Fixed for issue #51• Bugfix based on Pull request #52 for MEP connector, and a few clean-ups• Fixed minor issue to ensure generic element exporter will generate consistent GUID for the instance• Fixed issue when OverrideElementContainment is used but the Site does not have site geometry (from Topography surface)• Add support of OverrideElementContainment also for SpatialElement (Room/Space/Area). This enables export to place IfcSpace directly to IfcSite for example, which is useful for outdoor spaces• Refactored the handling of valid entity and type and fixed a few defects related to it (Github issue #68)• Fixed issue with Stair Landing that is offset far away from the supposed location• Fixed issue with missing geometry when assigning IfcExportAs to the Spatial Element (Issue #23) However, in IFC4RV or DTV, there is a fixed list of valid entities that will be enforced, entity such as IfcExternalSpatialElement will be exported as IfcBuildingElementProxy.• Fixed performance issue when there is a large triangulated geometry for export to IFC4RV• Fixed issue of exception raised during export when "Export schedules as property sets" option is selected, and the model contains ViewSchedule from the template• Update Source/IFCExporterUIOverride/IFCExporterUIWindow.xaml.cs (issue #59)• IFCBooleanOperator.Union don't work! (issue #32)• Fixed issue in exporting IfcBuildingElementProxy that assigns an invalid enumeration for CompositionType in Ifc2x3 export• Fixed issue related to opening that cuts through multiple walls (note that this is not yet 100%. In some cases, due to the extended body of the opening (that is defined in the native code) there may be more cut than it should for a few cases• Fixed issue with changing GUID of Window or Door when it is in the context of the opening that cuts multiple walls (issue "IFC Guid on family" in SourceForge)• Fixed IfcWindowLiningProperties, IfcWindowPanelProperties GUID issue• Improve handling for multiple meshes in a tessellated geometry that causes missing some surface body.• Fixed issues of UserDefined propertysets that fails to recognize the Pset assigned to a Type. Also improve the handling for Conditional Pset (by PredefinedType)• Fixed regression issue #70 missing toprail for IfcRailing on export• Fixed issue with "runaway" flex duct with "Keep Tessellated Geometry as Triangulation" option selected (issue #58)• Fixed regression issue (issue #96) IfcZone ObjectType not exported• Fixed issue of Naming override/default value, and issue of Qto_ properties are not exported• Fixed issue on a wrong enumeration for the SweptArea (it was set to .CURVE., should be .AREA.)• Fixed for orphaned entities and wrong footprint information due to incorrect projection direction for IFC4RV requirements. IFC4RV Beam (Arch) is now without error in the automated test• 1st fixed for issue related to runaway parts in "export only elements visible in view" (there are still situations that may cause a wrong rotation, but the test case reported in issue #86 so far looks good)