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

[Quanun]

Am 11.3.2024 um 17:38 schrieb Mausar:

What I hate the most is when I put Q3 off head for some reason the game crash. I mean it freeze in VR. Have never that issue before.

 

Hi! I`ve put a small bandaid over the proximity-sensor between the lenses so the Q3 doesn`t know that i`ve put it off and DCS doesn`t crash...

 

[Lange_666]

3 hours ago, majorandme said:

Did not work.  I did everything up to step 5.  Then went to flash up Oculus and it said I am running V63,  Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361)

Means that the installer is now also on the latest version...

[13sq*Axe]

6 hours ago, unlikely_spider said:

Hmm... I am currently on Meta Quest Link app version 63.0.0.216.361 and played last night for like 2 hours with no issues.

This IS very interesting. My Windows System Restore fix I described got me working even thou my PC app shows to be Version 63.0.0.216.361 also. I checked my DeBug tool and it shows to be V62 as does my Q3 headset. 

Edited March 12, 2024 by 13sq*Axe

[slughead]

9 minutes ago, 13sq*Axe said:

This IS very interesting. My Windows System Restore fix I described go me working even thou my PC app shows to be Version 63.0.0.216.361 also. I checked my DeBug tool and it shows to be V62 as does my Q3 headset. 

I suspect the restore missed one or more files.

[Phantom711]

@Mausar @Quanun

No offense guys, but maybe we should keep this thread a bit mor on-topic of the current problems with the Meta/Oculus Link.

[Maksim Savelev]

В 11.03.2024 в 18:13, biotech сказал:

https://forum.dcs.world/topic/186233-virtualnaja-realnost-v-dcs/?do=findComment&comment=5395919

https://forum.dcs.world/topic/186233-virtualnaja-realnost-v-dcs/?do=findComment&comment=5396145

 

Thank you very much,  that helped and I'm back on track for flying)

[jurinko]

Now I can run DCS with v63/Quest 3, starting it from the desktop icon or from Steam shortcut. I set SteamVR as OpenXR runtime and in game OpenXR toolkit still works. Strange is, now Turbo mode causes terrible stutter and DCS runs smoothly without it, before Turbo mode smoothed things out. 

 

 

[hockey3761]

Bummer, I literally just got a Quest 3, and been trouble shooting and see these problems....oye

Edited March 13, 2024 by hockey3761

[scottpussehl]

Does anybody still have the v62 version installed on their computer. Could they upload the files from their program directory and allow us to replace the files we have for v63 with their v62 files? Would this work?

Or would it be helpful to compare the differenced between the files for the different version and we could maybe find what file has changed that is causing the issue?

[CaptSteviej]

Tall order. My directory is 138GB Meta Link App Version 62.0.0.235.346 (62.0.0.235.346)

 

1 hour ago, scottpussehl said:

Does anybody still have the v62 version installed on their computer. Could they upload the files from their program directory and allow us to replace the files we have for v63 with their v62 files? Would this work?

Or would it be helpful to compare the differenced between the files for the different version and we could maybe find what file has changed that is causing the issue?

 

[jurinko]

3 hours ago, scottpussehl said:

Does anybody still have the v62 version installed on their computer. Could they upload the files from their program directory and allow us to replace the files we have for v63 with their v62 files? Would this work?

There is a procedure how to do it in Bignewy's thread about using oculus runtime. You uninstall oculus software, reinstall, snooze update, click off auto update, make a copy of the folder, delete some folders, get it updated, replace the oculus folder with the old one, run installer for repair and you have v62 not updating itself.

It worked for me but the performance is better with v63 using steamvr as openxr runtime so i reverted everything back and at 3am i went to bed satisfied i have the best option on.

[YoYo]

1 hour ago, jurinko said:

Steamvr as openxr runtime

Personally I dont like SteamVR, only native, clean OpenXR. Notice also that this change will affect the settings for other simulators (like MSFS or IL-2) and games. Im still waiting for a patch from ED side.

