# Twinmotion VR: Troubleshooting *** ## **Quest 3 Troubleshooting** It may be a hardware issue as well; double check: [Quest 3 Troubleshooting](https://ms-kb.msd.unimelb.edu.au/next-lab/virtual-reality/guides/virtual-reality-hardware-set-up/meta-quest-3/troubleshooting) ### **Restarting Everything** **Hard Restart of the Headset** 1. [Follow Quest 3 Instructions](https://ms-kb.msd.unimelb.edu.au/next-lab/virtual-reality/guides/virtual-reality-hardware-set-up/meta-quest-3/troubleshooting) **Restart Twinmotion** 1. Close and re-open through Epic Games Launcher. *** ## **Twinmotion Optimisation** 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: {% embed url="" %} ### Export Files Consider using Twinmotion/Unreal Engine's DATASMITH files.[ Plugin install required.](https://www.twinmotion.com/en-US/plugins)\ Or you may use standard file types like motionbuilder (.fbx). ### Direct Link 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. *** ### Object Hierarchy * [ ] Object groupings in Twinmotion are decided upon import; it is recommended to collapse files as much as possible (refer above article) * [ ] Group objects by material and they will be imported as one object when Collapsed by Material during import * [ ] To keep ALL objects separate (not recommended), import while Keeping Hierarchy * [ ] Alternatively, you may export as many individual or grouped geometries as you wish if you want to control each object's material separately. *** ### Model Optimisation * [ ] Simplify the mesh as much as possible * [ ] E.g. In Rhino; use the Mesh command to manually mesh objects + edit them to be as simple as possible * [ ] What do you really see - if you are looking at something from far away, does it need to be full 3D or could it be a single plane? * [ ] Import objects in a more efficient way (refer to the above article); * [ ] In general, one single object is preferred to smaller objects, e.g. a context model should be all booleaned together into a single mesh. *** ### **Scene Optimisation** 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. *** ## **Connections** **Meta Quest 3** * [ ] Meta Quest link and Twinmotion are required to be open for the process to succeed. * [ ] On your laptop navigate to: `Meta quest link > settings > general > OpenXR settings > ensure Meta quest link is set as the active OpenXR runtime` * [ ] In the same tab, ensure the 'allow unknown sources' toggle is on. * [ ] Ensure divers are updated and restart Twinmotion. * [ ] Open both Twinmotion and Meta Quest link as admin and try again if issues continue. *** ## **Slow Program** * [ ] Refer to the model [Twinmotion Troubleshooting](#twinmotion-troubleshooting) above; making changes to your scene is the most optimal way to increase performance. * [ ] In general; Twinmotion VR can quickly become slow, so only populate areas that are in viewable within your VR experience. * [ ] In scene properties; reduce scene detail. * [ ] Navigate to: `twinmotion > stats (bottom left of screen) > quality setup (top left) > ensure all options are set to 'low' in both the VR and desktop tabs` * [ ] Navigate to: `twinmotion > stats (bottom left of screen) > quality setup (top left) > settings tab > refer to adjustments in next steps` * [ ] `Probes resolution > reduce to 64 in viewport` (you don't need to change the export level) * [ ] `Sky dome resolution > low` (for viewport) * [ ] `Grass fading > near` (this will reduce quality of ground plane but allow the model to run smoother) * [ ] `Save > autosave every 30 - 60 mins` * [ ] Do not use sync/autosync to link Twinmotion and Rhino. Datasmith save is preferred. * [ ] As a last resort, delete your asset files for smoother running:`locate twinmotion cloud library and delete folder`. l`ocate quixel cloud library and delete folder` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ms-kb.msd.unimelb.edu.au/next-lab/virtual-reality/guides/twinmotion-vr/twinmotion-vr-troubleshooting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.