You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2021. It is now read-only.
The current PSMoveSteamVRBridge has a bug in the latest update for Windows 10 (I still use W7, but it looks like W10's latest update retroactively added the glitch to previous OS') that causes what the title implies: After pairing a controller and shutting the computer down, it remains paired in the Bluetooth Devices menu, but vanishes in the Config Tool controller list. Trying to pair the controller back gets stuck on step 3/7. I fixed this once by removing the controllers from the Bluetooth menu and all device managers, rebooting and starting fresh, but now it happened again.
My best bet for a fix is to move the SteamVRBridge to the latest version of PSMoveService, which theoretically has fixed the issue.
The text was updated successfully, but these errors were encountered:
UPDATE: As it turns out, there is another bug causing the controllers to refuse to pair. I've got no idea what it is, but hopefully the console output below will help. (W7 Proffesional, SP1, latest update)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current PSMoveSteamVRBridge has a bug in the latest update for Windows 10 (I still use W7, but it looks like W10's latest update retroactively added the glitch to previous OS') that causes what the title implies: After pairing a controller and shutting the computer down, it remains paired in the Bluetooth Devices menu, but vanishes in the Config Tool controller list. Trying to pair the controller back gets stuck on step 3/7. I fixed this once by removing the controllers from the Bluetooth menu and all device managers, rebooting and starting fresh, but now it happened again.
My best bet for a fix is to move the SteamVRBridge to the latest version of PSMoveService, which theoretically has fixed the issue.
The text was updated successfully, but these errors were encountered: