Skip to content
This repository has been archived by the owner on May 3, 2021. It is now read-only.

Controllers unpair after shutdown and get stuck on step 3/7. #113

Open
LambdaHidden opened this issue Mar 24, 2020 · 1 comment
Open

Controllers unpair after shutdown and get stuck on step 3/7. #113

LambdaHidden opened this issue Mar 24, 2020 · 1 comment

Comments

@LambdaHidden
Copy link

LambdaHidden commented Mar 24, 2020

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.

@LambdaHidden
Copy link
Author

LambdaHidden commented Mar 25, 2020

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)

image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant