Vive Headset Keeps Losing Base Stations

[TheInsomniac]

ISSUE
Since the 1.8.21 update, my Vive headset will not stay connected to the base stations except if the sync cable is used, which is not convenient in my particular case. Have not had desync issues like this since I installed the system.

OS
Windows 10

STEPS
1. Open SteamVR or VR game as normal
2. Begin playing

RESULTS
After a random amount of time, tracking becomes inconsistent, and the SteamVR overlay on my desktop shows one or both of the base stations not being detected. They will go through cycles of connection and dropout, with no particular pattern.

EXPECTED
Smooth tracking that I've enjoyed since setting up the system.

MEASURES I'VE ALREADY TRIED
- Rebooting computer
- Rebooting Vive
- Checking tool integrity for SteamVR
- Opting into (and out of) the latest beta
- Re-doing room setup
- Check base station power supplies
- Covering any potentially reflective surfaces around playspace
- Power cycling base stations

The only fix I've found so far is to connect my base stations using the sync cable, but for practicality's sake, it is not a permanent solution for me.

Thanks for helping me resolve this issue!

[bendotcom]

If the sync cable fixes the issue, then the problem is that the base in mode "c" is having trouble seeing the base that is in mode "b". The "c" base needs to see the "b" base to maintain sync. One common way to hit this issue is to set up the bases at body height and then walk between them. When directly between them, base "c" will (after a few seconds of coasting) turn off.

The first thing to try in this case is usually to swap the "b" "c" roles using the buttons on the back of the base. If you've been plugging in the sync cable (and setting them to "a" + "b") you are familiar with the button.

Slight changes in the aim of the "c" base can also help, since it is possible for the "c" base to see the light from "b" bounce off of a wall or ceiling and get the signal it needs.

[TheInsomniac]

Originally posted by bendotcom:

If the sync cable fixes the issue, then the problem is that the base in mode "c" is having trouble seeing the base that is in mode "b". The "c" base needs to see the "b" base to maintain sync. One common way to hit this issue is to set up the bases at body height and then walk between them. When directly between them, base "c" will (after a few seconds of coasting) turn off.

The first thing to try in this case is usually to swap the "b" "c" roles using the buttons on the back of the base. If you've been plugging in the sync cable (and setting them to "a" + "b") you are familiar with the button.

Slight changes in the aim of the "c" base can also help, since it is possible for the "c" base to see the light from "b" bounce off of a wall or ceiling and get the signal it needs.

Well, I thought the sync cable had fixed the issue, but I've continued to have intermittent desync even with the cable. I went back and disconnected the cable, switching B and C per your recommendations and it still loses connection. I've tried realigning the stations, re-running Room Setup, and still have the issue. The base stations are well above head height so blockage should not be an issue, and as I said before, I've had the system positioned as-is for well over a year and never had issues. In fact, I hosted a VR party just a couple of days before the update and had zero sync issues.

I don't mean to randomly point fingers, but after incremental testing and tweaking, the only difference I can find between when the system worked and when it didn't is the software update.

Thank you for reaching out to help!

[TheInsomniac]

UPDATE

Upon further investigation, the issue seems to be isolated to one base station. This station's LED intermittently changes from green to blue, which as I understand means it isn't stable. However, I have not moved the mounting point from where it has always been, and there is no new source of vibration. The only vibration on the unit is from its internal fan.

Again, this issue did not start until after the 1.8.3 update; could it perhaps have affected the base station's stability sensing?

Thanks!