The integration between Revit and Unreal Engine has been a cornerstone for many architectural and design professionals for years. However, recent versions of Revit, particularly starting with 2025, have introduced significant workflow disruptions related to the Datasmith export plugin, leaving users frustrated and seeking solutions. This issue, widely discussed across forums and community channels, directly impacts the user experience and efficiency of professionals who rely on this powerful workflow.
Historically, the journey of integrating Revit with Unreal Engine has seen substantial evolution. Early adopters, like the author of the original post, recall a time when exporting projects between the two platforms required indirect methods, such as using 3ds Max as an intermediary. This was a time-consuming but necessary process for those dedicated to leveraging the combined power of Revit’s design capabilities and Unreal Engine’s visualization potential. The introduction of Unreal Studio and Datasmith marked a significant leap forward, streamlining the conversion process and directly addressing user feedback for a more seamless integration.
This robust integration continued to function smoothly through Revit version 2023. Even as the plugin’s distribution shifted, becoming integrated within Revit starting in version 2024, users could still export .udatasmith files through an icon, likely linked to Twinmotion. This maintained the crucial bridge for importing projects into Unreal Engine via Datasmith.
The situation changed dramatically with Revit version 2025. Users were suddenly prompted to install Twinmotion to export .datasmith files, a requirement that felt counterintuitive and disruptive, especially for those who preferred not to use Twinmotion or had specific workflows that didn’t necessitate it. This change forced many, including experienced professionals, to revert to older methods, such as using 3ds Max as a bridge, which is both laborious and inefficient.
The problem has been exacerbated with the arrival of Revit 2026. Attempts to use the same “workaround” – installing the Datasmith plugin version compatible with Revit 2023 – failed. In version 2026, the plugin reportedly no longer recognizes 3D views within Revit, rendering the export process impossible through this method. This has led some users to uninstall Revit 2026 and return to Revit 2025 to maintain their existing workflow.
The core of the issue lies in the apparent disconnection between Autodesk’s Revit development and the functionality of the Datasmith exporter. While the plugin was internally integrated with Autodesk, this integration appears to have broken down in Revit versions 2025 and 2026, specifically concerning the export of Datasmith files. This situation is not merely an inconvenience; it actively hinders the workflow of experienced professionals who have built their workflows around the Revit-Unreal Engine integration.
There is a strong call for the Unreal Engine team, particularly individuals like @Ue_FlavienP, to acknowledge and address this escalating problem. The continued reliance on an indirect workflow or the inability to export projects at all significantly impacts the user experience and the overall effectiveness of utilizing Unreal Engine for architectural visualization and design.
For those still managing to export using Revit 2025 and an older Datasmith plugin, it’s a temporary solution to a growing problem. The hope is that renewed attention and communication between Epic Games and Autodesk can restore the seamless integration that professionals have come to rely on, ensuring that the powerful synergy between Revit and Unreal Engine remains a viable and efficient tool for the industry.