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

[YoYo]

9 minutes ago, majorandme said:

A great Easter present would be a DCS update AND the F-4E release!  And a big-ass chocolate bunny as well. Lets not be too demanding!

Dont wait for F-4E in incoming patch, next maybe or even May, not now Im sure 100% .

[majorandme]

4 minutes ago, Dogmanbird said:

did you stop the oculus service prior to copying, then restart service prior to starting the oculus app?

  I used the solution from TheIziWarrior  Up above.  It got me up and running.  Not as good going through Steam, but at least running for now.  Thanks Brother! 

[Dogmanbird]

glad you got it working anyway

[rob10]

Just an FYI -- seeing reports that a headset update for Quest went out last night that has completely broke them for ANY use currently (can't set boundary etc.).  So it may be more than a DCS issue occurring for some currently.

[Qcumber]

5 hours ago, Qcumber said:

OK. So I have just checked my headset and there is an update waiting. I presume the ".400." version is the one which breaks everything. Maybe these are being pushed out to QP later than Q3. I'm not going to upgrade until I have to (24th April). 

OK. So I have updated my headset to the "400" version and DCS still runs fine. I am out of ideas as to why it works for some and not others. 

[Alexfly65]

The FIX above worked for me too. With the first attempt it didn't work because I had completely replaced the 3 original folders with the downloaded ones.
It is necessary to overwrite the original folders, not replace them. The version always shows me V. 63, but now it works!
However I hope EA will fixes this bug soon.

[minimi66]

8 hours ago, VirusAM said:

Asking for a friend.....
Does it work also with the Rift S?
Ps nice to see you posting again..I hope all is good

Sadly none of the above worked for me.  I will now wait for the DCS update/Fix.  Wasted enough of my life on this already!

[ESA_maligno]

Mismo problema con las Q3.............

Same problem whit the Q3.............

[koen330]

Same problem here (on Quest 3). I played DCS, stopped for half an hour. I wanted to continue and BAM, crashing on startup. Probably the Oculus update was pushed at that time.

I started investigating, running the cleanup, etc...Looking on internet didn't bring me to this page, as I was looking for DCS crash on start-up, not realising it was the VR part.

After a couple of hours I decided to reinstall everything. Jippie, everything worked again (I thought) as the first times I started DCS after the re-Install it was stil in 2D. Me happy again, until I tried VR again, and crashing...:(

Realising it was the VR part, I ended up finding this tread. Unfortunately I lost a couple of hours....

Some communication about this problem would have been nice. 

The above mentioned fix did it for me. I can play again in VR. Still I hope an official fix will come soon.

Edited March 27, 2024 by koen330
typo

[Shibiswag]

On 3/10/2024 at 2:47 PM, psycho said:

Hi, I'm also affected by the problem with a Quest 3. I don't know about you but I don't have an option to prevent oculus link from updating.
While waiting for the patch I work around with Steam VR, it works.

 

How do you do the work around using SteamVR?
I have the same problem.

[spiffyy]

I don’t want to sound sceptic just genuenly curious on how ED will fix this issue.

 

For me it seems the root cause lies between Oculus app and OpenXR.

And because OpenXR cannot utilize the HMD, DCS cannot start.

 

So how will ED devs will fix this when the issue is a broken link between the two 3rd party app.

 

But I have all my faith in the devs, hope they can pull something!

[slughead]

15 minutes ago, spiffyy said:

I don’t want to sound sceptic just genuenly curious on how ED will fix this issue.

 

For me it seems the root cause lies between Oculus app and OpenXR.

And because OpenXR cannot utilize the HMD, DCS cannot start.

 

So how will ED devs will fix this when the issue is a broken link between the two 3rd party app.

 

But I have all my faith in the devs, hope they can pull something!

ED have already said that they have implemented the fix.

[Qcumber]

13 minutes ago, spiffyy said:

For me it seems the root cause lies between Oculus app and OpenXR.

And because OpenXR cannot utilize the HMD, DCS cannot start.

That might be the case but it's not affecting everyone who use oculus. I can run DCS fine including QVFR and OXRTK. I don't know the scale of the issue. There are maybe 50-60 people affected in this forum but how many people use oculus VR in VD. A lot more than that. 

[Aries Avenger]

@SlugHead . . . hey brother can you provide any other details on this said "ED Fix"?

Where did you hear this?

[Shibiswag]

Anyone who used the steam workaround?
What settings do you use.
I can actually get into the game via oculus link into steamVR and launch it from there, from the guide that was posted.
Getting horrible FPS though, talking like 5-10 with severe pausing and choppiness.
So for someone using the work around, could you tell me your settings for both oculus, including the tray tool and the steam settings.
Would be much appreciated.
Thank you.

20 minutes ago, Qcumber said:

That might be the case but it's not affecting everyone who use oculus. I can run DCS fine including QVFR and OXRTK. I don't know the scale of the issue. There are maybe 50-60 people affected in this forum but how many people use oculus VR in VD. A lot more than that. 

What version of oculus are using? V62, 63, or 64?

13 minutes ago, Aries Avenger said:

@SlugHead . . . hey brother can you provide any other details on this said "ED Fix"?

Where did you hear this?

I can't seem to find anything on it either, though from various users, I have been told that ED has fixed it internally and are currently testing it to make sure it doesn't break anything esle.
That the fix will come out in the next patch whenever that will be.
Could be a day, a week, a month.
No one knows.

[slughead]

15 minutes ago, Aries Avenger said:

@SlugHead . . . hey brother can you provide any other details on this said "ED Fix"?

Where did you hear this?

Yeah, read back up through this thread. They're continually saying it will be fixed in the next release. You only need to back one page. 

Edited March 27, 2024 by slughead

[Dkha]

I tried in all possible ways (Quest Link, SteamVR and Virtual Desktop) and nothing happened. Isn't it possible to release this patch for fixing things easier?

[Shibiswag]

1 hour ago, slughead said:

Yeah, read back up through this thread. They're continually saying it will be fixed in the next release. You only need to back one page. 

 

ah okay, good to know.

12 hours ago, data790 said:

Thanks so much. This got mine back up in no time. Though it still states in the Oculus app on my desktop V63...... but it works, all that matters. Some additional hoops so let me explain how I got this working for folks like me that need a step-by-step (ooooh baby etc...):

1. download the client and runtime from here.

 2. stop oculus app: windows key and type "services" find "OculusVR Runtime Service" and right click to bring up properties.

3. "startup type" set to manual and apply.

4. restart the computer.

5. open C, programs, Oculus, support, save the files "Oculus-client" and "oculus runtime" as a backup (not needed but good practice)

6. copy downloaded files into each of these folders.

7. if files stop then something is triggering oculus software.

8. when complete, start oculus software and disable automatic updates, do the same on the headset if needed.

9. this should now boot up DCS as before.

I am running windows 11 with quest 2 and the above has solved the issues for me.

 

Thanks to everyone listed in the above links to making this available. Hope this helps as I have had to dig around a bit to find out how to stop services and what not. 

Confirmed this worked for me as well.
My system:
Oculus Pro
Ryzen 9 5900X
7800XT 16GB
64GB 3200 DDR4

[Ramstein]

I went through replacing those Oculus from the Reddit DCS thread. it works, but I went though hours of HELL I will never get back. Stop the Oculus services, then replace with the previous versions /Oculus/Support/....  that were saved by someone who set them up for download. Not their fault, but we had 3 power outages while I was working on this! On stand by my comments online in several forums on how much I hate Meta, Oculus,, etc..etc...

 

I am not a child, but a dream would be a Meta Oculus Hate fanclub page on the Internet...

Edited March 28, 2024 by Ramstein

[omohat]

17 hours ago, BIGNEWY said:

 

We have a fix that has been tested internally for the next patch, we did see some issues during the tests with third party VR software that also complicated the fix, the long and short of this is complex software will always be a challenge and things will break from time to time. Thank you all for the feedback and for the crash logs, and also for community members who have found various work arounds. 

I hope I can share the patch date with you all soon, I am waiting for the all clear from QA before I update the patch status post. 

thanks

While we wait for you to confirm patch date, any chance you can give us some indications of which 3rd Party VR software you're seeing issues with when testing the fix. I'm really really hoping its not QVFR and OXRTK 

Edited March 28, 2024 by omohat

[Qcumber]

7 hours ago, Shibiswag said:

What version of oculus are using? V62, 63, or 64?

V63 on both headset and PC app. On the headset it is 63.0.0.400. I updated to the latest versions yesterday which stated these would be the mandatory updates from 24th April. There are others who are unaffected too (3-4 that I am aware of from this forum) but I don't know how many because many don't access the forum and are blissfully unaware that some people are having issues. BigNewy did state in his message earlier in this thread that there were some issues resolving the original problem related to third party software. I am speculating that I don't use said third party software. 

1 hour ago, omohat said:

While we wait for you to confirm patch date, any chance you can give us some indications of which 3rd Party VR software you're seeing issues with when testing the fix. I'm really really hoping its not QVFR and OXRTK 

 

I am using OXRTK and QVFR with no issues on the latest v63 update so I don't think it's these. XRnecksafer works fine too. 

[coolts]

7 hours ago, Ramstein said:

I went through replacing those Oculus from the Reddit DCS thread. it works, but I went though hours of HELL I will never get back. Stop the Oculus services, then replace with the previous versions /Oculus/Support/....  that were saved by someone who set them up for download. Not their fault, but we had 3 power outages while I was working on this! On stand by my comments online in several forums on how much I hate Meta, Oculus,, etc..etc...

 

I am not a child, but a dream would be a Meta Oculus Hate fanclub page on the Internet...

 

This is for ED to patch, not Meta.  I'm no Zuk fan, but there is a workaround.  Use the Quest as god intended, wirelessly.  Honestly, you wont go back to having  a cable dangling over your shoulder*.

*(once you've spent a month faffing with bit rates, researching codecs and routers and wishing you'd bought a pimax).

Edited March 28, 2024 by coolts

[jurinko]

8 hours ago, Shibiswag said:

Anyone who used the steam workaround?
What settings do you use.
I can actually get into the game via oculus link into steamVR and launch it from there, from the guide that was posted.
Getting horrible FPS though, talking like 5-10 with severe pausing and choppiness.
 

If you use openxr toolkit, switch off turbo mode. 

[BIGNEWY]

 

Totally understand not wanting to mess around with work arounds, we can only apologies for the inconvenience the meta patch has created. 

We have a fix for the next patch so it is just a matter of waiting for the patch, as mentioned previously we are testing the whole of DCS and its modules and I am waiting for QA to give me the all clear to announce the date. 

thank you 

[Alexfly65]

2 ore fa, jurinko ha scritto:

If you use openxr toolkit, switch off turbo mode. 

I use turbo mode, but for me is a game changer.  So I prefere to use the downgrade temporal fix and keep turbo mode enable.
Waiting for ED fix.