Rift Detection Issues - Problem Found

[Tinkickef]

I was not sure where to put this post. Since it is not a DCS problem I did not think it should go in the VR bugs section. If the mods disagree, they are welcome to move it.

 

So for the last week or two I have had rift connection issues and suspected my cable was failing, since the only way to get the rift detected was to disconnect and reconnect the cable at the headset port. Since the cable looked a bit deformed and ragged, it was natural to assume it was the cable and so bought a new one.

 

It was not the cable.

 

Then I found that it was a widespread problem since the last update and looked more closely at various settings and why the rift would be detected some times without problems and not others.

 

TLDR it appears to be some type of audio incompatibility, introduced in the last Oculus update.

 

After lots of experimenting it was found to be audio related.

 

I use voicemeeter to power my buttkicker amp and have done so for a couple of years without problems until now. I found:

 

If I start voicemeeter then start Oculus home, Rift just shows orange light and will not connect.

 

If I start Oculus home without voicemeeter, rift will connect immediately with white LED.

 

If I start Oculus, then start voicemeeter, I lose audio in the Oculus headphones when voicemeeter starts up.

 

If I have lost audio in the Oculus headphones and then open DCS, rift, headphone audio and buttkicker all work fine.

 

So it is some kind of problem with incompatibility in oculus home audio since the last Oculus update.

 

Audio settings.

 

Voicemeeter set to default audio device.

Rift headphones set to default communications device.

Rift audio mirroring on.

Hear non vr apps through headphones on.

DCS use built in audio is off.

 

All the above have worked for years until the last update.

 

Latest Feb 2019 Nvidia driver installed yesterday without result.

 

All these auto updates are starting to grind on my nerves. :mad: