I was approaching BMWORLD's KSEA earlier today. I flew past on the downwind leg in the 787 (AAU2 version) and frames were absolutely fine.

However on approach at about 1000 ft, the frames dropped through the floor. Stutters everywhere and it was pretty much unflyable.

Once I got on the ground frames were fine. 

Has anyone else experienced this?

Ben

Maybe something to do with the interior rendering of terminals?  I'm not sure where this new obsession with interior terminal modelling came from (though I suspect the msfs drone cam had something to do with it).

I had this happen a couple times recently -- once landing at Cloudsurf WSSS and once with Asobo LFPG. It's doesn't happen consistently, but when it does, exactly as you said: normal performance on approach until about 1000 feet and then the FPS dropped dramatically (I wasn't running a counter but my eyeballed estimate is that it went from about 50 FPS to 20 in both cases). With WSSS it stayed that way until I ended the flight, with LFPG the FPS recovered after I was on the ground.

Both times this was a demanding area/airport with a lot of AI traffic, but I've flown into enough similar situations in the sim to know that something else seemed to be at work...something seemed to have gone wonky, somehow.

James

It’s most likely the AI ac and/or the Objects (LOD) that start being loaded are causing this.

You can test it by turning the amount of AI ac down and setting the Objects LOD slider to a lower setting.

 

 

Edited July 17, 20232 yr by GSalden

So this airport by BMWorld isn’t known for being a frame rate killer?

20 minutes ago, BWBriscoe said:

So this airport by BMWorld isn’t known for being a frame rate killer?

Seattle has plenty of parking spaces.Traffic has a big impact on FPS.. Without traffic, I have 52 FPS. Default KSEA 60 FPS. 8 fps difference. Not so much.

Edited July 17, 20232 yr by Flying-Hare

21 hours ago, ryanbatc said:

Maybe something to do with the interior rendering of terminals?

Multiple developers have said that the LODs in use mean their interiors won't display until your aircraft / viewpoint is close to the terminal buildings of their scenery.

Rather than the word not allowed ton of exterior details, huge texture sizes, AI aircraft, objects, and possibly bumping up against the VRAM limit of the GPU because of these, we're stuck thinking that interiors are the problem.

Funny how turning off interiors in some scenery makes very little difference to overall performance. Yet, we like to frighten ourselves with our favourite boogeyman scare story: "Detailed interiors... 😱"

Detailed interior should be an option.  It really has nothing to do with flying an airplane.  Waste of resources in my book.  What is next, lets go into people's home that show up around the airport.

The amount of polygons needed for a typical airport terminal interior pales in comparison to the amount needed for the exteriors, clutter on the apron, AI aircraft, etc, and is an even smaller fraction of the amount needed for photogrammetry.   If your machine can handle a typical PG city, terminal interiors are not the problem.

I don't understand why I can land at iniBuilds EGLL with full FSLTL traffic and have no issues but at BMWorld KSEA I have this issue?! Surely heathrow should affect my system a LOT more?!