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

[les]

More problems!!

So vdxr works good for me ( WiFi permitting)  but I now can't run DCS unless I'm using the vr headset! I do like to run it on the monitor for mission editing etc .. I have the same issue of not loading!! 

I have uninstalled oculus, any ideas? 

Thanks again...

Les

[jurinko]

Install the Skatezillas DCS updater and run it in VR OFF mode.

[VR Flight Guy in PJ Pants]

6 hours ago, Lange_666 said:

You can check that in the app:

 

Thanks, but I have already done that but it still downloads the update...

[Qcumber]

1 hour ago, les said:

More problems!!

So vdxr works good for me ( WiFi permitting)  but I now can't run DCS unless I'm using the vr headset! I do like to run it on the monitor for mission editing etc .. I have the same issue of not loading!! 

I have uninstalled oculus, any ideas? 

Thanks again...

Les

Skatezilla or leave the VR box un-ticked and create a launch shortcut with .. 

"C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR

Make sure you use your folder path. 

[Lange_666]

1 hour ago, VR Flight Guy in PJ Pants said:

Thanks, but I have already done that but it still downloads the update...

That's because the PTC V63 went into release. Turning off PTC will now get you V63 instead of reverting to the V62 since that is not an option anymore.  Blocking the update won't work since it can only revert now to V63. You're too late!

Edited March 15, 2024 by Lange_666

[flybull]

When is next DCS update?  We're grounded !

 

[VR Flight Guy in PJ Pants]

Well, the current update tab looks like this:

I think I can still play DCS in VR, for now.

Edited March 15, 2024 by VR Flight Guy in PJ Pants

[slughead]

1 hour ago, flybull said:

When is next DCS update?  We're grounded !

 

2 weeks.

[jurinko]

9 hours ago, flybull said:

When is next DCS update?  We're grounded !

 

You csn set steamvr as your openxr runtime and start dcs from desktop icon. For me, steamvr runs even better than with oculus/openxr. 

[adam34aus]

when will this be fixed. Its been weeks now not been able to play on VR. Spent a small fortune on this game and its very fustrating not been able to play.

 

Edited March 16, 2024 by adam34aus
pissed off

[parasxos]

This should have been a priority hotfix....

[Tomcat388th]

13 hours ago, slughead said:

2 weeks.

If its the team in charge of updating/fixing Super Carrier it might be 2 years.  

[g5flyer]

This sucks lol, carry on.

[seavoyage]

I was only able to launch DCS if on SteamVR. Unfortunately can not migrate any of the purchased mods from ED E-shop (Only possible from Steam to ED standalone). Meta confirmed can not roll back from autoinstalled v63 to v62. On SteamVR both DCS Standard and MT work fine. OpenXR is enabled.

[yoadknux]

honestly I'm surprised this wasn't patched yet, let alone acknowledged in a weekly newsletter or some way the casual player can see it. 

It left a really bad impression on me and on my will to continue investing in new DCS modules as well as continuing the upgrade path for VR. I'm not angry at Meta or ED, but rather about how inflexible they are towards each other: Meta for not allowing official rollbacks and ED for not releasing a hotfix. 

The Rift, Q2, Q3, and QPro are some of the most popular VR headsets in the world. They're essentially the Thrustmaster of VR. Imagine if one morning all the Thrustmaster devices stopped working natively with DCS, and you would need an emulator or new software to make them work with degraded performance. that would be completely unacceptable, and that's exactly what happens with the Meta headsets at the moment. 

I'm one of the players who was affected by this. In the end I managed to come up with a v62 rollback method that still works in my system, but many players are not as fortunate. Still, I can't help but think: I bought the most high-end PC available, invested in HOTAS and pedals, invested in a VR headset, bought modules in hundreds of dollars and I woke up to a non-working setup with no official date on when it will be fixed. That's really frustrating. 

[YoYo]

2 hours ago, yoadknux said:

how inflexible they are towards each other: Meta for not allowing official rollbacks and ED for not releasing a hotfix. 

This is what I wrote before. I don't understand why a hotfix cannot be released if it is ready for the current version of DCS we have. We don't have to have anything more and nothing new. Interestingly, I still have v.62, so everything is OK for me, but, for example, my friend currently does not fly in DCS, but in IL-2, he is waiting for the patch, DCS doesnt work for him and he doesn't want to mess with the files. Fingers crossed for this week.

[slughead]

1 minute ago, YoYo said:

This is what I wrote before. I don't understand why a hotfix cannot be released if it is ready for the current version of DCS we have. We don't have to have anything more and nothing new. Interestingly, I still have v.62, so everything is OK for me, but, for example, my friend currently does not fly in DCS, but in IL-2, he is waiting for the patch, DCS doesnt work for him and he doesn't want to mess with the files. Fingers crossed for this week.

I guess you don't work in the software industry.

[yoadknux]

7 hours ago, slughead said:

I guess you don't work in the software industry.

Working in the software industry means you can't communicate with your users? Does the average player have to go into DCS forum -> DCS 2.9 -> Bugs and Problems -> Output and Visual bugs -> VR bugs to figure out why his game no longer launches? Two weekly newspapers were released since the bug was introduced, no mention of this giant incompatibility issue. 

[slughead]

1 hour ago, yoadknux said:

Working in the software industry means you can't communicate with your users? Does the average player have to go into DCS forum -> DCS 2.9 -> Bugs and Problems -> Output and Visual bugs -> VR bugs to figure out why his game no longer launches? Two weekly newspapers were released since the bug was introduced, no mention of this giant incompatibility issue. 

I was referring to a hot fix availability.

[seavoyage]

23 hours ago, seavoyage said:

I was only able to launch DCS if on SteamVR. Unfortunately can not migrate any of the purchased mods from ED E-shop (Only possible from Steam to ED standalone). Meta confirmed can not roll back from autoinstalled v63 to v62. On SteamVR both DCS Standard and MT work fine. OpenXR is enabled.

From Oculus:

"For now it seems like the only solution is really to play via Steam by using the launch option force_oculus_VR. I'm not sure if DCS allows it, but maybe you could login to your Quest account inside the game via the Steam? If it does, that could be an option to play.

Aside from that, I don't see much of an alternative until the fix rolls out from the developers. You can try to look for ways to roll back to V62 if you really have to, though I can't advise it as they are all unofficial methods, but some of them do mostly work."

 

Progress?

ED Support suggested renaming the DCS folder and the result:  DCS v2.9.2.49940 Open Beta (non_steam) VR Enabled (Oculus v63)  launched!  ...but only once

After DCS launches it creates a new DCS folder and I'm back to DCS not launching as DCS ignores the renamed folder.  I have to manually delete the generated Saved Games\DCS folder to launch on OculusVR.

A new options.lua is generated in ~\Saved Games\DCS\Config and you need to disable VR to relaunch DCS. I override the Saved Games path with DCS Updater Utility and Launch VR On or rename options.lua to options.lua.BAK .  This hack occasionally launched DCS VR enabled in v2.9.2.49940 Open Beta and Oculus is v63, OpenXR

Same finding when tested on v2.9.3.51740.

Meanwhile - SteamVR is the backup. DCS Steam is v2.9.3.51740

Edited March 17, 2024 by seavoyage

[seavoyage]

I was only able to launch DCS if on SteamVR. Unfortunately can not migrate any of the purchased mods from ED E-shop (Only possible from Steam to ED standalone). Meta confirmed can not roll back from autoinstalled v63 to v62. On SteamVR both DCS Standard and MT work fine. OpenXR is enabled.

Progress?

ED Support suggested renaming the DCS folder and the result:  DCS v2.9.2.49940 Open Beta (non_steam) VR Enabled (Oculus v63)  launched!  ...but only once

After DCS launches it creates a new DCS folder and I'm back to DCS not launching as DCS ignores the renamed folder.  I have to manually delete the generated Saved Games\DCS folder to launch on OculusVR.

A new options.lua is generated in ~\Saved Games\DCS\Config and you need to disable VR to relaunch DCS. I override the Saved Games path with DCS Updater Utility and Launch VR On.  This hack occasionally launched DCS VR enabled in v2.9.2.49940 Open Beta and Oculus is v63, OpenXR

I am now testing on v2.9.3.51740.

Meanwhile - SteamVR is the backup. DCS Steam is v2.9.3.51740

[DCoffey]

19 hours ago, slughead said:

I guess you don't work in the software industry.

I do and have for 35 years now. While I rarely do HOTFIXs; occasionally an issue arises where I must and it's not a big deal. I make a new branch from master, add the fix, do a pull request to master and then apply the change to the current development branch. 

[g5flyer]

2 minutes ago, DCoffey said:

I do and have for 35 years now. While I rarely do HOTFIXs; occasionally an issue arises where I must and it's not a big deal. I make a new branch from master, add the fix, do a pull request to master and then apply the change to the current development branch.

Yeah, if the situation was big enough and there were no work around, we make a hotfix and push it. It's the beauty of having that pipeline in continuous deployment.

[slughead]

3 hours ago, DCoffey said:

I do and have for 35 years now. While I rarely do HOTFIXs; occasionally an issue arises where I must and it's not a big deal. I make a new branch from master, add the fix, do a pull request to master and then apply the change to the current development branch. 

So you will also understand that it isn't always possible or appropriate to divert team members from other activities to generate patches. Regardless, this question was not directed to you.

[adam34aus]

Release the bloody hotfix ffs before the next patch

Edited March 18, 2024 by adam34aus