08-06-2024 02:21 AM - last edited 3 weeks ago
I've always preferred using my PC speakers for seated PCVR... nice subwoofer and more defined surround.
V68 seems to prioritise headset output over PC speakers, I have to repeatedly select 'speakers' during a game launch until the setting catches. Yesterday in one instance, it just wouldn't switch from the headset no matter how many time I selected/deselected speakers.... at one point I simultaneously had the game sound coming from the headset and the non-game audio from the speakers.
Anyone else having this issue?
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
08-07-2024 04:04 PM
Hey there, @DaftnDirect! We know how important it is to have your audio configured properly. We're more than happy to look into this together!
The first thing that we would recommend is to try the steps on our Troubleshoot your Meta Quest Link audio page, if you haven't already. It mentions checking your audio input and output settings on both the Meta Quest device, PC, and any third-party programs.
If this doesn't do the trick, we recommend reporting the issue to our engineers directly so they can investigate the matter. You can report the issue on your headset here, and for the Oculus PC software here.
08-10-2024 04:51 AM - edited 08-10-2024 04:52 AM
Yeah I just thought I'd put the question out there to the good people of the forum and get an idea of whether it's just a setting or conflict on my PC, or if anyone else is having this problem in which case it's a bug and I'll go ahead and report it.
Anyway, it looks like this doesn't happen with MSFS 2020 (non-Steam version), so maybe a recent SteamVR update is causing this. So if anyone else has encountered this problem, please let me know... I'm sure I'm not the only one using PC speakers for seated PCVR!
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
08-20-2024 12:21 PM
Hey @DaftnDirect ,
I have another issue but maybe linked to yours :
I updated to V68 and I am now having issues with Quest link for Quest2.
I have audio playing well (in headset, any windows sound or my VR app sound) connected via USB link. If I plug off the headset (Quest link stops in headset, sound still works in headset), then plug the headset in the pc again, Quest link starts again and then I get no sound at all in headset !
Only rebooting the headset solves the issue. This did not happen before v68.
I have check all audio settings and FAQ but everything is correctly set. It is like just the headset audio does not output anything in such case.
08-20-2024 01:53 PM - edited 08-20-2024 01:58 PM
Hi @VirtualWalkVR it's very difficult to say if related or not... but if you never had the issue before v68 then yeah, that's where I'd be tempted to point the finger. Have you done a reboot of your headset?
For my issues it's tricky because so many updates happen around the same time... Windows, SteamVR and the Quest software. Makes it difficult to pin down which is the cause. My issue only happens during Steam games but I guess that doesn't necessarily mean v68 isn't the cause and it's not playing nice with Steam.
For me it basically means I have to start Fallout VR twice and I always get PC speaker sound working properly on the second launch. Non-Steam games, no issue.
For both of is, it would be good if someone else had these same problems. Just to confirm if it's a bug or some issue with our particular headset/PC.
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
3 weeks ago - last edited 3 weeks ago
Just an update that the cause of this issue was tracked down to a SteamVR update that changed its sound setting without my input. Unfortunately it wasn't immediately apparent because the effect was different depending on how and when I set the sound output during the launch of SteamVR.
This happened again last week but this time it was Steam's FOV setting for the an individual game that changed to 80%. So ended up with weird tunnel vision only in Fallout VR!
So just a cautionary note to anyone who suddenly has a random change of behaviour using SteamVR... go through its settings, both general and the per-game settings just in case something's changed without your input.
13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro, Windows 11 Pro 24H2 (10.0.26100)
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
Check out some popular posts here:
Getting Help from the Meta Quest Community
Tips and Tricks: Charging your Meta Quest Headset