FS2020 not happy with my 1080ti for VR

User Support Hub Virtual Reality (VR)
,
1

Hi there. I am new to VR, so please bear with me. Hours of searching the web as well as these forums unfortunately has not given me a answer/remedy yet. Any assistance will thus be greatly appreciated.

FS2020 non-VR runs fine on my PC and monitor.

Whenever I try to enable VR in game (tried switching to VR before initiating the flight from General Settings → VR Mode → Switch to VR as well as after starting the flight and then pressing Ctrl-Tab) . In both cases FS2020 then shows an error window that says “Your GPU doesn’t match the requirements for VR compatibility, please verify the GPU you are currently using”. The only option is to press “OK”.

Screenshot (82)
Screenshot (82)1920×1080 115 KB

I’ve read numerous forum posts where users are indeed successfully using 1080ti’s as well as Quest 2’s for VR in FS2020. The 1080ti should also work as per Microsofts minimum hardware specs for FS2020. What am I missing?

My hardware specs are:
1080ti with latest drivers installed.
Asus prime X570-p motherboard with AMD ryzen 5 5600x
32gb ram
Win10…all updates installed
Oculus Quest 2 , PTC enabled, Latest PC software and Headset updates installed (also tried Link and Airlink)

Nvidia control panel settings:
Texture Quality: High Performance
Vertical sync: FAST

Any suggestions will be greatly appreciated.

Thank you in advance.

2

This is, indeed, puzzling.

Have you tried setting ALL your VR graphic options to LOW to see if that kickstarts it?

And you are pointing to the Oculus VR in the Registry aren’t you?

3

First, in the Nvidia control panel 3D settings under the program tab for Microsoft FS2020 the OpenGl redering GPU has your 1080ti selected and not the default motherboard (if exist).

Also try the Oculus app in the Beta tab towards the bottom the runtime is set to Oculus or OpenXR.

If using Virtual Deskop then the SteamVR runtime.

4

I’ve never seen that message, I can confirm 1080ti works fine, almost identical specs as you.
Worth checking nvidia control panel but a bit puzzling as there isn’t onboard graphics with ryzen 5 series.
Before I upgraded I ran vr with 1660ti

5

I never saw that notice with my 1080ti and Valve index…but performance was really not that great

6

Would it be possible that MSFS checks integrated GPU, not 1080ti?

7

Yes, this seems the most likely answer to me. Perhaps you can set your BIOS to use the PCIe GPU on boot and disable the integrated GPU?
I have a 1080Ti and it’s working fine (although I use 457.30 drivers - but the latest ones work too)

8

Hi Everyone. Thank you for all the suggestions…

I have read before that some users reported issues with oculus link after Nvidia driver updates.

I have now, for what feels like the 100th time, uninstalled all Nvidia drivers and software as well as uninstalled oculus pc software. I tried various Nvidia drivers from the latest all the way back to Feb 2021 - made no difference.
Currently on 461.72…I’ll try 457.30 as well and set BIOS to use PCIe GPU, as suggested…however, as far as I know my Motherboard (Asus Prime X570-P) does not have integrated graphics.

All anti-virus programs are disabled and I am using a windows admin account (I’ve also tried using another new admin account - makes no difference).

I have double checked the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1

ActiveRuntime is set to: C:\Program Files\Oculus\Support\oculus-runtime\oculus_openxr_64.json and I confirmed the file actually does exist in that location.

In the oculus pc app under Beta tab towards the bottom it also shows the runtime is set to Oculus or OpenXR.

In Nvidia Control panel:
3D settings / OpenGl redering GPU is set to my 1080ti
Texture Quality: High Performance
Vertical sync: Fast

I do suspect my problems might not be specific to FS2020 though. When I received the headset I initially struggled with link regularly disconnecting. This was solved a couple days later after setting USB root hub power settings via device manager to not allow windows to use power saving on the usb ports. For two weeks the headset worked very well in DCS via link cable. I seem to remember using the headset once during that time in FS2020 in VR, without issues, but I have tried so many variations,etc since my issues started, I honestly cannot remember anymore. Then about four weeks ago the Oculus pc app suddenly did not want to start as before…when starting I would get “Can’t reach Oculus Service” message with a “Repair” button shown. For what it is worth, under windows services though it shows “Oculus Runtime Service” as Running. After days of internet searching, numerous “repairs”, un-installation and re-installs of the oculus link software and several factory resets of the Quest 2 headset the problem persists. The only way I can get the pc link app to start is to manually run OVRServer_x64.exe first and then start the app. Same goes for the Oculus Debug Tool…will not run without manually starting OVRServer. Under “devices” my Quest 2 shows it is connected, it passes the link connection test and reports the connection correctly as usb3 and I can then enable Oculus link in the headset as well, after which I am taken to the usual “room” when the link cable is connected. However…Whenever I start a game on the pc (DCS or Xplane), it initially shows a static loading image in the headset, but no other video is displayed in the headset, even though the left lens vr image is displayed and running fine on the pc. One can hear the correct audio in the headset though. I am unable to understand how it could work without issue for 2 weeks prior…and that was with Bitdefender antivirus running as usual. I was also using Oculus Tray Tool during that time with no problems. Sometimes when the pc Oculus Link app starts( utilising the process described above) for literally a split second a red bar is shown saying “Oculus isn’t compatible with this systems hardware” and then disappears. This was never displayed before, as far as I can remember. I made no hardware changes. I seem to remember the only out of the ordinary thing I did during that time was to enable network sharing on a folder on my computer…The other computers on the network could still not access files in that folder via the ethernet and as such I adjusted some folder sharing options. I have subsequently rechecked all the folder sharing settings and can’t see anything out of the norm…I can’t think this could be the culprit but with windows I guess anything is possible. A more likely culprit, I also seem to remember an update of some sorts installing when I shut down my computer that evening, which I can only think to be an automatic windows update…I have tried to roll back the windows updates to a state before but not all the modules could be uninstalled again…As I said, this might be the culprit but I have no way of knowing for sure and I am pretty sure other users are using the latest win10 version without problems. I have subsequently installed all win10 updates again. Too late now, but I should obviously have made a restore point when everything was working but to my dismay I did not think of it at the time.

