After playing a few hours, FPS drops from 40 to 5FPS

So I turned off precache, off not down mind you, then did a 3 hour flight no where specific starting in Texas and headed North, and I only loss 2 fps the whole trip, and I didnt really loose them just from time to time the fps would drop by 2 and then a few min later recovered again.

Soooo…turn off pre-caching all together and try it. At the moment my CTD’s seem to be gone as well, but those have never been a all time occurance here. Everything set to ultra with post process turned off on a 1080ti i7-6 16 gigs of ram @ 3840x2160x4k

It only has Low to Ultra settings. How can we turn offscreen precaching off completely?

Update: I found the setting can be disabled on UserCfg.opt file:

	{OffscreenTerrainPreCaching
		Enabled 1
		Quality 2
	}

I’ll give a try and see if disabling it would reduce stutters or avoid memory leak.

1 Like

You might overheat your CPU quite heavily by doing this :backhand_index_pointing_up:t2:

this isn’t the same to the others issues mentioned here as with most of us it’s mainthread and manipulators not GPU … could be drivers seen some bad drivers from Nvidia lately

Put this in another thread but happening to me again.

I don’t think that would be a very good idea. I forget the update, possibly the dreaded SU5, it it was a stuttering mess till the next update came out where they gave us that slider.

It disappoints me no end that they make these kinds of changes that cause real harm to the experience.

The saying “If it ain’t broke don’t fix it” should be on a post-it on everyone’s monitor at Asobo. It was simply impossible to ignore, and. I way could not not have been noticed during testing.

But they absolutely had to make that XBox debut deadline, no matter the cost.

And here we are.

1 Like

ONE CAUSE OF FPS LOSS IS DETERMINED - POPPED-OUT INSTRUMENTS

I also reported my problem earlier about massive FPS drop (from 50 to below 10) after some hours of using the sim. I guess the problem could have different reasons and thus solution (or work around). I made some controlled tests and found something that causing the FPS drop for me.

I used the Kodiak 100 with G1000 Nxi and I used to pop up the two Nxi displays to my second screen so that I could see them better. If I am not doing it, I am not experiencing the FPS drop. I made several cross checks and it seems to be consistent. If I close these popped up screens, the FPS drop stops. I experience a small FPS increase (as there are less info to be displayed), but I am not getting back the original value.

As far as I remember, there were reports about problems with popping up windows more than a year ago, so this is not really a suprise. UPDATE: as I see those earlier performance problems were related to a one time FPS drop when popping up the instruments. That still exists, but not serious. However, in my case FPS is deteriorating by tie and rather soon goes below 10.

UPDATE: THe same is with the standard C172 with G1000Nxi. Within 50 minutes FPS drops from 78 to 50 if the G1000Nxi is popped out to a second monitor. Now I run a test with the C172 steem gauge version where there are other poppable instruments. This is to check if the problem relates to the G1000Nxi or to popping out instrument displays in general.

Same here. 2 hour flight CYSJ to CYYZ (Fly Tampa) in Aerosoft CRJ. Ryzen9 5900x Gigabyte RTX3080 Gaming OC. Completely smooth for most of flight until final. FPS drops way down and becomes jittery on landing and taxi. If I restart the sim and set up a gate at CYYZ, fps is perfect and smooth. So, I am definitely getting a degradation in performance. This seems to have always been a problem with the flight simulator series. It sucks and ruins otherwise excellent flights. :frowning:

Hi all,

I experienced same issues when I do long haul flights.
I tried everything from changing every graphic settings and AI traffic ect ect to see what will help, and it was non of them.

I had to save my current location using the flight plan safe option in the game, then end flight go to the game default world map again and load my current state of the flight plan and boom up went the frame rates again as normal.

Change all graphic settings to low or turn of AI did not help either.

For now this is my only solution.

If i get low FPS when i’m around a big airport using graphic settings on ultra I turn of Airport life. this will improve performance drastically.

On high end graphic settings i do not need to do this.

PC Specs:
AMD 5950X
3070 TI
32 GB Ram

CAUSE: POPPING OUT ANY INSTRUMENTS

I made several tests with the C172 Skyhawk steam gauge and G1000 versions with the same result. FPS dropped from 80 to 10 within less than 2 hours.

This is a problem with the pop out instruments feature of the basic MSFS product. I will open a ticket.

This has been a long-running and still-open issue with Asobo. It’s not so much something is broken, but rather mostly a limitation of DX11 (long story). I believe that last word was it will be improved on DX11 in upcoming updates, and DX12 should handle multiple windows much better by virtue of how DX12 works vs DX11.

I saw this today with the Justflight Turbo Arrow IV. About 2.5 hours into a flight, down to single digit frame rates in the span of a few minutes.

System (no overclocking):
Ryzen 5600X
32G Ram
RTX3080

System built new beginning of year. I don’t have many addons installed (I am wary of perf killing addons).

Things that were different for this flight from previous flights:

  1. Enabled Garmin GNS530 (previously used default instruments)
  2. Disabled 30Hz vsync
  3. This was my first flight over 1 hour in this plane. Previous long flights were in the caravan and I don’t recall having issues.

Things to note:

  1. Pausing sim (not active pause) relieved the issue, but was back as soon as I unpaused
  2. Outside view had same issue
  3. Saving flight, then loading it back (without exiting exiting flight) cleared out issue

Someone know if this bug is currently logged on the RoadMap of Asobo ?

With the PMDG 737 coming, it’s really annoying if we can’t do flight longer than 4 hours, especially with the BBJ built for flights up to 12 hours.

Have a nice day.

1 Like

With major issue - performance over time still present, there’s no need to buy PMDG 737’s. I won’t spend money on product which I can not fully use, because Asobo does not have properly working product. I would love to fly it, but there’s no point when FPS are going to drop after 30 minutes of flying.