[BIGNEWY]

Thank you to all for posting your experiences and work arounds for the issue with v63. 

I do not have a date for the patch yet, as soon as I can update you all I will. 

 

[adam34aus]

Any news on a fix yet. I miss playing DCS

[4romeodelta]

On 3/11/2024 at 1:15 PM, yoadknux said:

For now, I was able to survive the dreaded 4 hour snooze.

Here are the steps I took.

1) Uninstall Oculus with the regular Windows uninstaller.

2) Go to C:\Users\(your username)\AppData and remove all Oculus folders inside Local, LocalLow, Roaming

3) Install Oculus from the following link: https://www.mediafire.com/file/rn5uurwqvv9qp8q/OculusSetup.exe/file - This will install v62 (at least at the moment this post was written).

4) Turn off Automatic updates on the Oculus app settings. You will still get notified that there is an update ready to install. Snooze it.

5) Go to Oculus folder, delete all the contents of Staging and tmp. Make a copy of the entire Oculus folder, name it Oculusv62. 

6) 4 hours after the snooze, the app will update to v63. Once it's updated, go into safe mode, and replace the contents of the Oculus folder with the contents of Oculusv62. You can do this by deleting the Oculus folder and renaming Oculusv62 into Oculus (I recommend keeping a copy of Oculusv62 regardless)

Optional: Also make a copy of the Oculus folders inside Local, LocalLow, Roaming (from step 2).

7) Exit safe mode. Run OculusSetup, and use it to repair. 

The outcome is that you will have a "fresh" v62 with empty Staging & tmp folders, with auto-updates disabled at the oculus settings. 

I'm still not 100% sure it works long term - it only worked for a few hours for me. It may still update to v63 somehow. However, if it updates, I think restoring the Oculusv62 + AppData folders should send it back to v62 for another few hours. Good luck guys. And I hope ED fixes this issue as soon as possible. 

This worked for me (so far!) Thanks to yaodknux for coming up with this workaround.  

[fjacobsen]

It´s weird...

I have both V63 on my Quest 3 and in the Oculus PC App and everything works as it always did.

I´m not sure if I still use then openvr.api.dll from the Open Composite Github site and if it makes any difference to the issue.

Here is the link: https://gitlab.com/znixian/OpenOVR (look under pre-game install and download the 64bit version) 

[majorandme]

Do you think DCS should put an information news item on their home page.  akin to "We at DCS realize many DCS members may be experiencing difficulty playing DCS in VR following an Oculus version update in February.  Though we are not responsible for this incompatibility issue, Oculus users can rest assured we at DCS understand their frustrations with Oculus and will be attempting to provide a solution in a future version release"?  Or something along those lines?  Oculus screwed up, but don't worry, we'll fix it for them!  Many folks don't go on the Forums (I am here rarely) but do check out the home page from time to time.

Just spit balling ...

[majorandme]

Do you think DCS should put an information news item on their home page.  akin to "We at DCS realize many DCS members may be experiencing difficulty playing DCS in VR following an Oculus version update in February.  Though we are not responsible for this incompatibility issue, Oculus users can rest assured we at DCS understand their frustrations with Oculus and will be attempting to provide a solution in a future version release"?  Or something along those lines?  Oculus screwed up, but don't worry, we'll fix it for them!  Many folks don't go on the Forums (I am here rarely) but do check out the home page from time to time.

Just spit balling ...

[BIGNEWY]

6 minutes ago, majorandme said:

Do you think DCS should put an information news item on their home page.  akin to "We at DCS realize many DCS members may be experiencing difficulty playing DCS in VR following an Oculus version update in February.  Though we are not responsible for this incompatibility issue, Oculus users can rest assured we at DCS understand their frustrations with Oculus and will be attempting to provide a solution in a future version release"?  Or something along those lines?  Oculus screwed up, but don't worry, we'll fix it for them!  Many folks don't go on the Forums (I am here rarely) but do check out the home page from time to time.

Just spit balling ...