At the moment DCS and Xplane11 will not start in the headset if initiated from the pc. All I get is a static loading page of the game logo in the headset while the program starts up correctly on the PC…I can hear the program sounds on the headset though. When selecting the desktop button from the ring of buttons shown in the headset while in the oculus link virtual space my desktop monitor’s display is correctly shown and I can interact with it with the hand controllers (so data is sent to headset) but VR imagery is for some reason not getting through. I can get Xplane11 to start correctly in the headset if I initiate the program from within the headset (clicking on the game icon shown in the history bar in the headset). The same does not work though for DCS, in which case the VR image is shown in the headset for a split second in the headset and pc monitor and then the game crashes/auto close.

I’ve been in contact with Oculus support for weeks. Tried all their suggestions - nothing worked thus far…When asking them about FS2020’s problem I experienced they said I should contact the 3rd party developer - which I did…still waiting for a response and that is why I posted this message.

I have a feeling my misery will end or at least be reduced when whatever is interfering with the normal starting of the oculus link app (i.e. not having to manually run OVRServer_x64.exe first) is rectified. I am pretty sure the problem is something silly, hidden somewhere but I am at a complete loss what it could be…I have a fair amount of computer literacy but this has me stumped.

Again, any suggestions will be highly appreciated.

Thanks!

9

If you’re having issues like this with the Oculus suite, then you’ll need to get those sorted before FS2020 will have a chance!

Any help here?:
https://www.reddit.com/r/oculus/comments/muo5ku/oculus_link_instantly_crashing/

10

No comfort for you but everything I was going to suggest you try, you’ve tried already. Thank you for a complete diagnostics report.

Please do report if it works in the future and what you did.

Best wishes.

11

If there was ever a case for a logging file, this is it. In this situation, MSFS has somehow identified this card as being insufficient for VR. What methodology did it use? A log file would (hopefully) display what MSFS used for its determination, what it found, and why that isn’t sufficient.

12

How much effort is it to do a fresh install of windows etc, there’s quite alot of events you’ve gone through during the short life of your headset, I’m trying to ruleout something got changed along the way and might be causing the problem, although it looks like youve been fairly dilligent in your approach. The link to reddit might be useful as the debug tool helped to identify a setting (bit rate) that was set too high causing an instant crash

13

Oculus itself use a txt file (or XML) with all GPU accepted, and often forget to update it when a new card is released. It’s the most easy way and I guess msfs have a similar approach. As it was working previously it should not be the problem you meet…

14

Based on your description that followed this, I agree. I don’t know what the problem is, but the fact that you have to do all that extra stuff just to get Link to work in other VR apps indicates something is wrong at the Oculus software/service level. Or even at the OS level, causing the Oculus service to flake out from whatever is causing MSFS to also not recognize your GPU.

15

Thanks again for everyone’s inputs. I sincerely appreciate it. I have been holding out on doing a fresh windows install, mainly because I was hoping to avoid the effort of re-installing everything, plus I have read several online posts where others have tried it and it actually made no difference…but it is the only remaining thing to try that I can think of as well.

I did start up the oculus debug tool as suggested to check the settings…Bitrate setting was at 0 though and all the other settings seemed to be correct…well, according to my limited knowledge of VR settings - I’ll be the first to admit I still have heaps to learn in that regard. But it does unfortunately highlight the fact that just one odd setting can make the whole house of cards tumble to the ground.

Microsoft has today asked for DxDiag and MSinfo files…hopefully they can learn something from them and point me in the right direction. I’ll report back when I get an answer.

Thanks again everyone! Blessings

1 Like
16

Hi Everyone. Just a bit of feedback.

After trying everything I could think of to rectify this, plus everything recommended by Oculus, Microsoft and everyone else, I ended up formatting my C: drive and re-installing windows 10…Updated windows with latest updates, latest Nvidia drivers and Re-installed Oculus link software, etc. Oculus link now starts correctly again!

Thought I would have to reinstall the whole FS2020 from scratch…However during the install process, after pointing to the old FS2020 install directory on my D drive where I initially installed FS2020, it only took a couple minutes and FS2020 was up and running again - thankfully! Everything works now! No error message when trying to select VR in FS2020 as before.

Thanks again for everyone’s recommendations etc.

Blessings

3 Likes
17

Did you run MSFS 2020 with a 1660ti? Results? Low settings only? FPS?

Thanks. Awaiting delivery of my G2.

18

I couldn’t get acceptable performance with a quest 2 but this was back in January so upgraded to a 1080ti.
G2 is more demanding also. Give it ago see what happens.

Ga aircraft are less demanding and try mountain flying first rather than cities. Courchevals a good airport to take off from.

19

Thanks. Will do.

20

Hi.
Sorry, I also only have a 1080ti…so can’t comment on 1660ti.

I followed the following settings for MSFS and Quest2:

For the G2 I guess you can try these settings (they were done with a 3090 gpu though):

Better PC hardware and VR headset will obviously have better results, but as a new VR user I am still blown away every time by the immersion, even on the Quest 2 with 1080ti. I understand the G2 should give you even better results.

All the best.