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

[mimamema]

14 minutes ago, Qcumber said:

I am using v63 in the desktop v62 in the desktop app. I thought my desktop app had updated so I guess I will keep this as is.

The link I am using is "D:\DCS World\bin-mt\DCS.exe" --force_oculus_VR

 

Sorry, but I don´t understand which version are you using in the desktop app, meaning the one that I posted a screenshot above, could you post a screenshot of yours? I think you are confusing the version you have in your headset (mine is v63 as well) with the version of your Oculus Link app on your PC which is most probably v62 ( like in the screenshot I´m posting below). The problem we are discussing at the moment is related to the  PC App that in v63 is not working with DCS, the version of the version of the headset has no incompatibility with DCS. So if you could double-check this it would be great. To double-check this please go to Settings in your Oculus App then open the General tab and scroll down as you can see in the second screenshot. Thank you!

Edited February 29, 2024 by mimamema

[Qcumber]

25 minutes ago, mimamema said:

The problem we are discussing at the moment is related to the  PC App that in v63 is not working with DCS

Yes. I realise that. I had thought my PC app had auto-updated after installing but it had not. This is the version I am using. 

Edit: just reread my earlier post and it did not make sense. Sorry. I'll edit and update it.

null

Edited February 29, 2024 by Qcumber

[mimamema]

24 minutes ago, Qcumber said:

Yes. I realise that. I had thought my PC app had auto-updated after installing but it had not. This is the version I am using. 

Edit: just reread my earlier post and it did not make sense. Sorry. I'll edit and update it.

null

 

Thank you for confirming this. It´s fine, don´t worry I could guess more or less what was happening. I would suggest not to update the app to v63 till we manage to clarify if the "force_oculus_VR" workaround works, but as far as I saw in other of your posts you use VD, so you should be fine with it.

 

2 hours ago, BIGNEWY said:

correct and thanks for confirming, 

you have to be in MT DCS and not in openXR mode for native oculus to work. 

@BIGNEWY I´m sorry, this means that it´s not confirmed that works and the only experience we have for the moment is that is not working. I know you are not an Oculus user so I will try to make a small post later explaining what is exactly the issue here and what the people need to try and look for to see if the proposed solution works. 

[VirusAM]

