Twinmotion VR: Troubleshooting
Please refer to the following checklist if you are experiencing trouble with Twinmotion in VR.
Last updated
Was this helpful?
Please refer to the following checklist if you are experiencing trouble with Twinmotion in VR.
Last updated
Was this helpful?
It may be a hardware issue as well; double check:
Hard Restart of the Headset
Restart Twinmotion
Close and re-open through Epic Games Launcher.
For slow Twinmotion experiences, you will need to optimise your scene; there are visual settings to change but there are also optimisations in your model to make.
Please refer to this article by Twinmotion on optimising your scene:
Direct Link is not recommended for slow files, but you do have the option of Linking multiple files directly where Datasmith is supported. You need to have the file open during the Twinmotion's Import step and it will be available in the Direct Link menu. You are able to import multiple Direct Link files which gives you the option to assemble in pieces, and then finally collapse everything at the end.
When setting up expansive or large scenes, take note of the following:
Hierarchy
Import and process the most important details first at their highest possible level of detail, e.g. your main building model before adding context. Breaking up files into sections will also help you to slowly import and troubleshoot.
Instancing (Refer above article)
Where you have duplicates of the same exact model, consider instancing it instead. Import a single copy of the mesh and duplicate it from the Scene Graph, you will have the option to paste it as an instance. This is a more efficient technique for large scenes. This may mean you do more composition from within Twinmotion.
Meta Quest 3
Consider using Twinmotion/Unreal Engine's DATASMITH files. Or you may use standard file types like motionbuilder (.fbx).
Refer to the model above; making changes to your scene is the most optimal way to increase performance.
