issue with export to Twinmotion Cloud

Development Rendering
1

IMG_6224.HEIC
IMG_6224.HEIC3024×4032 2.74 MB

Hi everyone,

I’m encountering what seems to be a serious bug with Twinmotion Cloud export in version 2025.1.

Even when starting from the default scene (literally a blank project with the default sphere, no assets or geometry added), the Twinmotion Cloud export process estimates over 400 GB of RAM usage, and the cloud presentation takes over 2 minutes to load.

Here are the facts:

  • Project file size: 13 MB (just the default empty scene).
  • RAM usage locally (macOS Activity Monitor): 2.77 GB at peak.
  • My setup: brand-new Mac with the latest Twinmotion 2025.1.
  • No high-poly assets or ray tracing activated.
  • The issue persists even when exporting again, with no changes.

This looks like a bug in the resource estimation or a backend problem on the Twinmotion Cloud side.

Screenshots:

  1. Cloud export panel showing 400+ GB RAM usage

Is anyone else experiencing this?
If a developer from Epic/Twinmotion sees this, I’d be happy to share the project file (it’s just 13 MB).

Thanks in advance!

2

Same exact issue! please fix this- Blank scene is too big for cloud