I am trying to find a way to decrease the file size of a Twinmotion presentation. It is curently 8GB. So far I have established that the amount of scenes does not impact on file size, the resolution of scenes does not impact on file size, using resource collector (purge) does not impact on file size. The documentation does not seem to cover this. If you have an idea on what could be tried, let me know. Forum entries suggest TM files are quite often that big, but I wonder if the presentation can be made smaller. What causes these file sizes?
I just created an empty presentation: 6GB.
An empty presentation should not weight that much. I think you may have some remaining unused materials in your scene.
Have a look at this guide:
https://dev.epicgames.com/community/learning/knowledge-base/rMyK/optimizing-your-twinmotion-scenes
I did the same as OP, has panorama and phase in the file.
With just starting scene and the metal ball… it give wooping me 3GB file size.
For a local presentation, those 3Gb are the basis of all necessary ressources to make Twinmotion work. you cannot go under this mandatory package, in term of size
Can we compress the PAK file or just reduce Texture size?
Is it necessary to send the whole Prestentation folder or is the model and other meta data store somewhere else?
I might find an excuse to pass the whole 3GB of the file through Onedrive, just a few time. But if I have to send the whole engine back and fourth until the finall design is done… People might lost their patient.
I still don’t know how to explain to them about the 3GB presentation. The input model is just 100MBish Revit file.
If only the architectural data (imported from Revit) needs to be updated, you can just update the \Twinmotion\Content\Paks\Userdata.pak
file by re-exporting the presenter on your side and picking the updated file to your customer.
However, before sending the .pak file to your customer, it is essential to do some sandbox testing locally with a presentation setup similar to theirs. Ensure that no Twinmotion assets have been added to your file that are not already part of the presenter’s resources, as this could result in a crash.