fixed Latest Oculus v63 PTC build crashing DCS when used on Oculus Link

[Qcumber]

5 minutes ago, g5flyer said:

Greetings, what is QP?

Quest Pro. 

[Martuste]

Salut à tous,

Est-ce qu une mise à jours Windows pourrai causer se problème ? , pour moi se sont tous les mise à jours soit, :window11, Le Q3 et le soft oculus.

[YoYo]

19 minutes ago, Martuste said:

Salut à tous,

Est-ce qu une mise à jours Windows pourrai causer se problème ? , pour moi se sont tous les mise à jours soit, :window11, Le Q3 et le soft oculus.

No, not Windows 11 update, just v63 for Oculus Link. Fix is ready, wait for a patch for DCS MT.

Edited March 20, 2024 by YoYo

[Martuste]

Merci pour ta réponse

 

[VirusAM]

15 hours ago, Qcumber said:

Here is my log file. Using QP with headset v63 and app v63. MT and open xr.

dcs.log 45 kB · 7 downloads

Well, in your logs, dcs is the right version and OpenXR is indeed used...

Could you please show a screenshot of the version number on your Meta PC app?As all this is really strange

you find it in Meta PC app, settings, general tab down the bottom of that page.

 

Maybe Quest Pro, and Quest 2/3 have different behaviours so while it doesn't work with the 2 and 3, it works with the Pro.

I am still on v62 so can't try....

18 hours ago, unlikely_spider said:

I as well haven't experienced issues. Running MT. Oculus software v63, headset still seems to be on 62 though.

 

dcs.log 43.8 kB · 7 downloads

 

which quest device do you have?

Edited March 21, 2024 by VirusAM

[Qcumber]

29 minutes ago, VirusAM said:

Could you please show a screenshot of the version number on your Meta PC app?

null

[Qcumber]

One thing I noticed with my headset is that I was already at v63 and had a prompt for another update on the headset so I presume this is a patch of some kind?

Headset version: 63.0.0.327.363.576466842

Runtime version: 63.0.0.324.363.576466932

I didn't make a note of the headset versions before the update. 

One more thing. I needed to delete the FXO shaders before it would run after the update. 

[VirusAM]

41 minutes ago, Qcumber said:

One thing I noticed with my headset is that I was already at v63 and had a prompt for another update on the headset so I presume this is a patch of some kind?

Headset version: 63.0.0.327.363.576466842

Runtime version: 63.0.0.324.363.576466932

I didn't make a note of the headset versions before the update. 

One more thing. I needed to delete the FXO shaders before it would run after the update. 

Thanks...maybe for some reason the quest pro is not suffering from this change...

Another user saw that there are no issues with the new version...I am waiting that he replies on which headset does he use

[Qcumber]

14 minutes ago, VirusAM said:

Thanks...maybe for some reason the quest pro is not suffering from this change...

Another user saw that there are no issues with the new version...I am waiting that he replies on which headset does he use

Do you have v63 on your headset and is it the same version as mine. 

[slughead]

24 minutes ago, VirusAM said:

Thanks...maybe for some reason the quest pro is not suffering from this change...

Another user saw that there are no issues with the new version...I am waiting that he replies on which headset does he use

I have the Quest Pro.

[YoYo]

2 hours ago, VirusAM said:

Thanks...maybe for some reason the quest pro is not suffering from this change...

Another user saw that there are no issues with the new version...I am waiting that he replies on which headset does he use

There are good news for Quest Pro owners! Like me too .

Edited March 21, 2024 by YoYo

[slughead]

9 minutes ago, YoYo said:

There are good news for Quest Pro owners! Like me too .

 

Except I have a quest pro and I’m the one who reported the fault. Now either meta didn’t include the change in the general release, or something else is at foot. Either way, I’m not upgrading to v63 until ED releases a patch.

All this conjecture is somewhat pointless as ED has identified the issue and a fix is being tested. So it’s not a matter of if but when.

[unlikely_spider]

6 hours ago, VirusAM said:

Could you please show a screenshot of the version number on your Meta PC app?As all this is really strange

Yes, it is in my original post above (I am not at my PC at the moment)

I have a Quest 3

Edited March 21, 2024 by unlikely_spider

[slughead]

1 minute ago, unlikely_spider said:

Yes, it is in my original post above (I am not at my PC at the moment)

I have a Quest 3

 

