My Oculus Quest 2 has been running MSFS OK for a few months, but yesterday, when I was setting up the headset and got to the curved menu bar, the two buttons on right are missing, including the one to switch to the PC desktop. So obviously I can no longer run the sim.
The headset itself is running ok, with both controllers working. In the Oculus desktop app, I’m logged in, and the Quest2 and controllers are showing as connected.
There is a diference when I open the debug tool:
Pointing to one of the greyed lines (which I’ve not seen in the debug window before), a message comes up saying “Options like this are only available in internal builds”.
I “repaired” the app, and it worked properly once (with the normal debug window, and all the buttons on the curved toolbar), but now it’s gone wrong again.
I’d appreciate any suggestions as to what’s gone wrong, and how to put it right.
Thanks.
EDIT: Actually, I’ve found if I run the sim and press Ctrl-Tab as normally, it does connect at this stage. It’s still annoying though that I can’t connect to the desktop normally, so I’m still looking for ideas.
Oculus configuration. There have been a couple updares recently, both PC dedktop software and Quest2 updated to v.44 a day apart, and some things were funky until they both were on the ssme build.
Sorry to break up the party but for me, from my experience over the years, MSFS does not play well with Oculus/Facebook/Meta Quest 2, and this is not case for everyone. At least try to use Virtual Desktop and SteamVR, for me (and others) it works very well, always.
SteamVR is a good option for some, but for Quest/Oculus ive been Beta testing since 2019 and fly every sim using Oculus/Meta products on Windows10/11 and the VR implementation in FS20 is wonderful. Being able to switch VR on and Off on the fly is rare. Steam is not optimized for VR, and the default supersampling negatively impacts performance. I dont recommend Steam for a game that can fully function standalone. Heck, you CANT update FS20 with Steam, its just a launcher wallet for Microsoft Products. I close it completely before flying on mu Quest2 with Airlink wireless as seen in my previous Twitch sample.
Thanks for the suggestion, which I thought was a good possibility, but I checked the update versions and they’re both on v.46. Disappointing.
I’m beginning to wonder if they’ve completely removed the Desktop option from the curved belt in the new update, so I’m on a wild goose chase.
It’s not as bad as I first feared, though. I can connect to the flight sim as normal by pressing Ctrl-Tab once the sim has loaded. The first time I tried to exit VR mode I got a CTD, but it’s been OK since then. So it’s usable, just not so convenient.
I’m experiencing the exact same issue…missing desktop button. Also happened for me after updating to most recent Quest 2 firmware. Hopefully Meta will sort this out soon. In the meantime, I also discovered I can CTRL-TAB in. However, not seeing my desktop makes it more difficult to pop out and adjust settings in OculusTrayTool.
Yes, mine seems to have happened after the update. I searched the internet and could find anyone else with the same problem, so I thought it was just me. If you’ve got the problem, it helps confirm my suspicion that the update was to blame.
While it isn’t a showstopper for me (as you say, it’s still possible to Ctrl-tab into the sim), it is an annoyance. I used to put my headset on before starting the sim, and was able to load the sim, modify as necessary, fly and exit before needing to remove the headset again.
What worries me is that the button has been removed deliberately (for whatever reason), and we won’t see it back again.
I just found this question asked yesterday on the Oculus forum.
The reply to it was to opt out of the PTC (Public Test Channel, in OculusApp:Settings:Beta). I checked, and found I had indeed (unwittingly) opted in to PTC, so I tried this, which allowed the app to revert back to V44 (from V46), and the desktop button is back!
I only had the PTC enabled because I slavishly followed a published list of things to do to enable VR in the sim, assuming it was a necessary step. I should have looked into it a bit more.
NB: Aplogies to @arho10 for not reading your post more closely.
