Twinmotion crashes due to VRAM limit on large scene – optimization exhausted

Hi everyone,

I’m currently working on a relatively large Twinmotion project, and I’m repeatedly encountering crashes with the error indicating that the application has run out of VRAM.

Issue details

  • Twinmotion crashes abruptly after some time working in the scene
  • Error message: “Out of video memory / VRAM”
  • This has happened around 3–4 times on the same project
  • The file has grown quite large due to scene complexity

What I’ve already tried

I’ve followed the official Epic Games guidance, including:

  • Scene optimization steps
  • Reducing quality settings
  • Managing textures and geometry

References:

Despite applying these recommendations, the crashes still occur, which makes me think the project has reached a practical VRAM limit.

My questions

  1. Are there any advanced techniques to handle very large scenes beyond the standard optimization steps?
  2. Is there a way to force Twinmotion to manage VRAM more efficiently or reduce memory spikes?
  3. Would splitting the project (e.g., into multiple files) be the only reliable solution?
  4. Has anyone successfully worked around this on complex models without upgrading hardware?

System info (to be filled)

  • GPU: [your GPU model + VRAM]
  • RAM: [your system RAM]
  • Twinmotion version: [version]

Any advice, best practices, or workflows for handling very large datasets in Twinmotion would be greatly appreciated.

Thanks in advance!