Would Twinmotion become unusable with REVIT?

[David_TESSON]

Hi,

I just tested Twinmotion 2026 for Revit 27. What a disappointment!

The multi-material object problem isn't fixed, and even worse, aware of the issue (it's explained in the release notes), they removed the "Collapse by material" option during import. Now we have the choice between "Collapse all," meaning a single object for the entire model unmanageable, or "Keep hierarchy," which results in a phenomenal number of objects! Equally unmanageable.

And regardless of the solution chosen, multi-material objects are buggy.

The same problem occurs with Datasmith export.

There are clearly a lot of ghost object issues after synchronization.

I completely abandoned 3ds Max years ago because Twinmotion was simple and efficient, but I'm afraid I'll have to go back to it. However, this version does offer a lot of interesting features.

And you? Have you tested it?

[Simon_Weel]

My colleagues did some testing with Twinmotion and decided they rather stick with Enscape.

A new kid on the block is D5 render, so if you go shopping for something new - it looks pretty impressive?

[luukdekker8]

Yes the collapse by material was the only way it worked with revit. Now materials are buggy. When changing a material of an object in revit it will not update in twinmotion anymore. The only option is to reset materials for all, but this will reset material settings for everything. What a bummer