yoadknux

I asked Meta to allow rollbacks. What makes you think I didnt? Whatever, this is just another absurd issue of the "sim experience" where you spend more time troubleshooting or waiting for fixes than playing

Yes

This mentality is exactly why this field will never grow and remain a niche, expensive and time consuming segment in PC gaming. Imagine buying a shooter game, and the shooter game works, but one day it stops working with Logitech hardware. So the game launches but the keyboard doesn't work. Or a game that launches only with an AMD GPU and not NVIDIA GPU. A "few weeks" is a very long downtime in PC gaming, enough to make any average player move on. And the fact that there's no official acknowldgement nor a date for a fix just make this issue worse

I understand that its temporary, and like I said, personally I was lucky enough to come up with a roll-back method while it was still possible, so I'm unaffected But how in the world would I recommend ANYONE to spend thousands of dollars on equipment that just becomes incompatiable for nearly a month with no date for a fix? This is NOT the "nature of PC gaming". In PC gaming there are things like driver incompatibility, in which case you can roll back. Or degraded performance. But I've never seen in my 25 years of gaming a long-term update that causes things to stop working alltogether. I'm sorry but this is unacceptable and further alienates casual players from going into sims

I have a friend who wants to copy my exact same setup after seeing it in action, with the exact same DCS modules, specifically because of VR performance. After this recent bug, I really don't know what to tell him. How can I recommend anyone to spend money on a high end PC, HOTAS, DCS modules and a VR headset knowing his setup can become completely useless in the blink of an eye?

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.

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.

I guess enabling auto-updates through the software should work, but I'm not sure. We'll wait and see

No, there is no need.

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.

Follow the steps in my post, I was able to go back to v62 and oculus link works, so far it remains this way. I agree it should be fixed ASAP

There is still no date for the next patch. Better to use one of the suggested workarounds in this thread. I'm already 2 days with v62 rollback using my method.

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.

I think this blocking method works if you pre-applied it. But If you install fresh v62, the moment you finish setting up it will say "core download started", and a few seconds later the snooze or update pop-up. The Staging and tmp folders don't exist before you finish logging into the Oculus app. I am trying to figure out if anything can be done during the "Snooze" period.

Workaround update: If you uninstall Oculus, then delete all Oculus files from appdata, and use a v62 installer (https://www.mediafire.com/file/rn5uurwqvv9qp8q/OculusSetup.exe/file), then you will have a v62 version installed and DCS will work by Oculus Link. The problem is that after logging in you are immediately notified that a new version is available and you either install it now or install it in 4 hours. Once someone comes up with a way to completely block the update, then it will be a good temporary solution until ED fixes it on their part.