For anyone on a current release, effectively no. The Omniverse connectors for Autodesk Revit and Autodesk 3ds Max are in maintenance rather than active development, they do not support Revit 2025 or 3ds Max 2025, and the launcher that distributed them was deprecated on 1 October 2025. If your Revit and your 3ds Max are recent, there is no working Omniverse route between them.
This is a change worth knowing about, because Omniverse was a real answer for a while and a lot of writing about the pipeline still assumes it is one.
What changed
| Item | Status |
|---|---|
| Omniverse Launcher | Deprecated 1 October 2025. |
| Revit connector | Does not support Revit 2025. |
| 3ds Max connector | Does not support 3ds Max 2025. |
| “Send to Omniverse” and “Publish Project” in the Revit connector | Deprecated, scheduled for removal. |
| Both connectors generally | Still downloadable from the NGC catalog. Patched as needed rather than actively developed. |
Nothing here was switched off overnight, and NVIDIA has not deleted the connectors. But a route that stops at the 2024 releases of both applications is not a route most teams can take, and one whose transport functions are marked for removal is not one to build a pipeline on.
Why it was attractive, and what the real cost was
Omniverse promised live synchronisation through USD rather than a file handoff, which is a genuinely different proposition from everything else on the list. Change a wall in Revit and see it in 3ds Max without an explicit reload.
What that description usually left out was the infrastructure. The route required a connector installed in each application and a Nucleus server for the two to meet on. It was a platform commitment, not a plug-in, and that is a large amount of setup for a two-application problem.
What it is still reasonable for
If you are on Revit 2024 or earlier and 3ds Max 2024 or earlier, already run Nucleus, and want USD at the centre of a larger pipeline, the connectors still exist and still work. That is a narrow set of conditions and it gets narrower with each release.
Where that leaves the pipeline in 2026
Shorter than the lists suggest.
| Route | Available on current releases | The cost |
|---|---|---|
| File Link Manager | Yes, native in 3ds Max | Object identity is not stable across reloads. Materials, modifiers and UVW are lost on the elements that get rebuilt. |
| FBX export and re-import | Yes | Rebuilds the scene every revision. |
| NVIDIA Omniverse | Not on 2025 or later | Maintenance mode, launcher deprecated, transport functions scheduled for removal. |
| Speckle | No | No 3ds Max connector exists. |
| Epic Datasmith | Not applicable | Its exporters write for Unreal Engine, not for 3ds Max. |
Two of the five entries that commonly appear on these lists cannot move anything between Revit and 3ds Max at all, and a third no longer runs on current releases.
Frequently asked
Does NVIDIA Omniverse still connect Revit and 3ds Max?
Not on current releases. The Revit connector does not support Revit 2025 and the 3ds Max connector does not support 3ds Max 2025. Both are in maintenance rather than active development.
Was Omniverse discontinued?
Not entirely. The Omniverse Launcher was deprecated on 1 October 2025, and the connectors remain downloadable from the NGC catalog, patched as needed. The Revit connector's Send to Omniverse and Publish Project functions are deprecated and scheduled for removal.
Did Omniverse really give live sync between Revit and 3ds Max?
It offered live synchronisation through USD, which is different in kind from a file handoff. It required a connector in each application and a Nucleus server for them to meet on, so it was a platform commitment rather than a plug-in.
I am on Revit 2024 and 3ds Max 2024. Can I still use it?
Yes, the connectors exist and work on those releases. That window narrows with each new release of either application.
What are the remaining Revit to 3ds Max options in 2026?
The native File Link Manager, an FBX round trip, or a purpose-built plug-in. Speckle has no 3ds Max connector and Datasmith exports to Unreal Engine, so neither is an option.
Related field notes
- Why “Keep material parameters on reload” doesn’t save your 3ds Max materials
- Do Revit and 3ds Max versions have to match?
- What happens to deleted Revit elements in 3ds Max?
- Why modifiers and UVW break when a Revit link reloads
- What Combine By Revit Material actually does to your model
- Does Datasmith move a Revit model into 3ds Max?
- Can Speckle sync Revit and 3ds Max?
- Revit File Link or FBX for 3ds Max?
Levlin Bridge
Levlin Bridge is a Windows plug-in that moves geometry between Autodesk Revit and Autodesk 3ds Max in both directions. Push the model from Revit, pull it into 3ds Max, and push the geometry you changed back into Revit as real elements. Only the difference ever moves, so materials, modifiers and UVW stay exactly where you left them. Any Revit 2022–2027 works with any 3ds Max 2024–2027.
Levlin Bridge is in final testing and is not released. There is nothing to download yet. Leave your email and you get the 30-day trial the day it ships.