2025.2 Full release Memory Issues

General Feedback & Requests
1

Just built a new PC with top end parts on everything. 9950X3d, 5090, 96 gb RAM, etc…

I am totally stable with every other program but noticed with the 2025.2 preview that I was running out of memory and crashing basic scenes. I assumed it was part of the preview instability and that it would get resolved in the full release, but after installing the full 2025.2 release this morning, it still has the same issue.

Anyone else encountering this? Twinmotion is at an unusable state once again and I’ll have to revert back to 2025.1 for projects.

Thanks,

2

I get the same problem. And maybe it is just imagination, but seems like it is the material picker that makes it worse.

3

Hi there, thanks for posting, and I’m sorry for the trouble. We’re aware of this stability issue, and our team is actively investigating it.

To help us diagnose crashes more quickly, please report them via the Contact Us button. When you submit your ticket, include:

  • your .log file

  • The product and version number

  • Steps to reproduce the crash

  • Your OS and hardware specs

  • Any crash ID or a screenshot of the error

These details provide us with the full picture, allowing us to pinpoint the cause and implement a fix more quickly.

Thank you!

MC

4

I’ve opened a ticket on this same issue, and after trying various old tricks the file is working again and I can render on DX12 as well as save my file. Case 21429598.

To save if not letting you - resource collector is the only thing that worked for me.

What finally worked:

I switched back from DX11, to DX12 and was able to render Raytrace images. I was also able to do a regular “save” without crashing, I had to hide vegetation and all imported objects and not be in media mode.

I’m not sure if it was switching DX12 to DX11 & saving after hiding everything, then opening, switching to DX12 successfully saving again and reopening as DX12, that worked. But it is working now!

5

Nevermind. It crashed again.