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

[Phantom711]

Even though a fix to this problem doesn‘t seem to be too far on the horizon and there are several workarounds available, I am still wondering, why some people (including me) seem not to be affected by the problem at all while the majority is. I don‘t want to brag about it but rather figure out, which of my settings it is, that I can still run QuestLink (cable) on v63 with OpenXR without problems.

First I thought, it might be the fact that I have a Quest Pro as opposed to a Q3 which most people have, but this in itself seems not to be the case.
BUT: Quest Pro users are certainly more prone to have the „Developer mode“ enabled because this is the only way to have eye-tracking in DCS (QVFR).

@Qcumber

@minimi66

So please chime in! Those of you that use developers mode, can you still run QuestLink with OpenXR without any workarounds? And of course also those of you that run a QP and have the problem, can you confirm, that you don‘t use developers mode?

 

I might be wrong of course…it‘s just a guess.

Edited March 29, 2024 by Phantom711

[YoYo]

Ok, so the Windows version probably has nothing to do with it, thanks for the info.

[ssamayoa]

41 minutes ago, Qcumber said:

I've just updated to v64 and am using W11 and everything is working ok.

Meta Quest Link v64?

How you get it?

[Gazzer]

34 minutes ago, ssamayoa said:

Meta Quest Link v64?

How you get it?

You need to enrol in the public test channel (PTC) here: https://www.meta.com/en-gb/help/quest/articles/headsets-and-accessories/oculus-rift-s/public-test-channel/

Sad to report, it didn’t for me with a Quest 2 and Windows 11. Still won’t start up past the “15 years of DCS” splash screen 

[tribbin]

Reposting my solution that has worked for many people, because it has ended up many pages back due to discussions.
 

Happy flying this Easter weekend!

Edited March 29, 2024 by tribbin

[Qcumber]

9 minutes ago, Gazzer said:

You need to enrol in the public test channel (PTC) here: https://www.meta.com/en-gb/help/quest/articles/headsets-and-accessories/oculus-rift-s/public-test-channel/

Sad to report, it didn’t for me with a Quest 2 and Windows 11. Still won’t start up past the “15 years of DCS” splash screen 

Maybe it’s not affecting Quest pro. However I am sure someone has posted previously on this thread that they were affected with QP.

[Qcumber]

1 hour ago, Phantom711 said:

Even though a fix to this problem doesn‘t seem to be too far on the horizon and there are several workarounds available, I am still wondering, why some people (including me) seem not to be affected by the problem at all while the majority is. I don‘t want to brag about it but rather figure out, which of my settings it is, that I can still run QuestLink (cable) on v63 with OpenXR without problems.

First I thought, it might be the fact that I have a Quest Pro as opposed to a Q3 which most people have, but this in itself seems not to be the case.
BUT: Quest Pro users are certainly more prone to have the „Developer mode“ enabled because this is the only way to have eye-tracking in DCS (QVFR).

@Qcumber

@minimi66

So please chime in! Those of you that use developers mode, can you still run QuestLink with OpenXR without any workarounds? And of course also those of you that run a QP and have the problem, can you confirm, that you don‘t use developers mode?

 

I might be wrong of course…it‘s just a guess.

 

I have just updated to v64 and everything still works fine for me with QP. I am using the dev mode. 

[GavH77]

Meta Quest Link App Version 64.0.0.359.367 (64.0.0.359.367)

I'm on W11, all the latest updates and Meta Quest Link App Version 64.0.0.359.367 and as soon as I try to enable VR in the game, the restart fails just after the '15 years of DCS' splash screen loads.

As a side issue, does anyone know what file I need to find and amend to turn that off so I can at least open the game in pancake mode?

 

[tribbin]

5 minutes ago, GavH77 said:

Meta Quest Link App Version 64.0.0.359.367 (64.0.0.359.367)

I'm on W11, all the latest updates and Meta Quest Link App Version 64.0.0.359.367 and as soon as I try to enable VR in the game, the restart fails just after the '15 years of DCS' splash screen loads.

As a side issue, does anyone know what file I need to find and amend to turn that off so I can at least open the game in pancake mode?

 

Two comments above your comment is the solution that has worked for many, including me on W11.

[Picchio]

1 hour ago, Phantom711 said:

Even though a fix to this problem doesn‘t seem to be too far on the horizon and there are several workarounds available, I am still wondering, why some people (including me) seem not to be affected by the problem at all while the majority is. I don‘t want to brag about it but rather figure out, which of my settings it is, that I can still run QuestLink (cable) on v63 with OpenXR without problems.

First I thought, it might be the fact that I have a Quest Pro as opposed to a Q3 which most people have, but this in itself seems not to be the case.
BUT: Quest Pro users are certainly more prone to have the „Developer mode“ enabled because this is the only way to have eye-tracking in DCS (QVFR).

@Qcumber

@minimi66

So please chime in! Those of you that use developers mode, can you still run QuestLink with OpenXR without any workarounds? And of course also those of you that run a QP and have the problem, can you confirm, that you don‘t use developers mode?

 

I might be wrong of course…it‘s just a guess.

 

QPro user here, Dev mode enabled, v62 reported by the headset. DCS crashed upon start.

I haven't investigated much into the issue as there seems to be a lot of confusion, reading the various reports - the workaround I applied was to use the files shared here: 

Logic seems to suggest that the problem isn't with v63 (I have not updated the headset) but with the Oculus app (necessary for Link). I run the headset via USB.

Edited March 29, 2024 by Picchio

[slughead]

27 minutes ago, Qcumber said:

Maybe it’s not affecting Quest pro. However I am sure someone has posted previously on this thread that they were affected with QP.

