Skip to content

IFC for Revit 2015 v15.2.0

Latest
Compare
Choose a tag to compare
@AngelVelezSosa AngelVelezSosa released this 15 Jan 21:19

New Export Functionality:

  • Added a message to the user stating that exporting linked files does not support exporting mirrored instances.
  • Moved some more native code into the open source .NET code.
  • Revit spaces support IfcLongName to override the "LongName" parameter.
  • The export UI has been prepared for localization into alternate languages, and has been translated into French. The French version will be automatically used if you have a French OS on your machine. If you are interested in translating the UI into your local language, contact us and we will provide you with the resources file to translate. Note that the help is still English-only.
  • The functionality for creating and using user-defined property sets has been greatly enhanced. This includes:
    • Added a "DefaultUserDefinedParameterSets.txt" file to allow a user to create user-defined property sets for any setup, including the in-session setup.
    • Added the "IFC2x3 Extended FM Handover View.txt" user-defined property sets file to the installation. This also fixes a typo in the original version.
    • Allow the user to specify any file as a user-defined property set file, instead of being forced to use the default name and location.
    • Increased the types of fields that can be used from the original 4. The full list is detailed in the DefaultUserDefinedParameterSets.txt file.
  • The Setup dialog for the export alternate UI has been split into 3 tabbed pages to make it easier to find and understand the export options.

Export Bug Fixes:

  • Allow export of an instance of a face-based door or window family placed on a wall.
  • Correctly associate IfcFlowSegment to its associated IfcPipeSegmentType entity when exporting gutters.
  • Don't do special calculations to generate geometry for stairs, ramps, and railings that aren't multi-story.
  • Don't export "NOTDEFINED" as the type value if the user hasn't specified a value. This was especially a problem for IFC entities that didn't have "NOTDEFINED" as a valid value, such as IfcBuildingElementProxy.
  • Fix the exported height of some walls that have vertical regions defined that extend beyond the actual height of the wall.
  • Fix the exported placement of some objects such as railings when the "Use Solid Models if Possible" UI option was used.
  • Improve performance when exporting 1st level space boundaries by not calculating the boundary information twice.
  • Significantly improve performance when trying to export a highly-tessellated geometry.
  • When splitting walls and columns on export, ignore non-building storeys when doing the split.

New Import Functionality:

  • Add an "IfcMaterial" field that contains the material name(s) associated with the element.
  • Add an "IfcSpatialContainer" field that contains the name of the project, building, building story or space that contains the element.
  • Create multiple layers for simple cases of elements where IfcMateralLayerSetUsage is defined.
  • Import IfcGrids. There are some fundamental differences between IFC and Revit Grids, most notably that IFC grids are per-view, and Revit Grids are per-model. As such, there may be cases where some grid lines show up in more views than initially designated in the IFC file.
  • Improve healing and logging of imported solid data that is slightly dirty. This should result in fewer missing objects.
  • Read in Axis information. This is still not displayed to the user, but it is used when IfcMateralLayerSetUsage is defined.
  • Read in IfcConnectedFaceSet in some cases where it was ignored.
  • Populate the ALL_MODEL_DESCRIPTION built-in parameter with the entity description, if the element has the field and the entity has a description.
  • Support IfcSpecularRoughness for material definitions.
  • The "Processed" indicator will be updated every 500, not 100, entities read.

Import Bug Fixes:

  • Fix "missing" faces when elements were cut by openings and the IfcOpeningElement sub-category had its visibility turned off.
  • Handle unbound circles used for profile definitions in certain cases.
  • Protect against an element not being created because of an invalid material definition.