AI-generated Key Takeaways
-
Address degraded controller performance by ensuring controller visibility, power cycling the controllers and faceplate, changing batteries, and adjusting lighting conditions.
-
Resolve flaky Bluetooth pairing by power cycling the controller or re-pairing it if necessary.
-
Preserve battery life by unplugging the faceplate when the headset is idle and turning off controllers when not in use.
-
Utilize community resources like GitHub to report issues or seek assistance with Google VR SDK for Unity and Unreal Engine.
Degraded controller performance
If controller tracking performance degrades, gets stuck in position, or disappears completely, try these steps to remedy it:
Bring the controllers in view of the faceplate.
Unplug the faceplate and then plug it in again.
Power cycle both controllers.
Replace the existing batteries with fully charged AAA batteries.
Try moving to a room with different lighting conditions. (Fluorescent lighting and HTC Vive lighthouses are both known to interfere with tracking.)
Flaky Bluetooth pairing
- If bluetooth pairing becomes flaky, power cycle the controller. If this doesn't fix the issue, re-pair the controller.
Battery life
Save battery life on the headset by unplugging the faceplate when not using the headset for extended periods of time. Keeping the experimental 6DoF faceplate plugged into the Mirage Solo significantly reduces the battery life in standby.
Save battery life on the controllers by switching the controllers off when you’re not planning to use them.
Community troubleshooting
If you're looking for help with Google VR SDK for Unity, you can report issues or submit feature requests on GitHub.
For help with Google VR SDK for Unreal Engine:
- Access Unreal Engine 4 C++ source code via GitHub.
- Visit the Epic's EpicGames/UnrealEngine GitHub repository. This will also allow you to access Google's googlevr-unreal/UnrealEngine GitHubrepository, which is forked from Epic's repository.
- Report your issues or submit your feature requests.