Troubleshooting Quest

Unfortunately, there is no way to remotely connect to a quest headset for troubleshooting, If an issue comes up with a headset, the player will need to take off the headset and give it to the VR operator to fix the problem.

Table of contents

Maximum Number of Headsets

  • While our software does not actually limit the number of players that can join the game, officially, VRCave software supports up to 5 players for all of our escape experiences. We understand that running 6 or more players may be desirable sometimes, there are some issues that can happen when the limit is exceeded.

Problems possible with 6 or more players:

  • playspace is too crowded, people run into each other more

  • some gameplay will not have enough activities for all 6 players to do, so it’s more likely some players will be bored

  • more likely for players to block the headset cameras of other players leading to more likelihood of tracking loss

  • there’s a possibility of performance drops (stuttery graphics) due to the headsets having more to draw on screen. I don’t think this is especially likely but we validate the graphical performance up to 5 players.

Operators Menu

  • To access Operator controls from within a player headset, you can unlock the Operator Menu by pressing this button combination. Remember to lock the Operator Menu after you are done by repeating the button combination. You do not want players to have access to this.

A B B A X Y X

  • After entering that command, pressing X on the controller will toggle the menu below

  • From this menu, you can start the calibration process, clear the current calibration, enable teleportation movement and have access to the server operator controls.

Server Crashes on startup

  • Any time the game crashes on the Server PC, the first thing to check is the PCs graphics drivers. Make sure they are updated to the latest version. For Nvidia graphics cards, you can go to their website and download Geforce Experience to automatically update your graphics drivers.

  • if you are getting a crash report with the line above in it. Then the issue may be caused by steamVR expecting a VR headset when the server is launching. to fix this, right click on your startup shortcut and select preferences. In the Target path, add this line to the very end:

-nohmd

Sideloading is not detecting the headset

When you are sideloading to a headset, you should get 2 popups in the headset when it is plugged into the PC, One will ask to allow access to files on the headset. the other will ask to allow USB debugging. the USB debugging popup is the one that allows for sideloading and will only come up when the Install_VRcaveLibrary-arm64.bat has been run at least once, you you are not getting that popup when you plug in the headset and run the install file, try the following steps:

  1. If you have not sideloaded on the headset before, you will have to follow these instructions

  2. If the headset has been sideloaded before, Go to your Meta Quest App on your phone or tablet and navigate to the devices page.

  1. Select the headset from the list, and then touch the Developer Mode option in the headset settings section

  2. Enable Developer Mode, If it is already enabled, disable it, then re-enable.

  3. If the headset continues to fail to sideload, log out from the app, log back in and repeat steps 2-4

Quest headset not joining game

  1. Confirm the quest is connected to the correct wireless network.
  2. Check that the quest is trying to connect to the server. You should periodically see a message pop up in the upper lefthand corner of the HMD. If the are no messages, then

  3. Close the VRCave Library application and start it up again.

  4. Check the server PC for any Firewalls that are overriding Windows Defender Firewall. Try disabling them temporarily to see if that is why headsets are not joining the server. If they are, find a way to create a firewall exception for vrcavelibrary.exe to allow for internet access.

  5. NordVPN has a firewall that runs more secretly than other firewalls. It is best to just uninstall NordVPN if it present on the server computer.

  6. On the server computer, make sure there is only one network connected and enabled.

  7. You can also check your network environment by opening a command window and typing the command ipconfig. you should only see one category filled with information like the image below.

Quest players cannot see each other after starting game or changing games.

  1. This issue should be very rare, however, we have discovered that other games using Unreal Engine, eg. HeroZone, can take over a local network on a server PC. Make sure any other game is shut down, then restart the vrcave lobby and try to connect again.

Quest player is frozen in place in the game

  1. This usually happens because the quest lost tracking and a popup came up, This popup has a button on it and most peoples first reaction is to press the button. unfortunately, the button turns off tracking.
  2. Minimize the vrcave librabry by holding the oculus button and find press the tracking mode button. re-establish roomscale tracking.

Quest is not finding its guardian boundries

  1. This happens sometimes on startup, the quest does not recognize the room for whatever reason. put on the headset and look around the room slowly. eventually the guardian bounds will be found.
  2. If the guardian bounds do not recover, then you can ethier restart the Quest headset, or begin the process of redrawing new guardian bounds.

Fixing calibration issues

  • VRCAVE calibration should persist when the headsets go to sleep or are shut down. However, it is possible for the calibration to be lost. This usually happens if the headset lost the guardian, found another from memory, and returned to the previous guardian, or the guardian had to be redrawn.

  • In this case, the best thing to do is:
    1. Reboot the headset
    2. Redraw the guardian (if it is not restored on it’s own)
    3. Perform VRCAVE calibration

  • If the headsets are constantly shifting their height and position, then you may need to clear your guardian history. To do this, go to Settings -> Physical Space -> Boundary -> Clear Boundary History

  • After you clear your Guardian Boundary history, you will need to re-draw your boundary and recalibrate in vrCAVE

Getting a “failed to save anchors” message after calibrating

  • The Quest Headset will need to have the privacy setting Share point cloud data in the Privacy section of the Quest settings turned on to use spatial anchors. Without this setting, the headset may fail to save the spatial anchors when calibrating.

Stackwalk2 popup Error, or other .dll conflicts

  • This issue looks like an error message that comes up when launching vrcave, a popup comes up that says something like The procedure entry point StackWalk2 could not be located in the dynamic link library followed by a folder path. closing the popup a bunch of times will eventually open vrcave.

  • To prevent the error from poping up, you have to navigate to the thirdparty binary files in the vrcave folder and delete the DbgHelp folder. it can be found here: vrcave\Windows\Engine\Binaries\ThirdParty

Operators Menu

  • To access Operator controls from within a player headset, you can unlock the Operator Menu by pressing this button combination. Remember to lock the Operator Menu after you are done by repeating the button combination. You do not want players to have access to this.

A B B A X Y X

  • After entering that command, pressing X on the controller will toggle the menu below

  • From this menu, you can start the calibration process, clear the current calibration, enable teleportation movement and have access to the server operator controls.