I am still in V62 myself (can't find a way to stop the auto-update but I am safe for now), but you can use the --force_oculus_VR switch with the v62 as well.

There are a couple of ways to check the runtime in use (OculusVR or OpenXR), for example if you use openxr toolkit just check if the menu opens, or tools like XRnecksafer should not work with OculusVR runtime.

[diamond26]

6 minutes ago, VirusAM said:

(can't find a way to stop the auto-update but I am safe for now)

what about this suggestion :

 

[Qcumber]

34 minutes ago, mimamema said:

Thank you for confirming this. It´s fine, don´t worry I could guess more or less what was happening. I would suggest not to update the app to v63 till we manage to clarify if the "force_oculus_VR" workaround works, but as far as I saw in other of your posts you use VD, so you should be fine with it

I had a rollercoaster yesterday of various issues which resulted in reinstallation of oculus and a headset factory reset. After a lot of setting up I can now get oculus-link to work with DCS MT open xr with V63 headset, v62 PC app, but I think others have already reported this. I have no plans to update the PC app to v62. 

[DayGlow]

I was running into the same issue. I have v63 on my Quest Pro and couldn't get link to start. I switched over to IL2 and found OpenComposite was crashing. To fix that I took the Oculus App on the desktop out of PTC in the Beta tab of settings. That fixed the link issue for DCS as well. 

[Qcumber]

On 2/27/2024 at 8:29 AM, Qcumber said:

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

I've got oculus link working again. V63 on the headset. V62 on the PC app and this is working ok. 

[slughead]

@BIGNEWY as predicted. Meta has pushed back on this despite it clearly being a change that they have made and have redirected me to Eagle Dynamics and Khronos.org! Has the team made any progress on this as I expect Meta will push this out for general release in a couple of weeks.

[BIGNEWY]

18 minutes ago, slughead said:

as predicted. Meta has pushed back on this despite it clearly being a change that they have made and have redirected me to Eagle Dynamics and Khronos.org! Has the team made any progress on this as I expect Meta will push this out for general release in a couple of weeks.

I am not surprised, as mentioned the team know what has been changed and a fix for using v63 will be in our next patch. We did not change anything and v62 works well with DCS and OpenXR. 

Ive asked the team to check the native oculus command again 

thanks

[slughead]

Super. Thanks for the update. I’m sure that’s going to put a lot of minds at rest.

[jurinko]

If I force oculus and still can open the openxr toolkit menu in game, am I running in openxr or in native oculus api?

[mimamema]

39 minutes ago, jurinko said:

If I force oculus and still can open the openxr toolkit menu in game, am I running in openxr or in native oculus api?

That means you are not running Oculus VR, you are still using OpenXR

[BIGNEWY]

We have asked the team to confirm the process. 

thank you 

[Hoirtel]

--force_oculus_VR did work for me when I tried it.

Confirmed by openxr menu not displaying. I also have a foveated rendering and super sample applied in this tool which also did not load. I haven't kept using it as still on v62 but thought I would check it to make sure I could do it.

[BIGNEWY]

11 minutes ago, Hoirtel said:

--force_oculus_VR did work for me when I tried it.

Confirmed by openxr menu not displaying. I also have a foveated rendering and super sample applied in this tool which also did not load. I haven't kept using it as still on v62 but thought I would check it to make sure I could do it.

thank you for letting us know. 

[YoYo]

On 3/1/2024 at 9:19 AM, BIGNEWY said:

I am not surprised, as mentioned the team know what has been changed and a fix for using v63 will be in our next patch. We did not change anything and v62 works well with DCS and OpenXR. 

Ive asked the team to check the native oculus command again 

If Meta pushed this Update v.63 as official it could ba a problem for many very soon, maybe this week even. Pls release the hotfix sooner than the Global patch. Now Im on v.62 and no issue, but If v.63 becomes the official version, I will receive these updates within a few days perhaps.

Edit. https://www.meta.com/pl-pl/help/quest/articles/whats-new/release-notes/ < looks like false alarm, still v.62 is a current version so maybe we have more time.

Edited March 4, 2024 by YoYo

[Lange_666]

Just block the update as discribed here:

You'll get a notification that there's an update when you launch the Oculus App but it will be queued until you remove the block.
This way i know that there is an update but i'll only give it a green light when i read that there are no big issues.

Edited March 4, 2024 by Lange_666

[mimamema]

5 hours ago, Hoirtel said:

--force_oculus_VR did work for me when I tried it.

Confirmed by openxr menu not displaying. I also have a foveated rendering and super sample applied in this tool which also did not load. I haven't kept using it as still on v62 but thought I would check it to make sure I could do it.

We are trying to workout if forcing oculus VR is working with v63, it was not for me, and nobody else has been able to confirm it working.  In v62 is working already as you have confirmed now. But the issue is with v63 oculus pc app, that is the combination you need to confirm ( oculus VR and v63 oculus pc app), if not is going to be confusing for the developers to understand if it works or not. Thank you.

Edited March 4, 2024 by mimamema

[Hoirtel]

3 hours ago, Lange_666 said:

Just block the update as discribed here:

You'll get a notification that there's an update when you launch the Oculus App but it will be queued until you remove the block.
This way i know that there is an update but i'll only give it a green light when i read that there are no big issues.

 

Just checking, you say create a new file called staging with no extension, but then rename folder? Do you create a folder called staging? same for tmp

[diamond26]

1 hour ago, Hoirtel said:

Do you create a folder called staging? same for tmp

I only created a bak.staging (actually renamed an existing folder) and a bak.tmp folders and it worked as suggested by @Lange_666

[slughead]

1 hour ago, Hoirtel said:

Just checking, you say create a new file called staging with no extension, but then rename folder? Do you create a folder called staging? same for tmp

Rename the folders first. Then create two files called Staging and tmp. This will prevent Oculus from using the Staging and tmp folders thus blocks any updates.

[Lange_666]

6 hours ago, Hoirtel said:

Just checking, you say create a new file called staging with no extension, but then rename folder? Do you create a folder called staging? same for tmp

Made a mistake in the work order. Just corrected the work order in my original post... -)

[Arkku]

FWIW I have the same issue, but I can't downgrade Oculus because the earlier versions have another issue (controllers claim they are overheating when they are not)…

However, as a workaround, DCS works for me when I switch OpenXR to use Steam VR.

[slughead]

@BIGNEWY v63 of Oculus is now going live. It would be sensible to have a hotfix imminently. Are you able to share where the team is with this, please?