slughead

Quest 3 headset? You must have a huge amount of planes in your hanger. Fair do's.

Fair point. Have you not tried running via SteamVR in the meantime?

Seriously? Wow. Devoted simmer.

Innit tho. I stopped reading when I saw "--force_unable_VR" as that's not a valid command as far as I can tell from the post at the top of the VR section of the forum: People with no clue are making it up as they go, hoping to be the "saviour of the day". Lol. I refer you to the thread that I just shared.

"Auto updates" is only for the "apps" installed on the headset. It excludes the headset firmware and the Oculus link app that runs on the PC.

Just join one of the Facebook DCS groups. There's always a t-shirt scammers around.

Exactly. Nothing more, nothing less. Can we PLEASE stop with the conjecture and baseless theories?!

So if you don't know, perhaps it would be sensible to not add to the confusion. @BIGNEWY could you please put an end to all this conjecture that ED has not actually fixed this and instead have reported it to Meta. Then perhaps lock the thread until the patch is released. Thanks.

Nowhere does that say that it is "reported to Meta". It just says "meta" and "reported" — two unrelated tags. The first is because it is related to meta. The second is that it has been reported to the dev team - the ED dev team.

No. It's just a tag. Any post related to meta/oculus gets this tag. It's solely so people on this forum can search for all this "meta".

Show us all where it says "reported to meta".

I think some peeps just want to increase their post count.

That does not mean "reported to meta". It's just a tag for anything related to meta. Can you please stop dreaming up such fake news!

Quite. Mostly pointless posts about comparing version numbers, "is it ready yet", conspiracy theories and utter conjecture. Lol.

Yeah, read back up through this thread. They're continually saying it will be fixed in the next release. You only need to back one page.

ED have already said that they have implemented the fix.

There is no magical fix folks. Meta changed the API and it requires an associated change in DCS. It's as simple as that. If your system currently works with v63 and DCS via Oculus link, you've just not been pushed the version that has the change yet. Meta release updates/partial updates in dribs and drabs all the time to different groups of users. It's discussed a lot on the Meta support forums. Next, you will all be moaning when ED release the next build and all those who haven't yet had the affected v63 release find they can't use VR and DCS. @BIGNEWYhas this been factored into the fix or will DCS only work with the new Meta API?

This was in reply to @YoYo who says v63 works.

If you blocked the updater by preventing access to the staging and tmp folders then it possible that only just the version number is updated and not the actual binaries. This may also be complete tosh too. If you have block the folders and you’re confident you’ve been updated, try uninstalling Oculus, check the program folders and the workaround folders and files are gone and then install Oculus again.

It’s less painful to have your teeth removed than speaking to the support team at Meta.

Any. A text file the remove the extension.

Oh right. My bad eh? So the fact that the same thing happened to Steam (and thus all VR games via Steam) was just a coincidence.

v63 is now general release. Opting out of PTC will install v63 again.

Why aren’t you on Meta’s forum complaining about it? This isn’t Eagle Dynamics doing. This is solely down to Meta. So go complain there if you don’t want this happening again.

But you have no control over what meta decides to push to your device. Just all seems a fruitless exercise when ED knows what the problem is, has implemented a fix and will release it in the next build. Slughead out.