Very unusual ground performance despite a displayed 60+ FPS

User Support Hub Install, Performance & Graphics
,
1

So I recently upgraded to a 5800X3D, 32GB 3600RAM, and a 4090. All great.

Yesterday I updated my driver to the latest game ready one (I don’t use Nvidia Experience)

Set my flight from the last place I was, one of the new NZ hand-crafted ones (Can’t remember exactly where off hand but south island west coast)

I was in the Twin Otter and I noticed both with and without the Tobii 5 that panning around the cockpit was incredibly jerky. It reminded me of my VR experience when I was back on a 2080ti.

The displayed FPS in debug mode was a minimum 60, limited my main thread as usual. What I was seeing was definitely not 60FPS. It was jerky and very inconsistent.

All settings are pretty much ultra with the 2 LODs @ 200.

In the air, things seemed ok and displayed FPS 80-120.

Landed at another small new airport from WU12 and the same thing, Jerky.

I had no AI traffic on (i’d have seen non on the route) and only Navigraph open.

I only make the usual few settings changes to Nvidia Control panel

New driver problem maybe?

1 Like
2

Ive seen same problem flying at 1000’ over cities, dropped my quality from ultra to high end, this seems to have resolved it.
Did notice, little change in fps; during jerkiness the GPU dropped significantly during jerky period.
Will have to do some reading to see if there are other solutions.

3

Remember to delete the windows shader cache after a driver update. Let us know how it goes.

1 Like
4

Thanks, you got me with that one, where do i find the windows shader cache?

5
6

I think on the ground that Object LOD plays a big factor. You might try lowering that. Good luck.

7

Thing is, there is nothing anywhere near me in either airfield. The terrain is of course interesting but there’s literally zero objects anywhere near.

If I’d have been in a major city I’d have understood

8

Have you cleared the shader cache yet?

9

Job for later. i’m going to do various bits and test, that being the first. Will report back

1 Like
10

That makes sense but it might be worth trying anyway. My thought is that normally when flying you’re GPU bound and when on the ground something is causing extra stress on your other component like the CPU. The LOD’s are extra CPU stress. This could affect your 1% lows so even though your average framerate is showing 60 you probably have something making your fps jerky (jumping around) which would be measureable by looking at your 1% lows.

By the way, a program such as CapFrameX could measure your 1% lows. What I do when I have a problem like yours is first disable all addons, and then use CapFrameX to get a baseline. Focus on the 1% lows. Then change settings one at a time and watch the 1% lows. You can usually find the culprit.

11

Will try to determine my 1% using your method.

Ironically, when I have FSLTL on and little navi map, I typically don’t experience what I did yesterday. I only had Naigraph open.

No other addons (which would be being utilized in the problematic scenario)

12

Do you have HAGS activated in the Windows settings? I had the exact same issue and could solve it by deactivating this settings.

You can find it under graphics settings → hardware accelerated GPU scheduling

13

I do but isn’t that required to enable DLSS 3?

14

I disabled it in Nvidia 3D settings and the 70-80FPS I now seem to be getting, in the same scenario, feels like 70-80FPS, so perhaps that was the fix!

I do get some tearing though but I have VSync turned off so I put that down to that

1 Like
15

I dont think you need it, I have it disabled and do use DLSS. For me it was the fix and I am happy if I could help you with that.

HAGS does only make problems and that’s also what a lot of users here have reported…

Vsync off and Ultra for Low Latency Mode in the NVCP is a great combination.

16

Hi mate, shader cache is part of the windows OS, not something you can disable. If you click on the link to the other article I posted above, it will show you how to clear it, just takes a minute.

17

You can turn it off in the CP - or alter its size

18

Thats the scenery cache. The shader cache is part of the Operating system. You can’t configure it, it isn’t part of MSFS.

19

Its the shader cache. Its a global setting that applies across all games

20

Well, if disabling that shouldn’t in theory have been what was causing the issue, it means it was just an isolated and unknown issue I was experiencing.

Or, perhaps network issues