Still no response or update. I have several PCs, all have this issue with a Quest 2. I can't speak for other devices, but this is kind of ridiculous. Any chance of making a fix or providing an answer that isn't "report it as a bug"? I mean... considering that is exactly what people here are trying to do by posting here...
Hey there! We are just following up with you in order to check and see if you still need assistance with your Rift audio settings. If you do still need help, feel free to reach out to us anytime!
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
No, this is the same response you gave in the last post. There's no reason Quest Link needs priority over other audio devices. If it does, then it needs to drop the priority when the application is closed. Fix your product.
Hey @Stymiez, if setting another audio device as primary as was recommended in the other thread did not work for you, you can try a clean uninstall and reinstall of your Oculus desktop app to make sure that everything is up to date on your system:
Disconnect the Rift/Link cable from the computer
Disconnect your computer from the internet
Backup any necessary content. You can find steps on how to do so by clicking here.
Reboot into Safe Mode. You can find steps on how to do so by clicking here.
Uninstall the Oculus PC app using the Control Panel. You can find steps on how to do so by clicking here.
Delete all Oculus folders from the following folder:C:\Program Files
Remove any Oculus folders from the following locations:
C:\Users\YourUserProfile\AppData
C:\Users\YourUserProfile\AppData\Local
C:\Users\YourUserProfile\AppData\LocalLow
C:\Users\YourUserProfile\AppData\Roaming
C:\OculusSetup-DownloadCache
Restart your computer in normal mode
Reconnect your computer to the internet
Install the Oculus PC app again using the setup tool from our website here
Reconnect the Rift/Link cable and re-test the headset
Hopefully that gets things working as you hoped. If not, the next step would be to get this reported to the developers directly.
If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
oh hey nothinburger replies with non-fixes. This happens every single time I try to use my headset on the PC and is a strong reason I will never get a quest 3
Hey there, @KoburaCape and welcome to the community forums! 👋
I can certainly see how frustrating it can be having to change your default audio device on PC when using Quest 😓
This however is not a fault of the Quest and is due to how Windows interacts with audio-out devices such as speakers, headsets, earphones etc. As the headset has speakers, Windows will assume this is where the audio should be routed to. The same can be experienced when connecting any game controller or similar device that has an audio jack 🎮
There may be a way to change this through Windows advanced sound settings but it is not a bug with your headset and is just how Windows prioritizes default audio. Hope this helps explain things 🙂
I have other devices, VR and non-VR related audio and only the Quest 2 and Meta has this issue. I also have several game controllers and remote peripherals, and again, no issue.
If I was a company like Meta, I'd probably be discussing and troubleshooting with Microsoft to improve compataibility. Instead, you're blaming the customer and condescendingly making their experience "Frustrating".
These responses are very telling of Meta's commitment to, and apparent resentment toward their own customer base.
This was never resolved and I gave the Quest 2 to my nephew. This response is here to assist others deciding on whether to both dealing with a company that seemingly indifferent to their customers experience.
I think its funny you choose to continue to blame Meta for something they have no control over. Oddly enough you note that you have multiple PC's having the same issue as if its not something other than the OS.
I too am having the same problem, though as stated, it does seem to be a Windows problem. So if you can overcome your incompetence Microsoft would be who you should try contacting for further support.
Bashing Meta for something out of their control changes nothing. Hope this helps, good day.
