There is also a bug where if you enable multiplayer and anyone else in your view happens to have a non default aircraft or livery you get stutters.

This can confuse matters as some airports are stutter fests because there are a lot of players spawning there (rather than anything to do with the scenery). Of course in other cases it actually is the airport that is buggy.

As far as the original question goes - I landed the TBM at LFBO yesterday with no issue but there are definite problems at airports, There is a thread on the mainforums:

 

https://forums.flightsimulator.com/t/horrible-fps-drop-out-of-airports/394309/19

Edited April 22, 20215 yr by Glenn Fitzpatrick

I flew from KSBP to KSBA by flying manually (first south then east over water) in my TBM. No problems were encountered.

Landing easily at 30FPS+  . Did not use ILS.  Hope you can solve this problem. My settings are at the 'high' level with my hardware.

 

Dave

 

Been flying the TBM last few days and using NEOFLY..... no problems landing.

1 hour ago, Eclex said:

I flew from KSBP to KSBA by flying manually (first south then east over water) in my TBM. No problems were encountered.

Landing easily at 30FPS+  . Did not use ILS.  Hope you can solve this problem. My settings are at the 'high' level with my hardware.

 

Dave

 

Thanks Dave, though that differs in that I used ILS and a procedure to get there.  When things started to tank I changed from mostly Ultra, to High, but that didn't help.  I can certainly try w/o using a procedure/ILS and see if that fixes this new wretchedness.

Edited April 23, 20215 yr by Noel

13 hours ago, Noel said:

I wonder if that is a red herring, WT Garmin v default.  Try flying the Citation L from my old home down of KSBP to KSBA, land on RWY07, using the HABUT (i think it is) transition for an ILS approach.  It's a short flight.  This is the one I just did and it absolutely tanked by the time I was maybe 10m out from landing.  Sadly, no one knows what works and what doesn't at this point, but this will definitely be a fresh comparison of our two setups and what happens as you approach the airport.  Thanks in advance!  

 

Here you go, wasn't sure if you wanted weather or not, but here it is. Solid 35-45 frames until final where it dropped to 20 at the last minute. Absolutely no idea what the artifact on the runway at the end was - never seen that before anywhere !!! Video below:::::

Spoiler

 

 

Cheers

 

G

Thanks Gazz very kind of you, that is what I'm seeing, ruination of formerly rock solid 30 frames anywhere near, on, around this airport, and all others for that matter.  I am going to first try an exact landing using the HABUT transition for 07 ILS and see what happens.  I inc the rolling cache to 64Gb per one suggestion.  I should know in a few minutes...

...OK, so about 30m out from KTVL to KSBA, w/ my normal settings which are 200/200/100, Ultra except I will dial back reflections and volumetric clouds to High according to GPU utilization.  I started seeing dips in frame rate into the low 20's over essentially farm land at FL10K, and again, absolutely plenty of headroom GPU/CPU.  So I tried reduced most settings to HIGH, except put volumetric clouds back up to Ultra as well as 16xAF/8xSSAA, and frames returned to 30 locked per vsync, and was able to land w/o a hitch or stutter.

This is foreign to my experience since initial release when I could fly in and out of this airport and all but the most complex areas w/ most settings on Ultra.  My guess is perhaps because of internal changes that happened over the past few WU things are just no longer the same in some basic rendering ways.  The silver lining is even w/ settings turned down image quality is still very good, and I can fine tune more as I go, which is reasonable.  Perhaps HIGH settings now are actually a little better than they were before, i.e. the quality scale has shifted to the right slightly.  I'll be glad if even this holds up because at least I can use the thing!

Thanks for your help Gazz

Edited April 23, 20215 yr by Noel

3 hours ago, Noel said:

Thanks Gazz very kind of you, that is what I'm seeing, ruination of formerly rock solid 30 frames anywhere near, on, around this airport, and all others for that matter.  I am going to first try an exact landing using the HABUT transition for 07 ILS and see what happens.  I inc the rolling cache to 64Gb per one suggestion.  I should know in a few minutes...

...OK, so about 30m out from KTVL to KSBA, w/ my normal settings which are 200/200/100, Ultra except I will dial back reflections and volumetric clouds to High according to GPU utilization.  I started seeing dips in frame rate into the low 20's over essentially farm land at FL10K, and again, absolutely plenty of headroom GPU/CPU.  So I tried reduced most settings to HIGH, except put volumetric clouds back up to Ultra as well as 16xAF/8xSSAA, and frames returned to 30 locked per vsync, and was able to land w/o a hitch or stutter.

This is foreign to my experience since initial release when I could fly in and out of this airport and all but the most complex areas w/ most settings on Ultra.  My guess is perhaps because of internal changes that happened over the past few WU things are just no longer the same in some basic rendering ways.  The silver lining is even w/ settings turned down image quality is still very good, and I can fine tune more as I go, which is reasonable.  Perhaps HIGH settings now are actually a little better than they were before, i.e. the quality scale has shifted to the right slightly.  I'll be glad if even this holds up because at least I can use the thing!

Thanks for your help Gazz

No problem, for what it's worth got a chance to run it again and without the FPS overlay and recording there were no artifacts. Frame rate was also slightly better which may be a combination of not recording (obviously) - but also I guess the area would have got cached the first time as I had never flown there before ... !

 

G