Yes, me! I had the issue with v63 PTC and reported it in early Feb to ED. The threads have been merged so much now that this seems to have been lost. I am not upgrading from V62 until I am told it is fixed by ED.

[Lange_666]

21 minutes ago, GavH77 said:

As a side issue, does anyone know what file I need to find and amend to turn that off so I can at least open the game in pancake mode?

Saved Games\DCS World (or DCS.openbeta)\ Config\Options.lua
VR section (on top): set enable from true to false

Edited March 29, 2024 by Lange_666

[Phantom711]

@Picchio

Well yes…the common understanding is, that the problems started with v63 of the PC App, regardless of the HMD software. I have both on v63 now.

[theOtherMikeB]

20 minutes ago, GavH77 said:

Meta Quest Link App Version 64.0.0.359.367 (64.0.0.359.367)

I'm on W11, all the latest updates and Meta Quest Link App Version 64.0.0.359.367 and as soon as I try to enable VR in the game, the restart fails just after the '15 years of DCS' splash screen loads.

As a side issue, does anyone know what file I need to find and amend to turn that off so I can at least open the game in pancake mode?

 

I was able to get DCS to open in 2D by adding --force_disable_VR to the end of my shortcut for the bin-mt.exe on my desktop.  There may be other ways in the 20+ pages this thread has become.

 

[Gazzer]

@tribbin - you Sir are a genius. That worked a treat and all is working again. It took me a while to find the files on Reddit, but now I’ve stopped the Oculus updates too, then winding back to those old files has worked a great.

Thanks and Happy Easter

[Picchio]

19 minutes ago, Phantom711 said:

@Picchio

Well yes…the common understanding is, that the problems started with v63 of the PC App, regardless of the HMD software. I have both on v63 now.

I see. So, is the v64 mentioned above for the hmd software or the PC app, or both? Is it confirmed to be working?

Sorry, just read the Bug reports thread: Oculus PC app v64 only seems to be available through Public Test Channel. Although it doesn't work for some, it seems. I'll try updating both the headset and the app to v63 and report back.

 

 

Edited March 29, 2024 by Picchio

[BIGNEWY]

22 minutes ago, slughead said:

Yes, me! I had the issue with v63 PTC and reported it in early Feb to ED. The threads have been merged so much now that this seems to have been lost. I am not upgrading from V62 until I am told it is fixed by ED.

It will be fixed in the next patch, I will share the date soon hopefully. 

[raybanwomble]

Two weeks, be sure.  If it was reported in February, why wasn't it fixed sooner? 

Edited March 29, 2024 by raybanwomble

[-Sledgehammer-]

soon

[raybanwomble]

9 minutes ago, -Sledgehammer- said:

soon

Maybe they'll release occulus support as  a module - with the ability to purchase one eye at a time in case you are a pirate. 

Edited March 29, 2024 by raybanwomble

[slughead]

34 minutes ago, theOtherMikeB said:

I was able to get DCS to open in 2D by adding --force_disable_VR to the end of my shortcut for the bin-mt.exe on my desktop.  There may be other ways in the 20+ pages this thread has become.

 

I think that --force_dsiable_VR isn't an option that DCS recognises. So as you had removed --force_enable_VR, DCS defaulted to the in-game settings. So if you didn't have VR enabled in the in-game settings it just launched into 2D as though you didn't have any command line options.

22 minutes ago, BIGNEWY said:

It will be fixed in the next patch, I will share the date soon hopefully. 

Yes, I know. I meant I won't update the Oculus software until the DCS patch is released.

[Mike_CK]

Well, I was hoping for a patch today but that doesn’t seem likely since Bignewy said he hopes to let us know the patch release date soon. So that means at least another 4 days.

I know it’s pointless to ask….but it makes me feel a little bit better: can we PLEASE get a hotfix for this outside of the gameplay patch if that is at all possible???

[les]

I may very sadly be done with dcs.i live it but over the last couple of weeks I have spent around 30 hrs fixing problems and no hours flying, I'm a flightsim fan not a fixing problems fan, it's just too unreliable.....

Fixed the vr problem with VD, now I have another new issue of controls locking /freezing while the game continues to run..... sometimes for a few seconds sometimes longer , unplayable again

[ssamayoa]

On 3/25/2024 at 6:17 PM, tribbin said:

OK guys... I got it working.

1. Download the folders on this guys Google Drive: https://www.reddit.com/r/dcsworld/comments/1blxiry/comment/kwkcbib/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
(and give this Redditor an upvote)

2. Stop the Oculus service in Windows.

3. Overwrite the -client and -runtime folders in C:\Program Files\Oculus\Support with his files.

4. Start Oculus app and then start DCS.

If Oculus updates, repeat steps 2, 3 and 4.
 

 

Note that the google drive files are here:
https://www.reddit.com/r/dcsworld/comments/1bnspf6/recent_oculus_vr_bug_fix/?utm_source=share&utm_medium=web2x&context=3
 

[NIGHTHAWK1]

It is more important to ED to sell new stuff then it is to fix current problems.  My suggestion is to have everyone buy the new map and then maybe they can afford to hire someone to fix this issue. LOL.  Obviously  they have spent all their time and effort and money and energy lately to make some slick hype videos.  I counted all my DLC (downloads from Steam), got 34 of them, I would think we all have spent enough on this game to get some results, instead of "it is coming".  Sad thing is we cannot do anything.  Yes we all talk big, but once they got our money we lost all control.  We can't go on strike, or boycott the game, or anything like that.  This is the single largest issue I have seen with this game since I purchased it 2 years ago.  I do hope that DCS/ED is not on the verge of total collapse but so many signs indicate such possible outcome.  Can only wait and see.