SO:
Idioma:

Descripción

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).

Lea el documento de ayuda

Acerca de esta versión

Versión 19.1.0, 29/06/2018
General: - Some of the naming conventions for elements have changed. Please discuss in the forums if this causes problems. - This is generally a bug fix release with some new Link IFC functionality. New Export Functionality: - Add the ability to import and export custom configuration setups. - Add the ability to choose the project origin of the exported file. There are 4 options: - Current shared coordinates origin - Internal Revit coordinates - Project Base Point - Site Survey Point - A number of IFC4 Reference View improvements, including: - Export some profile names with geometry when appropriate - Fix scaling of triangulation coordinates - Improve export of beam axis - Restrict use of many disallowed IFC entities and geometries - Allow columns to be space bounding elements. - Allow remapping of IFC entity attributes in addition to properties. - Create more associated type entities for IFC objects. - Consistent ability to override name, object type and description for all entities - Export connectors even if they aren't connected to other elements. - Export parts whose host elements are in linked files, regardless of if "Export Parts as Building Elements" is checked or not. - Improved creation of IFCBUILDING and IFCSITE entities - Better support for Illuminance and Volume parameter types. - Include the exchange requirement information in the File Header for COBie export. - New UI to allow assigning the address filled out in the export options to the building and/or site. - Reduce the facet count for some element geometries. - Support export of fabrication parts. - Remove unneeded "Triangulation only" checkbox in the "Level of Detail" export options tab. Export Bug Fixes: - Export "NetVolume" and "NetSideArea" quantities instead of "Gross" ones. - Export PredefinedType/ShapeType for ramps, stairs and vibration isolators. - Fix export of certain elements so that they are of the right type instead of IfcBuildingElementProxy orIfcBuildingElementProxyType. - Fix export of some multi-story stairs. - Fix export of some space with empty Occupant fields. - Fix material assignment for some elements. - Fix missing predefined type for some elements. - Fix missing profile names for some beams. - Fix slope calculations for some elements. - Fix unexpected error when exporting a floor as an IfcRamp (for IFC2x3 only). - Fix unexpected error when exporting a site from a 3D view when exporting the active view geometry (for IFC4 RV only). - More fixes to correct "unexpected errors" of certain entity types. - Only allow unconnected elements if they are of type IfcDistributionElement. - Restore calculations for "concealed" and "is external" properties. - Restore proper mapping of Revit Grids to IfcGrids. - Restore proper GUID for some door, windows, and property sets. - Restore remapping of some deprecated IFC2x3 and IFC4 entities. - Restore support for parameter mapping files. - Restore support for provisions for voids in IFC2x3. - Restore support for IfcSpace "ElevationWithFlooring" attribute. - Restore tag for IfcCurtainWallType. - Restore tessellation level of detail for coarse tessellations. - Restore use of built-in parameters for populating some IFC parameters. - (Pre-IFC4) Stop converting space heater types to electric heater types. - (IFC4) Properly export some trimmed edges in advanced BReps. - (IFC4) Limit distribution ports to IfcDistributionElements only. New Import Functionality: - (IFC4) Support IfcCartesianPointList2D, IfcIndexedPolyCurve Import Bug Fixes: - Accept structural items that have an undefined LoadBearing parameter. - Better processing of slightly non-planar faces. - Better processing of some sweeps that have unnecessary start and end parameters. - Correct orientation of some objects on import with incomplete placement information. - Make sure all created schedules and parameters have unique names. - Improve import of some circular extruded geometries whose outer profile curves are slightly disjoint

Reseñas de clientes

(4 reseñas)

|

Obtener ayuda técnica
  • Exporting to shared coordinates
    Kong Hoang | marzo 13, 2019 Descarga verificada (¿Qué es esto?)

    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.


  • New naming of ifc objects?
    Tomas Westerholm | febrero 06, 2019 Descarga verificada (¿Qué es esto?)

    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? 


  • Override floor
    Edwin Bosma | enero 31, 2019

    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.

     


    Angel Velez (Editor) | febrero 01, 2019

    This isn't possible yet but it is something we are working on.


    Edwin Bosma | febrero 05, 2019

    Awesome. Thanks!


  • Plugin works only when revit display language is in english
    Elton L | diciembre 04, 2018 Descarga verificada (¿Qué es esto?)

    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!


    Angel Velez (Editor) | diciembre 18, 2018

    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.

Ir arriba