Hi, Flavien!
I had written this post previously 3 weeks ago but I ended up deleting it by accident
"Hello
Yes, I and many other people have been facing this problem since version 2025 of Revit. There are many forums and video comments on the internet complaining about this. I ask you, @Ue_FlavienP, to listen to us and make this issue relevant within the team. I’m even thinking about opening another post here on the forum to reinforce this subject.
I’m an architect who has been using the Revit + Unreal Engine integration since 2015. At first, it was more difficult to do the conversion, I had to use 3ds Max as a bridge to export the project between Revit and Unreal Engine… it was a lot of work, but it was the way it was at the time and that’s how I did it, because I was a fan of this integration (Revit + UE) and I still am today within our workflow. I even used some 3ds max scripts at the time, including one made by a friend to generate lightmaps and resolutions.
Some time later, between 2017 and 2018, Unreal Studio and Datasmith came along, and they finally listened to us and built this fantastic tool. I think that around this time, Epic also acquired Twinmotion, but I never liked using that program. Yes, I’ve tested it.
Until version 2023 of Revit, it was always wonderful to work with this integration, as well as the integration of Datasmith with all other 3D modeling software… until version 2024, when the plugin stopped being downloaded from the main website and came integrated with Revit from Autodesk. I think they outsourced this plugin service to Autodesk because of Twinmotion.
But until version 2024 of Revit, everything was fine, since even though it was “outsourced” by Autodesk, when clicking on the Twinmotion icon we could still export the 3D from Revit in a .udatasmith file so that we could import it normally into Unreal Engine via Datasmith.
Unfortunately, in version 2025 of Revit it started asking us to install Twinmotion in order to export the .datasmith files. That doesn’t make sense!
Just like @daveross777 said he was using Navisworks as a bridge between Revit and Unreal, I ended up using 3ds Max (I had to install it again) to do the same. This is quite laborious and not functional.
The best solution I found so far was to download the latest version available on the Datasmith website: the version for Revit 2023 and do an “informal workaround” to install and use it in Revit version 2025.
But the problem got worse yesterday, because I went to update and installed Revit 2026 and tried to do the same “informal workaround”, but in version 2026 the plugin (support up to version 2023) in my tests yesterday no longer recognizes the 3D views within Revit, so it became impossible to export as I was already doing with Revit 2025.
Unfortunately I had to uninstall Revit 2026 that I installed yesterday and go back to using Revit 2025 with Datasmith 2023 informally installed to continue using the Revit + Unreal Engine integration.
Because even after the plugin’s internal integration with Autodesk, this only worked in version Revit 2024. Neither version 2025 nor 2026 is working anymore when exporting Datasmith files.
I ask @Ue_FlavienP again to report this to the team, as it is disrupting the workflow of many people! Including users who, like me, have years of experience with both tools… All of this is negatively interfering with our User Experience with Unreal Engine.
Thank you very much for your time."
Have you read or reported to anyone about this? Is anyone on the Epic Games/Unreal Engine team aware of it?
Please help us 
