For me I wasn’t even managing to get my PC and Quest 2 connected with either the KIWI or Anker cables that many people are using. I can add my headset device from within the Oculus Home PC app and the connection test works fine showing 2.2GB and USB 3. But when trying to enable Oculus Link in the headset (V26) just wouldn’t connect and my PC would get some error messages saying there was an error connection to Quest, no error messages in the headset tho, after getting a black screen with 3 animated does it just reverts back to the main menu after a while.
I actually got link working by uninstalling everything to do with VR and then manually going thru the registry deleting any key or value related to Oculus. I then installed the PC app again and link started working, but the performance and quality in anything such as DCS, MSFS and X-Plane is awful, but oddly anything from my Steam library works fine (using SteamVR) but none of my flight sims are the Steam versions and adding them to my Steam Library doesn’t work either.
I submitted a support ticket at Oculus with everything in great detail and they’ve just replied and are basically blaming it on my setup and not using the official cable, but I noted loads of others in the official forums with the EXACT same problem and they’ve asked me to prove it! So they can go £uck themselves.
I can get DCS, MSFS and X-Plane all working fine wirelessly using the Virtual Desktop app and Steam VR.
But I’ve assumed performance and quality would suffer greatly using this method as it would be sending data from my PC to my router’s range extender and then onto the headset. Note, I can not use a wired link from PC to router as it’s not mine and too far away.
Hence why I opted to go with a link cable (KIWI one first then Anker one) but as I’ve not been able to get a link working with these sims I’ve not been able to do a comparison between cable versus Virtual Desktop wireless and Steam VR!
Yes v27 fixed the issue, I tested it for an hour today, but I still think v24 is a lot more stable and less power hungry.
1 Like
the way I start up my VR in MF is as follows:
1 start pc
2 run Oculus app on PC
3 turn on VR headset (Oculus Quest 2)
4 in the HMD, click and connect Oculus link, make sure its connected.
5 jump back out and start ODT ( make Sure AWS is Disabled, Adaptive GPU Performance Scale is Off, FOV Stencil Is off)
6 start Steam on PC
7 Start MF on Steam and wait for it to load onto the main window
8 Control Tab to get into VR mode.
(if you are using OTT, start OTT after MF is running and not before or it won’t take affect,
Again ASW off or forced 45) GPU off)
I think the start up order is wrong, VR should be connected prior to MF starting or you will get mega stutters and bad frame rates.
How did you get V27?
I’ve done the rollback to V24 and it has worked so far in X-Plane, so I am about to try DCS and MSFS.
However - in the Oculus Home PC app there is a red bar at the top with “New drivers are required for Oculus - Update Now?” - should I update or will that undo the V24 rollback?
I see your sequence here but which do you think I should get up and running first:
1] Launch Oculus PC app, then connect and link headset, then launch DCS/MSFS
or
2] Launch DCS/MSFS, then launch Oculus PC app, then connect headset
I guess it may differ from system to system so I will try both 1] and then 2] and see if it makes a difference.
Thanks for your help/advice here, if V27 seems to be working then I would like to try that if possible, after making backups of V26 and V24 though!!!
Updated to Version 27 beta…flashes gone but every 5mins or so VR crashes out. I’ve never had a crash in MSFS but now the VR goes back to my oculus home page and the normal 2D game keeps playing fine on my monitor. If I press to start VR again all works great for about 5 mins again then it drops out. This has only happened since using Version 27 beta.
Defo option 1. Start oculus app and then quest link before MF, v27 works just update the driver and see how u get on. Make sure you either run OTT or ODT.
That’s new to me. Not heard it bombs out every 5 mins. Maybe your setting are set to high for it to render on MF
To get v27, just open into public test Chanel then it will download the new version.
I get great framerate, when I connect the rift to the pc doesn’t seem to matter as long as the oculus software is running before I launch the game.
Link worked fine when I launched MSFS first then the Oculus PC app and then connected the headset and enabled link from inside it, my only issue is the horrendous frame rate and stutters I’m getting but I expected that using the GTX980 and intend to get a newer GPU once these crazy prices settle down.
I noted that when I did the Oculus stuff first and then launched MSFS it was extremely sluggish even in the MSFS menus and stuttered all the time.
So I’ll be sticking to this hybrid frankenstein setup until V27 will definitely work for me!
My settings worked great before this v27 Beta. Even with it I have a high fps. It just pops out of msfs every now and then. odd! I’ll try a full clean install tomorrow. if that doesn’t work I’ll try version 24 and if that works then I’ll know it’s the new beta.
1 Like
I made several flight tonight, longest was 32 minutes, and all is fine for me, not a single “white flash” or “violent head position shift”, and no crash at all. It’s definitivelly fixed.
I get the feeling that I have less stutter than before, but it could be placebo, or stars well aligned like it often happen with MSFS (random performance). I used 45fps locked ASW OFF, but also tested ASW ON and despite the lower GPU headroom it gave (expected due to ASW computing) I had the feeling it was smoother than previously, even if GPU usage was similar to previous days. You know, with ASW ON when it seems to display 2 times the same frame before jumping to the real next one. It happened less.
We are near a real smooth experience with ASW ON (that’s usually my preference), sound great to me!
2 Likes
Why in the world won’t oculus just give a freaking roll back option? Ridiculous!
1 Like
I can confirm reverting to Oculus driver v24 solves the flashing behaviour of v26. At least for the Rift S I’m using. In fact, I’ve just completed a 30min flight in the G36 without a single flash and with perfectly stable frame rate. Hence, even better performance than v25. The great thing about this solution of course is that it prevents Oculus forcing any further updates that might damage our VR enjoyment still further. It would be good if someone could confirm the same for the CV1 and Quest headsets too. Thank you Michalopole818!
1 Like
Yeah man, feel the same. Lots of people says v25 was great or better. Not for me. Started to look for solution to get back to v24 at v25 already it was way worse… Before v26 flashing. I don’t care for updates. Some say current v27 beta is awesome. I don’t care. Maybe they revert oculus to v24 and called it v27 would not be suprised. Glad it worked for you and thanks for letting me know. Keeping v24 as long as I can.
1 Like
Yep… I think we can get hung up on installing the latest drivers. How many of us, for example, are running the latest NVIDIA graphics drivers? I’ve certainly frozen mine at the version developed for launch of FS2020. Often developers are forced to update drivers to support the latest games as they arrive on the scene but then almost inevitably these updates mean they’re no longer optimised for earlier applications. For now I think I’ll stick with what’s stable and works well. Cheers.
1 Like
I thought I had solved C2D issues by re-installing fs2020, but what I just discovered after reverting to v24 and then going up to v27 beta is that the C2D issue I was seeing in both x-plane and fs2020 seems to be related to oculus. In v26 beta I didn’t have any c2d, when it went live I had the flashing issue so I reverted to v24. I didn’t have c2d in v26 beta but in v24 they came back. Once I upgraded to v27 beta I don’t have flashing and don’t have c2d anymore. So I assume the mysterious C2D many people have where FS2020 closes without any details in the error log other than fs2020 closed may be related to the oculus drivers.
One thing the v27 update seems to significantly help with is this weird problem with the wings while on the ground. I had noticed in v26beta this warping effect on the wing where the wing seems to become transparent and the ground shows through the wing with a sort of aliasing look to it. v27 fixed this problem for me, now the wings no longer look possessed while taxiing. So V27 Beta seems to be an excellent patch much better than the v24 rollback.