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

[AlpineGTA]

I posted this in the VR section. I'm not saying this is the problem but it might be worth checking. It might help some people.

[Bri01]

Yep, just got hit with v63 couple hours ago. I'm not installing steam or buying new router just to play a game that could be hotfixed (but they wont) 

[dugite57]

yeah, not happy, ED should have put the customer first and put out a hot fix.

[Bluto74]

Can confirm this as well.Does not matter if you still have ver 62 on the headset.  The link software forced an update today.  And of a pool of 10 people on a discord channel at leat three of us are unable to use DCS by this.  And that is from a small sample pool.  This needs a hotfix sooner rather than later guys.  Please.

 

[lahsoldier]

Dont think this is v63 related.  Meta dropped a Oculus link update about 6 hrs ago and I think that is what messed everything up.  Im still version 62 and mine wont work but did prior to that link update.  

[Cooper21]

They've had a fix ready since February but haven't put it out yet. No statement or apology wither

[Graves0922]

Just got hit with the update - DCS crashes on startup. 

[lahsoldier]

Don't think this is a V63 issue.  I was still on 62 and it doesn't work but I noticed Meta dropped a Meta Quest link update 7 hrs. (EST) for me and after that is stopped working.  It worked fine literally 2 hrs. before that update. 

 

Edited March 26 by lahsoldier

[Mike_CK]

Yep. It was whatever updated today. I thought it was 63 going stable from beta. My oculus app on the PC updated, then my headset. Then…nuthin

seems BigNewy has a good handle on the issue though. He says it’s something to do with the new Oculus download. Meta’s answer is “if the game you’re playing won’t work with the new Oculus software, that is the game developers fault”: which is a bit off putting but whatever.

I have ALOT more faith in ED fixing it than I do Meta

[Vmac77]

Flew in VR fine yesterday with my Quest 2. Had opted out of PTC and had automatic updates blocked. While I was at work today the update was pushed through and now DCS is unplayable for me as well. PLEASE push a hotfix.............

[JSOMaverick]

2 hours ago, AlpineGTA said:

I'm running the latest version 63.0.0.216.361 and my Quest 2 works fine.

One thing I have noticed though, if I try to run with the hand tracking option set in the DCS VR tab then it won't load at all, it just crashes to desktop. Only if I have the "TRACKERS" option selected. It's ok if I have the Controllers option ticked. Maybe check that setting if you're finding yours won't load. (If you can't get it to load to check the setting, launch it in 2D using the --force_disable_VR option in your desktop shortcut properties:

 

No ball - have toggled it both on and off, but zero dice still crashes. This is a Meta issue and apparently @BIGNEWYstated in another forum somewhere that they have a fix but it isn't likely to be getting pushed in till the next DCS update from what I read in discord.

Edited March 26 by JSOMaverick
Edited how it sounded

[SantasGolfClub]

So just to confirm, as my darn headset went to v63 (And there was a 'recommended update' for the Oculus app), so I'm broken as well - there's currently no work around, as the PTC is no longer a thing - v63 is official and forced?

There's mention of running someone elses uploaded executable... but ... I'd rather not.

So for now, we just need to wait? And .... MSFS2020 it is?

Edited March 26 by SantasGolfClub

[Mike_CK]

That’s really disappointing. I’d hope that if there was a large segment of the customer base that couldn’t use their  product, ED would release a hotfix and not make people wait until whenever a patch comes out. Maybe it’s more complicated than that. Dunno
 

Maybe the patch will come out tomorrow? I don’t know a damned thing about software and I’m sure ED will do their best….but It sucks not being able to use something I have put $1,000s or dollars into for sure.

[TheIziWarrior]

i have the standalone openbeta, oculus rift s and cant play vr, st/mt doesnt matter. i have the --force etc but nothing helps. iget to the 15year loading screen then it just stops and goes back to desktop

dcs.log

[Bluto74]

I just tried the step by step instructions listed above.  Yes, I was able to get it to run.  But, The debug tool then would not start.  Would just get an error.  And I need the debug tool to make it look good so there is no point in using it if you use the debug tool

 

[Bossco82]

4 hours ago, 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.
 

 

This worked Tribbin, thanks for sharing.

[Tchalla]

Was able to use steam VR and set openXr as active runtime. Bummer both apps have to run at the same time. 

[nephilimborn]

7 hours ago, ddc196 said:

I'm on V63 and am not having issues. Just FYI.

same here

[Qcumber]

34 minutes ago, nephilimborn said:

same here

Me too. Works fine with QP and v63. Not sure why it's not affecting everyone. 

[Qcumber]

6 hours ago, mediocre said:

v63 on head and link, I will check later and drop app bulid. I aslo opted for beta so maybe that is the diffrence.

 

edit: Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361)

 

 

 

I am using this version on my headset and it runs DCS fine (v63 on my PC app too).

Headset version: 63.0.0.327.363.576466842

This is the second v63 update I have had so wondering if this version fixes the issues others are having. 

1 hour ago, Mike_CK said:

That’s really disappointing. I’d hope that if there was a large segment of the customer base that couldn’t use their  product, ED would release a hotfix and not make people wait until whenever a patch comes out. Maybe it’s more complicated than that. Dunno
 

Maybe the patch will come out tomorrow? I don’t know a damned thing about software and I’m sure ED will do their best….but It sucks not being able to use something I have put $1,000s or dollars into for sure.

Can you please check your headset release version and see if it is the same as mine shown above? 

[coolts]

It's on ED to fix their openxr implementation. 

With the move away from open beta to predictable, slower releases, there probably won't be a hotfix.  

What we lose in agility, we hopefully gain in stable patches going forward. 

In the meantime, ditch the cable or use the janky steam runtime. 

 

[BIGNEWY]

As mentioned in previous post it is certainly unfortunate that the timing of this Meta update created this problem, we are currently locked into a testing cycle for the next patch, we have to test the whole of DCS including its modules, all our fixes features and planned updates. 

The work arounds in the first post are the only option at this time, the steam API seems to be the most successful at the moment. 

I hope (all going well) I can let you know the intended patch date soon, please keep an eye on the patch status post linked in my signature below. 

thank you and sorry for the inconvenience 

[YoYo]

I'm optimistic. Usually ED patches are on Wednesday or Thursday, so taking into account the 6-week cycle and the month, the patch must be this week I suppose, tomorrow or the day after tomorrow. Try MSFS or IL-2 during this time  if DCS doesnt work ;).

[tribbin]

Meta is informed:

https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-DCS-crashes-on-Link/m-p/1160636

[draconus]

19 minutes ago, YoYo said:

Usually ED patches are on Wednesday or Thursday, so taking into account the 6-week cycle and the month, the patch must be this week I suppose, tomorrow or the day after tomorrow.

In my part of the world math says 6 weeks from last update will be April 4th.