Troubleshooting common issues when joining existing multi-user sessions.
1. Network issues
Network problems can interfere with your ability to download, update, or launch the modules, and can even block you from hosting or joining a Collaborate session.
To properly access the modules, the headset will need to be connected to the internet via your Wi-Fi network; if you see an error while trying to connect the headset to your Wi-Fi, please check the password for your network and try again.
When the network or internet is insufficient, you may be able to use the hotspot functionality of your mobile phone to create a different Wi-Fi network for the headset to connect to. While this can be a useful workaround, it is important to ensure that the headset is updated before the event, or there may be large file transfers over the hotspot where carrier data rates will likely apply.
Read about other common network issues in our article "Can't connect to Wi-Fi".
2. Different software version
Joining or hosting a collaborative session might fail if participants are not all using the same software version of the application. While in the PrecisionOS app, tap the “?” button from the top of the case description panel to find the version number. If participants are using an older version of the software, they should update their module from the Oculus library. If needed, read more about how to find your app version number.
3. Headset sleep timeout
The headset will also be disconnected from a collaborative session if it goes to sleep. The default sleep timer is only 15 seconds, so taking the headset off for any longer than that means you will need to rejoin the session. This can cause problems when there are multiple users, so to extend that sleep timeout:
- Put on the headset.
- Press the Oculus button on the right controller.
- Select Settings from the Oculus toolbar.
- Select "System" from the Settings list that comes up.
- Scroll down and select "Power".
- From the drop-down, change the Headset Auto-Sleep to the desired setting.
4. Guardian issues
While participating in a collaborative session, leaving the Guardian boundary you set up will result in being disconnected from the session, and you will need to rejoin the session using the 4-digit Meeting ID. It is then a good idea to clear out the space that will be used for the session so that the Guardian zone can be set up in advance of the event.
In instances where the headset will be taken off or be shared between users, it is a good idea to mark off a spot in the middle of the Guardian zone and ensure that the headset always remains in that location when not actively used; this will prevent the headset from being disconnected from the procedure.