For architects and designers relying on the seamless integration between Revit and Unreal Engine, recent versions of Autodesk’s Revit software have introduced significant workflow disruptions. Users migrating to Revit 2025 and 2026 are reporting critical issues with the Datasmith export functionality, a crucial tool for transferring 3D models for real-time visualization and game development. This problem is impacting experienced professionals who have depended on this integration for years, leading to frustration and a degraded user experience with Unreal Engine.
The Datasmith plugin, initially a standalone offering and later integrated into Revit, has been a cornerstone for many in the AEC (Architecture, Engineering, and Construction) industry. Its purpose is to simplify the process of moving complex architectural models from Revit to Unreal Engine, eliminating the need for intermediary software like 3ds Max, which was previously a common workaround. This integration has evolved over several years, with users generally finding success through versions like Revit 2023 and 2024. However, the landscape shifted with Revit 2025.
In Revit 2025, the export process began requiring a Twinmotion installation, a departure from previous versions. While this might have been an attempt to streamline the workflow, it created an unexpected hurdle for users who primarily utilize Unreal Engine. The situation worsened with the release of Revit 2026. Users attempting to replicate the workaround used in Revit 2025 found that the Datasmith plugin, even when unofficially installed, no longer recognized 3D views within Revit. This renders the direct export functionality unusable in the latest versions of the software.
The inability to export .udatasmith files directly from Revit 2025 and 2026 has forced professionals to revert to older methods. Some users, like those mentioned in community forums, have had to reinstall 3ds Max to act as a bridge, a process described as laborious and inefficient. This setback is particularly frustrating for long-time users who have built their workflows around the Revit-Datasmith-Unreal Engine pipeline. The disruption negatively affects project timelines and the overall user experience with Unreal Engine, a platform celebrated for its real-time capabilities in architectural visualization.
The core of the issue appears to be a change in how the Datasmith plugin is handled within Revit, potentially an “outsourcing” of the service to Autodesk that has not translated smoothly into the latest versions. While the integration worked adequately in Revit 2024, the breakdown in Revit 2025 and 2026 signifies a critical need for attention from the development teams at Epic Games and Autodesk. Users are imploring the relevant teams, specifically mentioning @Ue_FlavienP on forums, to acknowledge and address this pressing matter.
The community is actively seeking solutions, with some users resorting to “informal workarounds” such as installing older versions of the Datasmith plugin. However, these methods are not sustainable and highlight the underlying problem: the lack of native support for Datasmith export in the latest Revit releases. The reliance on such patches underscores the dependency many professionals have on this specific workflow for their architectural visualization projects.
This situation is not isolated, as evidenced by numerous forum discussions and video comments from users across the globe experiencing the same export failures. The continuity of workflows for many architects hinges on a stable and reliable integration between Revit and Unreal Engine. The current issues in Revit 2025 and 2026 are a significant impediment, impacting productivity and user satisfaction.
The demand for a functional Datasmith export feature in the latest Revit versions is clear. Professionals are requesting that this issue be prioritized by the development teams to restore the seamless workflow they have come to expect and rely upon. Without a resolution, many will continue to face challenges in leveraging the power of Unreal Engine for their architectural projects, potentially leading them to explore alternative software or workflows.
We urge the Epic Games and Autodesk teams to investigate these Datasmith export failures in Revit 2025 and 2026 thoroughly. Addressing this issue is crucial for maintaining the trust and efficiency of the professional community that relies on this powerful integration. Further updates on the progress of a fix would be greatly appreciated by the affected users.

