Autodesk / Autodesk/revit-ifc

ENH: Fast export

Open
#831 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

### Enhancement Description

Some objects take ‘too much’ time while creating an IFC.
I would love the exporter to lower the export setting for those problem objects .. Or even skip them in order to save time. Just add a smart report that shows what has been done. And add a warning in those IFC objects that state what decision the Revit exporter has made.

From a Revit user perspective we need fast result. And we also want to know where the problems are in our model. So we can address them in Revit as efficient as possible. Perhaps even right after the exporter gave us a warning ánd an IFC. Waiting for a long time without knowing what is wrong with your model is frustrating and also does not help to get better results in the future.

To give another related hint: A quick way to find problem objects in Revit is adding related ID’s to an Selection Set. A user can Isolate this IFC-exporter generated Selection Set in a 3D view and off you go.

If this enhancement is a scarry thought, you can always make it an option. I think users will love it eventually.
And it will also help to improve the Revit and IFC models. Because every user learns over time what does or does not work.

Here an example what kind of things I’am talking about. But another example can be rooms. Generating a 3D IfcSpace with all it’s relations can be very hard. Even if Revit does not have a problem (yet) with that Room.
Using the (more) efficient Revit Profile family in a normal project will save +/-70minutes of calculation time.
(from 3minutes to 1 hour 11 minutes)
![not_efficient](https://github.com/user-attachments/assets/b3d90ace-5df9-420f-b1c1-730b7067fbad)
![efficient](https://github.com/user-attachments/assets/d1a3047f-6590-4865-a58d-d373c32665c5)

### Revit Version

2024.0.x

### IFC for Revit Addon Version

24.x.x

### Windows Version

11 22H2

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified, so begin by tracing the IFC export workflow and measuring which object types cause the reported delays. Done would require an agreed design for optional fallback or skipping, a report and warnings identifying decisions, and coverage for the example profile-family and room cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.