# Troubleshooting ## Troubleshooting VR Set-Up WIP Most errors concerning the VR setup are commonly related to disconnected USB/display/network/power cables, even with the awesome portable setup we’ve got running. In which case, turning both the computer and technology on and off, disconnecting and reconnecting cables, rebooting programs and user accounts, are all effective simple solutions to attempt before pulling out the big guns. ### Base Stations are in the Wrong Mode (a-a or other) The Base Stations need to be on separate channels. One on A, one on B. Press the Channel button on the base stations so that one is set to Channel A and one is set to B. ![Figure 1.1 Mode Button and Display Location](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FTaJJGXUfJ7dL8ynSlrhs%2Ffile.png?alt=media) ### Base Stations are not connecting in SteamVR The Base Stations need to be on separate channels. One on A one on B. Press the Channel button on the base stations so that one is set to Channel A and one is set to B. 1. Ensure both stations are receiving power 2. Reset base station 3. Check power brick 4. Potentially a channel issue (see wrong mode) 5. Use a sync cable. For a guide on if you need a sync cable, see [vive.com](https://www.vive.com/au/support/vive/category_howto/do-i-need-to-use-the-sync-cables.html) ![](https://1820679795-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXautSvCbUco5Lv7YrH%2F-LifHtiE4hpE3TTa4zXd%2F-LifIlDMXuxqTMYX_GpX%2Fsynccable.png?alt=media\&token=9fb7a9ec-5caf-4305-83cc-5127a4495b0f) ### Connecting to Steam Account #### abp\_fablab \[Windows Security log-in] 1. Close all running Steam programs. 2. Log-in with admin username and password*:*\ For the MSD VR Trolleys, the log-in credentials are as follows (unless otherwise shown on the device):\ Username: `msd-vr` \ Password: `Passw0rd` Log-in should only be necessary when Steam account is first attempting to sign into the `abp_fablab` account and computer start-up. ### Headset not Detected #### ERROR 108 Attempt disconnecting USB/HDMI on both sides of the adapter, and reconnecting. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2F0b033Gq3lo6Q6mJt3phJ%2Ffile.png?alt=media) ### Controllers not Detected 1. Ensure both have power 2. Troubleshoot: Select `[Troubleshooting]` If Steam VR is having trouble detecting controllers that are clearly visible to the base sensors, the issue may be that they have not been calibrated to the specific VR trolley set in use. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FoBvgjn67k9N3wAGxm09y%2Ffile.png?alt=media) ### Compositor is not Full-Screen The compositor is basically a pre-render or arrangement of layers (depth), in the form of a window (game or program) Make compositor (or game window) full screen to fix this issue ### Compositor not Available 1. **Unplug and plug back in everything** at the hub. Ensure that the cables are in the correct orientation. Unplug the **HDMI**, **DP** or **MiniDP** from the tower and plug it back in. 2. **Try another output** on the tower. ### Flickering HMD *May only apply to setups in other rooms/spaces without a predefined working setup* Play Area has been set up awkwardly in relation to the maximum viewing angles of the Base Stations. Base Stations have a viewing angle of 120 degrees. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LXautSvCbUco5Lv7YrH%2Fuploads%2FaRh6Gnfg26eefwtylJ8r%2Ffile.png?alt=media) ## Common VR File Problems 1. Can’t Move: No Navigation Bounds/Player camera is outside of these bounds 2. Loads empty/Signs of falling: Collision not properly generated 3. Can’t look around: No automatic player possession ## Error Codes WIP {% embed url="" %} ## Headset Errors WIP {% embed url="" %}