I still can’t understand how this issue is still not fixed after more than half a year. It seems they are not even trying to fix it.

They have promised more detailed FPS meter - after more than 2 months it still not implemented. This is massive mockery on community from developers.

5 Likes

Ok, I did 2 Flight tests from LPPT to EDDB. These flights are around 3 hours.
Pass some ocean areas, plains, cities, and a few mountain areas.
The weather changed from sunny to few clouds. Luckily on both flights,
Plane flybywire A320NX version 0.8.0 stable

This is about testing “OFF SCREEN TERRAIN PRE-CACHING” and might help this logged bug.

First Test
“OFF SCREEN TERRAIN PRE-CACHING” to “ULTRA”

Results






Second Test
“OFF SCREEN TERRAIN PRE-CACHING” to “LOW”

Results






New Flight and hold position @ EDDB Gate C5 - Pilot View - for 10 min check (much better FPS)

In-game Graphics Settings (sry very small)

My NVidia Control Panel Settings

Global Settings:
Everything Default except
Shader Cache Size = Unlimited (I recognized much less stutter combined with “OFF SCREEN TERRAIN PRE-CACHING” set to “LOW”)

NVidia Program Settings for Microsoft Flight Simulator:
Anisotropic filtering = Application-controlled
Antialiasing - FXAA = OFF
Antialiasing - Gamma correction = On
Antialiasing - Mode = Application-controlled
Antialiasing - Transparency = Off
Background Application Max Frame Rate = Off
CUDA - GPUs = ALL
Low Latency Mode = On
Max Frame Rate = Off
OpenGL rendering GPU = NVIDIA GeForce GTX 1080 Ti
Power management mode = Prefer maximum performance
Texture filtering - Anisotropic sample optimization = Off
Texture filtering - Negative LOD Bias = Clamp
Texture filtering - Quality = High Performance
Texture filtering - Trilinear optimization = On
Threaded optimization = Auto
Truple buffering = Off
Vertical sync = Use the 3D application setting
Virtual Reality pre-rendered frames = 1

Summary
Panning around during flight was almost fluid on both flights…
FPS on “LOW” was stable for at least 2 hours before I hit German airspace.
FPS on “ULTRA” was just stable for 1 hour. After I passed the Bay of Biscay it dropped.

But overall “OFF SCREEN TERRAIN PRE-CACHING” seems quite unstable. Especially when set on Ultra.
The decrease of FPS on the Ground could be an issue Asobo’s already working on. Or it’s sth different.
Because I see the same FPS drop on “LOW” setting. Although not quite as bad as on “ULTRA”. What is logical.

I actually see a drop from 48 to 20 fps at EDDB. After a 0.5-3 hour flight.
Arriving @ Gate it’s around 30-40% less than what I usually get. In Pilot View.
And this is actually every Airport around the Globe I checked. At least for me.

I never did a long-haul flight with SU9.
But I did one with SU8. And I remember well when I flew EDDB to VHHH.
Before wheels touched the tarmac, my FPS dropped to 12-14 fps.
I survived but this took away the fun.

Now I will keep “OFF SCREEN CACHE” on “LOW” and Frame Rate Limit @ 30. Just to be sure.
And it feels smooth. Maybe because I set NVidia Shader Cache Size = Unlimited.
Idk. But there is no big stutter like I saw in past version or different settings.
Despite 2-5 fps not noticable tiny drop offs when panning around. And a very tiny texture blur for 0.5 sec.

cheers

Intel 8700K
32GB RAM
1080ti 11GB VRAM (512.59 Studio Driver (no CTDs) slightly better performance/stability)
1 TB Nvme gen 3 (Western Digital Black)
200 Mbs wired ethernet connection

That’s my take on it, though it seems to perform better at lower terrain LOD’s. My assumption would be, given its name, that when all the offscreen terrain has been loaded up, with Ultra configured you shouldn’t get stuttering, but that’s exactly what you get. If your restrict your mouse movements to a cone in front of you its fine, but if you swing the mouse the other way it will stutter, then again when you turn back. It’s odd, and nothing quite like what we had before that feature turned up in WU6.

Hi again folks!.

Interesting find here: If I disable rolling cache, the FPS seems steady for me!. Just done a testflight without issues. Will do some more research on this on my end.

Freddy

Okay wow, I’m not sure if the problem we’re having is different to the others who are looking at terrain caching and etc, but I experienced the typical stuttering once more where exterior is fine with massive stutters, and interior is a constant <10fps. This is the first time I got it in the C700, which was great news as I can turn off the screens relatively easily compared to the 787/747. And you’re 100% correct!

The moment I switch off the screens, FPS returns to completely normal and when I turn them back on, it’s still fine for me, at least for the C700. I guess there’s something that gets stuck being rendered through the screens that gets reset by an off-on. Might be worth a try for others, and if so, then we’ve at least narrowed down the (or a) problem a little.

EDIT: Okay so it seems to fix the issue, but after 1-2 minutes the issue reappears. Resetting again fixes the issue once more. Maybe someone else with the issue can test this as well?

For reference I’m also flying over the Germany area, but I doubt it’s area specific as I’ve also experienced it over California, China, etc.

1 Like

I have the complete opposite experience. Panning the camera is terribly stuttery with precaching on anything less than Ultra. Though I haven’t tried turning it completely off in the UserCfg.opt file. (My guess is that would only make things worse for me.)

I also have shader cache set to unlimited, but I really think that is irrelevant.

combined with “Shader Cache Size = Unlimited” and “Low Latency Mode = On” in NVidia settings. last thing I changed after I got some stutter with “LOW” PRE-CACHING.