Tip for Nvidia Users- Check your 3D settings

[CptLucky8]

To all:
Here is the topic about the NVidia CPL Anisotropic bug, and several side-by-side showing that FS2020 settings are doing what they are expected to:
PSA: NVidia Anisotropic Bug: in-game setting disabled (was: Some tests on Texture Resolution and Quality) - Community / General Discussion - Microsoft Flight Simulator Forums

@KevyKevTPA
Here are my latest Index setting for SU5 HF1 (for HF2, just change TLOD and OLOD back to 100%):
My 2070 SUPER VR settings and suggestions (Index - SteamVR) 🟢 - #547 by CptLucky8

And some more comments:

@CptLucky8

I’ve disabled Tex. SS for now because in previous versions I believed this was one important factor to fps degradations at airports, especially large ones with lots of markings on the ground. This is why I’m using Aniso 16x for now in order to compensate, and except the RWY center line, usually it is still bearable with the Index resolution.

Otherwise after many tests in earlier VR versions, the best setting I’ve found back then (visuals and perf) was Aniso 8x and Tex. SS 4x4. I’ve not really tried it yet with SU5!

@CptLucky8

One of the reasons behind 126% and 152% (+ FOV 95%) is that with the Index native panel resolution and lens distortion, it seems to me these are slightly enhancing aliasing compared for example to 125 and 150, compensating a little bit for the blurriness due to motion smoothing and/or FS2020 rendering. It is really subjective though but it seems it is striking a balance to me, enough to make barely legible middle EFIS small letters slightly more legible (but aliased).

@CptLucky8

I’ve done a few more tests yesterday about this. Motion smoothing is taking more resources and usually you can balance this out with fewer frames per sec (and artifacts of course).

With the 9700K+2070S I can barely push beyond 152% and 18fps with the Index and FS2020 with aircraft with lots of EFIS for example, like the FBW A320 (for this one I must go 15fps on ground but can switch back to 18fps in the air) (NB: I can push much higher with XP11 though)

What stroke me is how much FS2020 has a struggle when on ground, to the point I have to disable motion smoothing otherwise FS2020 is like rendering pairs of frames in reverse order (displaying frame 2 first, then frame 1 next, then frame 4, then frame 3 etc… this is what it looks like).

Yesterday I’ve tried the FBW A320 latest dev version but this time with motion smoothing off. I’ve been able to keep 30fps (SS 152% and all the rest unchanged) on the ground, and when up in the air 45fps, and this was not bad at all to me.

If you read this topic from the beginning and when VR was initially available, I was explaining how 30fps constant is still useable in practice with the A320 (not FBW back then) and after a while you get used to the juddering. It has been months though that I’m only using motion smoothing at 18fps so I go used to the artefacts instead! Switching back to motion smoothing off was slightly uncomfortable at first because of the juddering but at 45fps it was not so bad after a short while, especially if you develop the habit of rotating the head (reprojection kicking it) instead of translating it (juddering is unavoidable in this case).

This is a short feedback post to share the experience!

PS: about “FS2020 on ground taking too many resources while on ground to the point I have to disable motion smoothing”: this one is puzzling me still because in 2D I can see there is still enough room on the CPU/GPU. I’ve been wondering whether FS2020 wouldn’t be using the GPU in a way which is interfering with the Turing silicon the NVidia Optical Flow lib is using for motion smoothing. What I mean by this is that it is has if both FS2020 and Optical Flow are fighting for the card silicon, which could be the case if for example FS2020 would be using compute shaders for example and if those would take a longer processing time when on the ground (handling much more things). This is one area I’d really like to figuring out, at least just by mere curiosity for these sort of things!

PS: I’m not done yet adjusting for the Index, thus I’ve not tried the G2 with SU5 HF2 yet.