Moxy Posted March 12 Report Share Posted March 12 The Quest 3 app, has an "Auto Update" . The update breaks my DCS vr mode, game launch. Including breaking a complete new predestine install. Reinstall the app version before the update, launches....4hrs later, auto update, game crashes on load up. Just found the post. Quest3's look dead in the water, for a fix https://forum.dcs.world/topic/345145-dcs-wont-lauch-since-meta-update-today/#comment-5395706 Mox Snaggle and Klaiber 2 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 Oh Man... that's B.S.!!! I wish all these tech giants would make ALL updates optional. They already got our money. It seems that they are breaking stuff to move our hardware into early obsolesce and force us to buy new stuff. (Yeah, I realize that's kind of a tin foil hat statement but still... ) I hope ED steps up to the plate and gets a fix pronto. Meta certainly doesn't give a sh*t. Snaggle and Klaiber 2 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 More on Hoggit. Looks like it affects all the Quests... Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 4 minutes ago, Vonrd said: More on Hoggit. Looks like it affects all the Quests... This scares me bad: Apparently this is an OpenXR feature change. All platforms needs to update it to remain compatible. "One caveat: WMR It is deprecated so WMR as endpoint will not get it (MS stopped working on it). So when ED makes the change in the next patch bye bye Reverb G2. DCS will not run on it anymore probably." However, my G2 worked fine tonight. I'm seriously considering a Pimax Crystal. Klaiber and Snaggle 2 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 Reading through the Hoggit it's been said that ED is aware (how could they not be?) but will not do a Hotfix and will address it at the next scheduled update. If that is actually true maybe EVERYONE should post tickets with support and flood them. Hopefully Bignewey, et.al. will post something tomorrow. Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Klaiber Posted March 12 Report Share Posted March 12 My headset is still on v62 for my Quest 2. I've turned off auto updates in the headset's OS, to try and stave this off. However, if they force the update, this won't work. Snaggle 1 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 Just saw this: 7 hours ago, BIGNEWY said: I have no date to share for the next patch at this time. Patch cycles on average will be every six weeks, it just depends on development merges and testing. That's BS! Six Weeks! I think some stink should be raised but since I'm not affected I can't justify getting on them personally. If it does turn out to somehow bork my G2... That's piss poor customer support more akin to Jason at his worst IMO. Snaggle 1 Quote Link to comment Share on other sites More sharing options...
Snaggle Posted March 12 Report Share Posted March 12 FYI: Further down the post apparent someone found a fix that might work... Factory reset Q3, uninstall software, the post is by: Mrkiliwiggles96 4 days ago. Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Snaggle Posted March 12 Report Share Posted March 12 35 minutes ago, Vonrd said: I'm seriously considering a Pimax Crystal. My backup plan also...... I believe your tin hat post is correct!! Vonrd and Klaiber 2 Quote Link to comment Share on other sites More sharing options...
Moxy Posted March 12 Author Report Share Posted March 12 Public Test Channel. The auto updating is related to the PTC. Apparently if you ever turned on that "feature" its in your "Account" and cant stop "Their" updates. Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Klaiber Posted March 12 Report Share Posted March 12 6 minutes ago, Moxy said: Public Test Channel. The auto updating is related to the PTC. Apparently if you ever turned on that "feature" its in your "Account" and cant stop "Their" updates. So, me shutting off the auto-update won't stop v63? Honestly, if they box the lot of us, I guess we can pick up Minecraft for the next 3 to 4 weeks... Snaggle 1 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 One of the latest from Bignewey We are working with many modules, and the core of DCS, we are already merging and testing fixes for a larger patch. I can not give you a date yet for that patch as it depends on test results for the whole of DCS. I am sorry but its not as simple as you think it is, so we will need to be patient. Again, we changed nothing in DCS, meta's update created the problem. thank you I would think that since a sizeable portion of ED's customer base is affected and, it seems, unable to use it's product (many report the recommended work around not fixing anything) that coming up with a fix, even if temporary, would surpass all other work. As to this statement: we changed nothing in DCS, meta's update created the problem. Guess what Meta's response is? If the issue is only happening with this one game, then you may need to reach out to the game developer and ask that they make the game more compatible with Quest devices. The dueling blame game... and who's the bigger dog in the game? Still, as BN says: [the fix,] its not as simple as you think it is. Snaggle 1 Quote Link to comment Share on other sites More sharing options...
Klaiber Posted March 12 Report Share Posted March 12 Oh, I blame Meta. 100%. All Meta cares about is the Metaverse and stopping the hemorrhage of money. They can't quit the project, and they can't make it profitable. So every other game developer with VR features is forced to be reactive. Quote Link to comment Share on other sites More sharing options...
Flyboy Posted March 12 Report Share Posted March 12 I suspect there is going to be a flooded market of used quest vr headsets Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Flyboy Posted March 12 Report Share Posted March 12 Quote Link to comment Share on other sites More sharing options...
Flyboy Posted March 12 Report Share Posted March 12 Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 12 Report Share Posted March 12 We got a surprise on our tax returns, more than we expected. Karin bought a new iPad Pro and I just ordered the Pimax Crystal Sim (after doing several days of YouTube-ing and forum research). Considering what I've found, I'm slightly worried but also excited. I'll let y'all know how it works out. Klaiber, Snaggle and Flyboy 2 1 Quote Link to comment Share on other sites More sharing options...
Labroisse Posted March 13 Report Share Posted March 13 You'll have to pry my G2 from my cold, dead hands. Snaggle and Klaiber 1 1 Quote Link to comment Share on other sites More sharing options...
Snaggle Posted March 13 Report Share Posted March 13 4 hours ago, Vonrd said: I'll let y'all know how it works out. Looking forward to your thoughts!! Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 13 Report Share Posted March 13 Seems that this from yoadknux has worked for several folks: Posted Monday at 11:15 AM 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. Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Moxy Posted March 13 Author Report Share Posted March 13 Personally I have a V62 download, so I guess I can keep re-installing it for up to 4 hours. Until when? Thanxs Von Quote Link to comment Share on other sites More sharing options...
Vonrd Posted March 14 Report Share Posted March 14 According to yoadknux and several other people: 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. So, if you follow his instructions exactly you might not have to keep re-installing. Klaiber 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.