I will certainly mention it to the team.

thanks

[yoadknux]

5 hours ago, 4romeodelta said:

This worked for me (so far!) Thanks to yaodknux for coming up with this workaround.  

I'm glad I was able to help. I'm happy to say that since I've written this post, my Meta Link App Version remains at 62, and everything works as it did before.  

I think outsiders don't understand how crippling this issue is. I felt completely helpless. 

[Scendore]

I take it this problem has not been resolved.  I'm keeping my Q3 on .62 for now until I hear otherwise.

 

[DCoffey]

I wonder what is different about my system as the new update is working with no issue using link cable.

 

I7-10700

RTX4070ti (latest driver)

64gb

4tb m.2

Quest 2 and Quest 3

 

[slughead]

2 minutes ago, DCoffey said:

I wonder what is different about my system as the new update is working with no issue using link cable.

 

I7-10700

RTX4070ti (latest driver)

64gb

4tb m.2

Quest 2 and Quest 3

 

And you are not going through Steam?

[NathB]

On 3/10/2024 at 9:28 PM, hockey3761 said:

I recently got a Quest 3. I started up DCS, went to settings so I could enable VR. After I applied the settings, it booted me out of DCS. I am trying to get my Quest 3 to work by having it plugged into the USB C port. (I previously had OpenXR set up for my former G2 Headset, but with a recent Windows update, I dont see any microsoft mixed reality settings, fyi).

 

I try to open DCS, I put my password in, I see a loading screen, the DCS "15 years" etc. screen, and then DCS closes itself. I try starting up DCS without the headset on, same thing happens.

 

So now I cannot open DCS. DCS is up to date. Not sure what to do now.

I too have exactly the same issue.. not on the Oculus PTC but version63 has stopped DCS launching, and you can't revert back to an older version as far as i'm aware.

Very Frustrating as I soley play DCS and only in VR these days. However if you are willing to go back to 2D I found a get around to get DCS loaded in non-VR mode. You have to rename your saved games DCS folder to something else like 'Temp' and then it'll launch DCS.. it does mean you'll have to set up all your graphics settings etc again unfortunately (unless there's another way to load DCS in non-VR mode).

 

I hope a fix comes out soon!

[13sq*Axe]

On 3/11/2024 at 1:15 PM, yoadknux said:

For now, I was able to survive the dreaded 4 hour snooze.

Here are the steps I took.

1) Uninstall Oculus with the regular Windows uninstaller.

2) Go to C:\Users\(your username)\AppData and remove all Oculus folders inside Local, LocalLow, Roaming

3) Install Oculus from the following link: https://www.mediafire.com/file/rn5uurwqvv9qp8q/OculusSetup.exe/file - This will install v62 (at least at the moment this post was written).

4) Turn off Automatic updates on the Oculus app settings. You will still get notified that there is an update ready to install. Snooze it.

5) Go to Oculus folder, delete all the contents of Staging and tmp. Make a copy of the entire Oculus folder, name it Oculusv62. 

6) 4 hours after the snooze, the app will update to v63. Once it's updated, go into safe mode, and replace the contents of the Oculus folder with the contents of Oculusv62. You can do this by deleting the Oculus folder and renaming Oculusv62 into Oculus (I recommend keeping a copy of Oculusv62 regardless)

Optional: Also make a copy of the Oculus folders inside Local, LocalLow, Roaming (from step 2).

7) Exit safe mode. Run OculusSetup, and use it to repair. 

The outcome is that you will have a "fresh" v62 with empty Staging & tmp folders, with auto-updates disabled at the oculus settings. 

I'm still not 100% sure it works long term - it only worked for a few hours for me. It may still update to v63 somehow. However, if it updates, I think restoring the Oculusv62 + AppData folders should send it back to v62 for another few hours. Good luck guys. And I hope ED fixes this issue as soon as possible. 

Are you also renaming the "Staging" and "tmp" folders and adding the non extension "Staging and "tmp" files as described in Lange_666 post?