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

[Om]

So there is no way to play DCS on Oculus, that's sad

Other games work well 

[Flappie]

51 minutes ago, Om said:

So there is no way to play DCS on Oculus, that's sad

5 threads below yours...

 

[slughead]

It's not the device you need to roll back but the Oculus PC app.

You can also run DCS with SteamVR using the latest SteamVR beta or you can use Virtual Desktop.

[Om]

On 2/21/2024 at 1:09 AM, slughead said:

It's not the device you need to roll back but the Oculus PC app.

You can also run DCS with SteamVR using the latest SteamVR beta or you can use Virtual Desktop.

thanks, will try

[Qcumber]

OK. I accidentally updated to v63 and it has worked until yesterday when it has started crashing. Can anyone tell me how to roll back to v62?

[Bazz_Mulder]

Disable PTC in Beta tab of PC app. Do the same in the mobile Oculus app when synced with headset. Do factory reset in headset after that.

[slughead]

You need to opt out of the PTC in the Oculus PC app. Just that, shouldn't need to roll back the headset. I say this as I never received a v63 headset update anyway.

[Qcumber]

27 minutes ago, slughead said:

You need to opt out of the PTC in the Oculus PC app. Just that, shouldn't need to roll back the headset. I say this as I never received a v63 headset update anyway.

I just reinstalled oculus app and then turned of auto updates. That seemed to do the trick. No changes needed to my headset. 

[Qcumber]

I am still having a lot of issues with oculus cable link. Sometimes it connects and runs ok. Sometimes it does recognize the headset is connected. Sometimes it crashes after it has run for a while. I'm using v62. No issues with VD.

[slughead]

2 minutes ago, Qcumber said:

I am still having a lot of issues with oculus cable link. Sometimes it connects and runs ok. Sometimes it does recognize the headset is connected. Sometimes it crashes after it has run for a while. I'm using v62. No issues with VD.

That’s some other problem. This one is specific to v63 PTC and DCS crashing on entry to VR space.

Probably better if you create a new thread or raise it on the meta support forum.

[Qcumber]

2 minutes ago, slughead said:

That’s some other problem. This one is specific to v63 PTC and DCS crashing on entry to VR space.

Probably better if you create a new thread or raise it on the meta support forum.

It's after i did the rollback from v63 to v62. I might try a factory reset on the headset and then another reinstall of oculus to make sure desktop app and headset are both running the same versions. 

[slughead]

Just now, Qcumber said:

It's after i did the rollback from v63 to v62. I might try a factory reset on the headset and then another reinstall of oculus to make sure desktop app and headset are both running the same versions. 

Sure but it isn't related to DCS crashing with v^3 PTC. This is an issue with the Oculus app and your headset. So to avoid this thread going off-track, please raise a new thread. Ta.

[Qcumber]

Just now, slughead said:

Sure but it isn't related to DCS crashing with v^3 PTC. This is an issue with the Oculus app and your headset. So to avoid this thread going off-track, please raise a new thread. Ta.

Sorry. Will do. 

[Hoirtel]

Will turning off automatic updates be enough to prevent these crashes from happening if/when the v63 goes mainstream? I don't think there is a way to block the app from updating. 

Edited February 27 by Hoirtel

[Lange_666]

On 2/27/2024 at 7:54 AM, Hoirtel said:

I don't think there is a way to block the app from updating.

There is:

Simply browse to C:\Program Files\Oculus (or where you installed your application)

Rename folder \Staging to bak.Staging

Rename folder \tmp to bak.tmp

Create a new file called Staging (with no extension)

Create a new file called tmp (also, no extension)

 

This blocks the update. When there is an update, you still get a notification that there is an update and that it is in progress but if you check it's queued and the update will be blocked.
Just reverse the steps and restart the app to let the update go through.

Edited March 4 by Lange_666
changed the work order

[YoYo]

I dont use any kidn of beta or public test channel for Oculus software. Its not the first time, where they broke something. Im still on the 62v and no any issue, I hope they will not release this problematic v63 as a public version (after fix ok).

[Qcumber]

I've given up on oculus app for now. I'm using VD instead. It works fine.

[Hoirtel]

1 hour ago, Lange_666 said:

There is:

Simply browse to C:\Program Files\Oculus (or where you installed your application)

Create a new file called Staging (with no extension)

Create a new file called tmp (also, no extension)

rename folder \Staging to bak.Staging

rename folder \tmp to bak.tmp

 

This blocks the update. When there is an update, you still get a notification that there is an update and that it is in progress but if you check it's queued and the update will be blocked.
Just reverse the steps and restart the app to let the update go through.

Thanks, didnt know this!

1 hour ago, YoYo said:

I dont use any kidn of beta or public test channel for Oculus software. Its not the first time, where they broke something. Im still on the 62v and no any issue, I hope they will not release this problematic v63 as a public version (after fix ok).

Neither do I, but I am glad that someone has so this may be fixed. But I will prepare to block it. 

[BIGNEWY]

Dear all, 

By default DCS uses OpenXR which is supported by Oculus.

For Multithreading DCS we also have a native Oculus API available which can be enabled by adding --force_oculus_VR

(Please ensure OpenXR is disabled, and you are using MT DCS.)

 

Due to the priority order OpenXR driver is selected first (prior to v62 oculus update) this was working well,

with Oculus v63 they broke OpenXR for DCS.

As a work around users can use native oculus with --force_oculus_VR

Target line example in properties 

"D:\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_oculus_VR

We do have a fix for the v63 driver coming in a future patch that will allow openXR to work correctly again for Oculus using the newer driver. 

 

----------------------------------------

Please also note there is a steamVR oculus plugin work around found by @jaghammer here

https://forum.dcs.world/topic/344539-native-oculus-api-and-dcs/page/2/#comment-5395501

------------------------------------------
Virtual Desktop XR is also another work around being used by some users. 

Thank you 

 

[Flyingfish]

Where do I need to add force_oculus_VR? I'm using DCS with steam

[Raven (Elysian Angel)]

19 minutes ago, Flyingfish said:

Where do I need to add force_oculus_VR? I'm using DCS with steam

I don't use Steam myself for DCS, but as an example: if you right-click you can add launch options:
null

[SkateZilla]

16 hours ago, Raven (Elysian Angel) said:

I don't use Steam myself for DCS, but as an example: if you right-click you can add launch options:
null

You should still be able to use a launch app, or make your own shortcuts for even the Steam Version.

Navigate to your Steam Library folder <drive><root>\SteamApps\Common\DCS World\bin-mt\
Make a shortcut for DCS.exe
Add the arguments.
 "x:<root>\steamapps\common\DCS World\bin-mt\DCS.exe" --force_enable_VR ----force_oculus_VR

 

or simply add "--force_enable_VR --force_oculus_VR" to the launch arguments in steam.

Edited February 28 by SkateZilla

[Dickie]

Do i add this to the MT shortcut?

[BIGNEWY]

2 hours ago, Dickie said:

Do i add this to the MT shortcut?

this will only work with MT so yes. 

thanks 

[Dickie]

Thanks for the reply. I get an error when adding this saying the destination file does not exist