Wasn’t the Quest 3 at version 63 from release? If so, it possibly was a version that didn’t break DCS. You may still be online for the update that will break DCS.

Sometimes it’s taken more than a month from the start of roll out until my headset gets the update as they release in batches.

[VirusAM]

32 minutes ago, slughead said:

Wasn’t the Quest 3 at version 63 from release? If so, it possibly was a version that didn’t break DCS. You may still be online for the update that will break DCS.

Sometimes it’s taken more than a month from the start of roll out until my headset gets the update as they release in batches.

yeah maybe a v.63 sub version...

We need to compare the one above, which the user reports as working, with another one which doesn't work

[slughead]

Just now, VirusAM said:

yeah maybe a v.63 sub version...

We need to compare the one above, which the user reports as working, with another one which doesn't work

CBA. What’s the point? It still needs patching.

[VirusAM]

9 minutes ago, slughead said:

CBA. What’s the point? It still needs patching.

My understanding was that  v63 on PC app means no go for DCS....I am still on v62 so for me everything is working.

Still there are at least two users which reports it working.....as a tester, I am trying to understand why is that.

If there are multible subversions of v63, then 1 in particular has the API change which is not compatible with the latest DCS version....understand if so, and which one may help.

And if this is not the case, then...it would be beneficial to understand why this is working for some users, and not for almost all others.

Edited March 21, 2024 by VirusAM

[unlikely_spider]

45 minutes ago, slughead said:

Wasn’t the Quest 3 at version 63 from release? If so, it possibly was a version that didn’t break DCS. You may still be online for the update that will break DCS.

Sometimes it’s taken more than a month from the start of roll out until my headset gets the update as they release in batches.

For what it's worth, the headset itself states v62. Just last night I turned off auto-update in the headset.

[slughead]

1 minute ago, VirusAM said:

My understanding was that  v63 on PC app means no go for DCS....I am still on v62 so for me everything is working.

Still there are at least two users which reports it working.....as a tester, I am trying to understand why is that.

If there are multible subversions of v63, then 1 in particular has the API change which is not compatible with the latest DCS version....understand if so, and which one may help.

And if this is not the case, then...it would be beneficial to understand why this is working for some users, and not almost all others.

But you have no control over what meta decides to push to your device. Just all seems a fruitless exercise when ED knows what the problem is, has implemented a fix and will release it in the next build.

Slughead out.

[13sq*Axe]

1 hour ago, unlikely_spider said:

Yes, it is in my original post above (I am not at my PC at the moment)

I have a Quest 3

This is the same PC App version I have and DCS/Oculus is working  for me with my Q3.

 

[DCoffey]

On 3/20/2024 at 7:59 AM, unlikely_spider said:

I as well haven't experienced issues. Running MT. Oculus software v63, headset still seems to be on 62 though.

 

dcs.log 43.8 kB · 8 downloads

 

How do you take a screenshot in VR?

[unlikely_spider]

16 minutes ago, DCoffey said:

How do you take a screenshot in VR?

I just took the headset off, alt-tabbed out of DCS, then Print screen key

[Flogger23m]

Is this still an issue with Quest VR headsets, including the Quest 2? Is there anyway to not auto updated Meta VR headsets? Or is it mandatory each time you plug the VR headets in it while having an internet connection? If so seems like a massive oversight.

[rob10]

2 hours ago, Flogger23m said:

Is this still an issue with Quest VR headsets, including the Quest 2? Is there anyway to not auto updated Meta VR headsets? Or is it mandatory each time you plug the VR headets in it while having an internet connection? If so seems like a massive oversight.

Yes, No, and see earlier parts of thread to avoid it if it hasn't already automatically updated you.
Unfortunately when it's two unrelated companies and something that only effects a subset of users it's hard to not have hiccups like this.

[Lange_666]

5 hours ago, Flogger23m said:

Is this still an issue with Quest VR headsets, including the Quest 2? Is there anyway to not auto updated Meta VR headsets? Or is it mandatory each time you plug the VR headets in it while having an internet connection? If so seems like a massive oversight.

This is how you can block an update:

 

Also, when blocking is in place you may see the taskbar blink (or shift if centered) briefly every 5 minutes. This is NOT a Windows problem but Oculus VR Runtime service checking for an update even if Oculus main software isn't running. If you stop it, the blinking stops until the next reboot.