I’m running into a consistent crash issue in Twinmotion 2025 that wasn’t present in Twinmotion 2024, and wanted to check if others are experiencing this too.
What’s happening:
When I try to export path-traced images above 2K resolution (like 4K), Twinmotion 2025 crashes instantly.
Even very simple scenes (like a basic kitchen with minimal textures) trigger the crash.
It happens regardless of path tracer settings (samples, shadows, lights, textures all minimized).
But here’s the weird part: even much more complex scenes worked perfectly in Twinmotion 2024, even at 4K with high path tracer settings.
My system:
GPU: NVIDIA RTX 4060 (8 GB VRAM)
RAM: 16 GB
OS: Windows 11
Twinmotion 2025 (latest build)
It seems like TM 2025 is using a lot more GPU memory up front — maybe pre-allocating render buffers for the whole image?
In 2024 it must’ve handled VRAM more gracefully, because it never crashed like this.
Questions:
Is this a known issue?
Is there a way to force Twinmotion 2025 to scale back memory usage or add a fallback for lower VRAM GPUs?
Would love to hear from anyone else using an 8 GB card — and especially from Epic if this is something you’re tracking. Thanks!
Yes, just upgraded to 2025.1.1 from 2024.1.2 and instant crash and dump error message on all views that previously exported just fine. I noticed that the views disabled the light source being dependent on the HDRI image when they were upgraded and thought that had something to do with it, but no. My hardware specs are maxed-out and cannot physically be upgraded any higher. Good thing I backed up everything before upgrading. I’ll be going back to 2024 until this can be resolved.
EDIT: My images are just shy of the maximum of 9000x9000, so perhaps 2025 can’t handle that size anymore? I’ve gone back to 2024 and rendering out these same views at medium rez in under 5 minutes each, instead of insta-crashing in 2025…
Thanks — this confirms it’s not just on mid-range GPUs. Even with RTX 4090 + 64 GB RAM, 2025 crashes while 2024 runs fine. Definitely looks like a VRAM mismanagement or resolution limit regression in 2025. Hopefully Epic can reproduce this and patch it.
I don’t even understand how nobody else is experiencing this, or how it went unnoticed in the 3 beta versions and two releases after that??? Baffling…are we not exporting our projects?
It seem that there are more bugs in 2025 1.1 - not only path tracer 4K export crashes (tested on rtx 3070 and 4060 - the same result - crash) but it seem that the sketchup import has some trouble.
