Take a read : https://forums.flightsimulator.com/t/intriguing-discovery-76t-bad-fps-areas-geometrically-linked-to-class-b-boundaries/382538/7

 

This is interesting read. Whenever your aircraft enter Class Bravo zone, the FPS drops....

That's an amazing bit of investtigation, let's hope it helps ASOBO in one way or other!

If it is then it's one of the several issues. It doesn't explain the extremely low frame rates in the main menu, or maybe the Manipulators stutters since 1.3.16.0.

Though it is great that some people are willing to make such painstaking investigations and write detailed reports. Hopefully it will help Asobo fix this fast.

Wow, that´some amazing detective skills there. Kudos.

Wow that is some brilliant analysis.  Sign him up Asobo!

It’s plausible that both times i experienced the issue i was on the edge of mode C airspace.  One was in between Teterboro and Bridgeport, the other was just before entering San Francisco Bay Area mode c airspace on approach to SFO.  I don’t remember enough specifics about where the issue started and stopped in both cases but it’s definitely something I’ll keep an eye on going forward.

Let's vote that thread until our LMB breaks

What a load of tosh, I thought when I read the first post, but having read the whole thread on the OS, I can see the rationale behind it and the theory does seem to have some legs.  Quite a surprising, interesting and informative read.

Oh, it has legs and it bears out. Do you own research in your own area of interest. (i.e; where you fly)

I fly predominantly in the south of England and I've confirmed that both the Farnborough EGLF and Pompey Stuttering at EGHF are both due to the proximites of Heathrow and Southampton CTAs respectively so I've nothing to dispute his findings so far.

Clever guy. Kudos - as they say.

Now, how about a fix?

Is it as simple as disabling ATC - which will hit our Tube Jockeys hard? (unless they're on Vatsim - which they should be!)

 

Edited March 23, 20215 yr by Will Fly For Cheese

2 hours ago, ChaoticBeauty said:

If it is then it's one of the several issues. It doesn't explain the extremely low frame rates in the main menu, or maybe the Manipulators stutters since 1.3.16.0.

Though it is great that some people are willing to make such painstaking investigations and write detailed reports. Hopefully it will help Asobo fix this fast.

I read somewhere that main menues are Class B in general.

Taking off from KFHR (Friday Harbor, San Juan Island, Washington State) on heading of 120° M - my FPS is 29 - 32 (75% CPU, 99% GPU) until SE of Cattle Pass and then drops to 14 - 16 with 99% CPU and 40% GPU.   Over water with NO controlled airspace of any kind within 10-miles.    

I spend about 90% of my flying time in the KSEA Class B airspace, flying into and out of it.  I never experience the FPS drop / high CPU & low GPU utilization while doing so.

Class B may explain some of the problems but not the one I test against. 

Edited March 23, 20215 yr by TacomaSailor

AMAZING FInd. I can confirm.

 

Here is my CPU Thrashing as I enter the dark zone of low FPS coming in from the East inside DFW Class Bravo into Decator

And then look at my CPU as I leave the decator dark zone into DFW Bravo space again.

Edited March 23, 20215 yr by Manny

Amazing!  The guy really put some work into this.  I still think there are a few other issues as well as this, but curing this would be a major win.

I am going to test to see if my 'manipulators' issue that cuts GPU to zero around Salzburg is related to this.

I see a bunch of people are flying around Decator. in the sim. I have flown here often in real life. There used to be a  big dig right at the end of the north end of runway.. a Massive hole. Approaching from the north to land would give you an illusion you are way too high to land... cause of the massive dig. Each airport/Rwy has its own story.

Asobo should hire the person that figured this out. 

12 minutes ago, Bobsk8 said:

Asobo should hire the person that figured this out. 

Often the community is better adept than Asobo at resolving Asobo's problems.