Quest v65 Update

[Dogmanbird]

Just a heads up - seems a lot of people on reddit are getting stuck at the "updating" message and doesn't seem to make progress (including me), even after hours of waiting. The solution appears to be to click cancel / open settings and system / check for updates and then apply update. Should only take about 5 minutes to complete

 

 

[YoYo]

My friend had this update yesterday (goggles v65) - after that his Link Cable connection stopped working (Quest 3).

I went to him today to check his settings. Everything seems to be OK. This update messed something up. He checked on 2 cables (in fact, there are no original ones), the goggles don't see the PC on either of them. Previously (dey before the update) there was no problem.

Edited May 17, 2024 by YoYo

[Dogmanbird]

going from v63 to v64 affected our cables. Still got issues here after v65. I got the v65 update for pc and headset within minutes of each other.

I have one headset still at v63 and it works on all the cables regardless of usb-c orientation or connecting order

[Qcumber]

I have been running v65 on my quest pro for a few weeks and I have no issues. Is this just affecting Quest 3? 

[YoYo]

1 hour ago, Qcumber said:

I have been running v65 on my quest pro for a few weeks and I have no issues. Is this just affecting Quest 3? 

Orginal cable of Meta?

[Qcumber]

24 minutes ago, YoYo said:

Orginal cable of Meta?

I'm using a third party cable. 

[Dogmanbird]

5 hours ago, Qcumber said:

I have been running v65 on my quest pro for a few weeks and I have no issues. Is this just affecting Quest 3? 

a month back with v64, it was affecting the cables we're using on qpro, q2 and q3. The q3 was the fussiest to get connected and show as usb 3, where the other two would connect consistently but often show up as usb2. I've only tested quest3 with 65 so far.

[Qcumber]

43 minutes ago, Dogmanbird said:

a month back with v64, it was affecting the cables we're using on qpro, q2 and q3. The q3 was the fussiest to get connected and show as usb 3, where the other two would connect consistently but often show up as usb2. I've only tested quest3 with 65 so far.

I had this issue around the time of v63 and bought a new cable which cured it. I've not tried the old cable since. Wonder if my issue was a problem with an earlier meta release. 

[Dogmanbird]

it would be interesting to see. Was v63 your first headset software? I've been experiencing usb connection variations each update since about v60. v64 & 65 have been my most troublesome. I think I first started with v5 point something.

I'd imagine the differences in motherboards may play a part in it too

[Qcumber]

9 minutes ago, Dogmanbird said:

it would be interesting to see. Was v63 your first headset software? I've been experiencing usb connection variations each update since about v60. v64 & 65 have been my most troublesome. I think I first started with v5 point something.

I'd imagine the differences in motherboards may play a part in it too

I started with v62 in January then through the various updates which affected most people with DCS but I was ok. Just an issue with the cable dropping out and not connecting. I replaced the cable around the same time v64 came out so not sure if the new cable solved my issue or v64. I'm away from home for a week but will try my old cable when I get back. 

The only difference with the cables is that the new one has a separate charging port. My first cable relied on power from the USB port. 

[slughead]

I was on v65, no issues. Now on v66 (PTC), still no issues.

[VR Flight Guy in PJ Pants]

It was a hit or miss, even before V64, it was rare but still the headset was not connected (Quest Pro, VR Cover cable). More often would be having the sound really choppy. Disconnecting and reconnecting solves the problem all the time.

[JesterIsDead]

This update is a big improvement for me. I can connect to the cable so much easier. Works like a dream now.

[YoYo]

46 minutes ago, JesterIsDead said:

This update is a big improvement for me. I can connect to the cable so much easier. Works like a dream now.

Good to know!

[diamond26]

V65 works as expected on a Quest Pro

[Cybet]

I was away from DCS for a bit, but had everything working with my Quest 3. Now that I have returned and my DCS, Quest 3 and Meta Link App up to date to V65, I seem to be experiencing the same problems as users at v63. DCS will start loading when launched from desktop or Link app and once it gets to the version screen it just disappears and does not load further.
I swear I read 50 pages of threads yesterday and feel like I am missing something as when DCS pushed the Meta update all of a sudden everyone was fine and I am missing something.
Is there a critical step I am missing here to get up and running again?

[Dogmanbird]

Try temporarily renaming the    C:\Users\Me\Saved Games\DCS\Config\options.lua    file and then restart the game. It will generate a fresh options.lua file. You'll probably need to turn on the VR option within DCS.

If it works, a recent game update might have imported wrong values. 

[Cybet]

@Dogmanbird I appreciate the suggestion, but no change.

[Cybet]

Problem solved and totally unrelated to Quest 3. It was an old and now incompatible mod found through DCS log.

[Dogmanbird]