It seems like it's never enough memory to upload a presentation to Epic Cloud! There's no clear understanding of where and how we could optimize. If we are blocked to that 13.6 Gb storage limitation, there is no way we could build a success market for our business! Appealing Scenes require lights, a lot of assets, some animations, nice shaders, etc.
Of course, it becomes heavy at the end. Please clarify this.
Thank you for posting in the community. At this time when you work in Twinmotion it saves information for the Undo command steps so you can go back and other important information for the scene to function while working.
In order to clear the memory you need to save the TM file then closing and re-opening the scene is usually needed before you try to upload to the cloud to make sure the Hardware check before uploading the scene will be more accurate.
We have also recently increase the memory to 20GB and larger scenes will be able to be uploaded. We are still in early access and developing a lot new features and improving the existing ones.
We have also released a Panorama Set so you have more options on how to present and share your work. This Panorama set is also a way to upload those really large scenes in a format that is easier to stream. We have also updated our documentation website with instruction for you to reference: https://www.twinmotion.com/docs/2022.1/en-US/SharingAndCollaborating/TwinmotionCloud/
If you have any suggestions or features request please send them to our road-map as this goes directly to the development team:
Here are some steps you can take to help for the current Presentation to upload with a better memory usage:
You may need to create a separate Twinmotion file so you can manipulate certain elements differently than your primary scene.
When sending a presentation to the cloud, every element in the scene graph even off will be taken into consideration thus it is important to completely delete unnecessary elements.
Check the statistics and how many polygons and textures you have in your file. Remove any unused Materials and use instances for objects that are supposed to be the same.
Reducing the size of the largest textures, for custom material.
Using the most simplified trees models as different tree models in Twinmotion have different size in MB.
Using datasmith plugin as it skips the back faces of the models, thus the number of polygons will be smaller.
Also consider using the Collapse All method for imported elements.
Remove unnecessary QuixelMegan scans 3D assets.
Remove unnecessary humans/characters.
Before uploading to the cloud you will need to save the Twinmotion file in order to update the statistics, then close and reopen to clear any temporary data.
Depending on your scene maybe splitting it up the interior and exterior content could help and uploading 2 files.
We also have updated our FAQ and our documentation site for further helpful information, and might be helpful.
Hope this helps and if you have any feature requests please submit them on our official road-map: https://portal.productboard.com/7pu88c9kpmqtzt8hwg6arujh/tabs/4-under-consideration