About the save error in Twinmotion 2025.2

Development Platform & Builds
, ,
1

I’ve been struggling with crashes when saving files for the past few days.

Error message:

[Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting…]

This issue occurs only with a specific project file.
The file was originally a bit over 1 GB, so I split it into two parts (around 0.6 GB each), but the crash still happens.
Other than during saving, everything works fine. However, when using this particular file, VRAM usage stays above 80%.
Changing the Quality Settings to Low or Medium makes the crash slightly less frequent, but it still happens sometimes.

Here are my PC specs:

  • CPU: Intel Core i7-14700 (2.10 GHz / 20 cores 28 threads)

  • GPU: NVIDIA GPU (10 GB VRAM)

  • Memory: 64 GB (DDR5 5200 MT/s)

  • Storage: 1.96 TB

Could this be a hardware limitation issue?
I’ve worked with fairly heavy Twinmotion files before, and I’ve occasionally had random crashes during editing, but this is the first time it happens specifically while saving, which makes it difficult to take preventive measures such as saving frequently.

Is there any fundamental solution or workaround for this problem?

2 Likes
2

I would roll back to 2025.1.1. I did some testing with the same project in both versions and I ran out of memory on my 4080 12GB card in 2025.2 but was running about 9GB of vram with no crashes in 2025.1.1. Maybe later I would switch to the later version if they would optimize their software.

3

Having this happen on different files on 2 machines, at home & at work, each running 5090s w/ different drivers, so it’s not a hardware issue. My files are all heavy so I’m trying to lighten them and always use Datasmith, but still crashing far more than what it used to. I’ll be using the previous version until 25.2 works.

4

Same problem here with a 4090. Until using 2025.2 I never encountered memory crashes like this before.

5

Whilst it’s not a fix per say I’ve found the following works 99% of the time:
Before saving, exit any scene/view you’re in and wait for the % usage stats in the bottom left of the interface to drop below 100%, it maybe necessery to hide some complex content and wait again for the % to drop.

As long as its below 100% I’ve been able to save, the only time it fails for me now is when I forget to come out of a RT scene before I do the above.