revit-ifc icon indicating copy to clipboard operation
revit-ifc copied to clipboard

IFC for Revit and Navisworks (2019+)

Results 293 revit-ifc issues
Sort by recently updated
recently updated
newest added

Hi, We are looking to convert the REVIT file to IFC file. We have downloaded this source and there is no build error. But we need to know, **how to...

inquiry
Triage

The relationship between a nested shared family and it's parent family isn't set.

enhancement
export
parameters-properties
Triage

Hello, I just updated Revit 2022 to the latest IFC export version 22.6.2. and when exporting to IFC 2x3, self-applied type parameter information for all IfcRamp and IfcFooting disappears. In...

in progress
export
parameters-properties
2022
Revit
IFC mapping

# System info Revit 2021.1.1 Revit IFC 21.1.0.0 Windows 10 IFC schema : IFC4 MVD : Reference View # Description of the issue Multilayer Roof exported as thin layers : ...

### Problem Description I have discovered that export from RVT 2025 does not include these mapped attributes of **IfcBuilding**: - Long name - Description - Object Type Using shared parameters,...

problem

Is there way to recreate a Revit 'sweep' upon IFC import?

### Problem Description Mapping parameters for Revit type "Gutter" is not working in version 24. ![Image](https://github.com/user-attachments/assets/2e7d1554-394c-44f3-83ed-9e75094a41c1) Tried using every possible Classes, and also Export as IfcWall class, but the problem...

problem

There are a number of dependent elements that would benefit from inheriting their ```IsExternal``` attribute value from their respective parent / host: - Stringers of assembled stairs - Stair-hosted railings...

enhancement
parameters-properties
2022

### Enhancement Description ## Context In Revit 2025, the ability to set export class mapping was moved from the File menu to the IFC export settings. This is generally a...

enhancement

### Problem Description When importing export class mappings from a text file the localized string for "Not exported" (which was working fine in previous versions) is not interpreted correctly. This...

problem