Questions and answers about Incremental Model Open (Tech Preview).
Opening a model with worksets closed reduces the amount of model content loaded into memory by excluding selected worksets during model open. However, this workflow still requires manual organization of models into worksets or linked files to manage performance and file size.
Incremental Model Open takes a different approach by processing model data on demand. Instead of relying on worksets to limit what is opened, Revit processes only the data required for the initial view, and continues processing additional data as needed while you work in the model.
Incremental Model Open is designed to improve scalability for large projects and reduce the need to split models solely to manage open performance or memory usage.
With Incremental Model Open, the initial model open prioritizes only the data required for the starting view. When opening additional views, Revit may need to process additional model data that has not yet been processed.
The impact depends on the type of view being opened and the amount of model data required. For example, opening a large coordination or 3D view may require additional processing compared to opening a smaller drafting or detail view.
Currently, data that has already been processed remains available during the Revit session, reducing the need to reprocess the same information.
Printing a large set of sheets may require Revit to process additional model data during the print or export operation. As a result, some processing that previously occurred during model open may occur later.
For PDF workflows, Revit also supports Background PDF Export, allowing exports to continue in the background while you keep working in the model.
Add-ins and API workflows continue to query model data using the existing Revit API workflows. If an operation requires data that has not yet been processed, Revit processes the required data before continuing the operation.
Incremental Model Open is designed to work transparently with existing add-ins and model query workflows, without requiring changes to current automation or analysis processes.
No. Incremental Model Open focuses on reducing the amount of data processed during model open. Save and Sync to Central operations already work incrementally in Revit and are not affected by Incremental Model Open.
No. Cloud-hosted models are still fully downloaded and cached locally before opening. Incremental Model Open currently reduces the amount of model data processed into memory during the Revit session.
Streaming model data directly from the cloud is part of the long-term vision for Revit scalability improvements.
Yes. The amount of data required by the starting view directly impacts model open performance. Simple views, such as drafting views, typically require less model data to process than large schedules or 3D coordination views.
For best results, select a lightweight starting view that minimizes model data requirements during startup.
No. Worksets and linked models continue to support collaboration, model organization, and discipline coordination workflows. Incremental Model Open is intended to reduce the need to split models solely to manage file size, memory usage, or model open performance.
Currently, model data that has already been processed remains available during the Revit session, even after closing views. Incremental Model Open does not unload processed model data from memory automatically. This is consistent with current Revit behavior.