Revit 2025 Connector – Release Date and Roadmap?

Hello!
I’m currently using Revit 2025, and I see that the current Omniverse connector officially supports up to Revit 2024.

In a previous forum post from September 2024, it was mentioned that “There should be an update for Revit 2025 later this year.”
Could you please confirm if there is now an official release date or roadmap for the Omniverse Revit 2025 Connector?

Additionally, if no direct connector is available yet, are there any recommended workarounds? For example:

  • Exporting via Datasmith?

  • Using intermediate formats like IFC or FBX?

Thank you in advance for your guidance!

@pst14 i am just another user so i’ll defer to the mods/devs for official response. but, AFAIK, Datasmith is the proprietary format for Unreal Engine/Twinmotion which likely won’t be compatible with OV. regarding .FBX, OV does have FBX support so shouldn’t be a problem getting your geometry into OV; but, i’ve not had luck with materials coming through and require an additional pass once the file’s been imported.

last but not least, not sure if you have other DCCs that you have access to, but more and more of them are starting to implement direct USD exports, which would probably something worth looking into if it’s viable in your pipeline.

Thank you for your reply — I really appreciate input from other users!

You’re absolutely right about the material issues when using FBX; it’s a common challenge. Regarding Datasmith, there’s an important clarification: while it is indeed heavily used in Unreal Engine and Twinmotion, Datasmith itself is actually a technology developed by NVIDIA as part of the Omniverse ecosystem.

Datasmith is designed to be the primary bridge between applications like Revit and Omniverse. It allows direct export of geometry, structure, materials, and parameters from Revit into the .udatasmith format, which can then be seamlessly opened in Omniverse Create, View, or USD Explorer.

The key point is that according to the official NVIDIA documentation, support for newer versions is being managed through their NGC platform:

“The Omniverse connector for Revit 2023 - 2025 will continue to be available on the NGC catalog.”
(Source )

hmm, i’ll defer to the devs/mods on datasmith if that’s the case. i have not seen any datasmith-related extensions in Kit but would love to be proven otherwise. i recall DS was developed by Motiva which was then acquired by Epic; i didn’t read too much about NVIDIA’s involvement in that product but i could’ve misremembered.

regarding the future roadmap for revit connectors, it wouldn’t hurt to keep an eye out on NGC. i will again have to defer to the mods/devs on the amount of support they’d be willing to put towards any of the connectors now that the they are considered legacy tools. based on previous threads, a mod has made mention that they are moving away from connector workflow. it’s encouraged for users to lean towards direct/native USD implementation from within DCCs instead. below are a few threads that come to mind wherein the connectors was inquired:

and a couple more direct points on connector workflow from the Discord server:

there’s another user on Discord that has reported not able to get 2026 to work with the connector, so unless you sit on older versions of Revit and rely on the latest connector available for the public, you may eventually run into situation similar to this. but the same user has reported IFC is indeed their prefer way of exporting from Revit.

i have not tested that workflow yet but could be worth doing some testing of your own to see what works for your purpose.

Thank you again for the valuable context and links - this is exactly the kind of insight that helps clarify the bigger picture.

You’re absolutely right about the historical roots of Datasmith (originally from Motiva, acquired by Epic), and I appreciate you pointing that out. My clarification was more about its current role within the NVIDIA ecosystem: while it originated externally, NVIDIA now treats Datasmith as a core part of Omniverse, especially through tools like the Omniverse CAD Converter and Connectors. For example, the Revit connector uses Datasmith under the hood to package data for USD conversion, even if it’s not exposed as a standalone Kit extension.

Regarding the shift away from connectors - thank you for highlighting those threads. The message from NVIDIA devs is clear: the long-term vision is native USD support in all DCCs. That’s where the industry is heading.

Let’s summarize, there may be a lot of opinions further, but without official support it will be fortune-telling.

Until Revit 2025+ offers direct “Export to USD” natively, we’re in a transitional phase. In practice, this means:

For users on supported versions (Revit 2023–2024): The NGC-based connector remains the most reliable way to achieve live sync with Create/View.
For users on Revit 2025+: We rely on intermediate workflows, just as you mentioned:
IFC - Blender/Rhino - USD (great for geometry and structure),
FBX (quick but lossy for materials),
CAD Converter (promising, but still evolving).
I’ve started testing the IFC - Omniverse pipeline via Blender (with the BIM workflow), and while it’s not perfect, it preserves topology and levels surprisingly well. It might indeed become the de facto standard for BIM-heavy projects.

The key takeaway for me is this: We’re moving from “connectors” to “USD-first pipelines”, and our workflows need to adapt accordingly. Tools like Datasmith will likely remain important behind the scenes during this transition.

Thanks again for sharing your perspective - it’s helping me refine my own approach. If you’ve tested the IFC-to-Omniverse flow, I’d love to hear how stable and material-friendly it’s been for you.

I can try to find out about the status of the Revit Connector, but now kit 108 can DIRECTLY import Revit files. We just added that. You can import RVT files directly without needing to convert them first. That is the way I would do it.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.