4 minutes ago, IndustrialEngineer said:

Huge thanks for putting effort on this!

Your video looks so nice, if I could fly that too!

After looking that video, im pretty sure I didnt use to have these pop ins I now have🧐

If you've not already done this it might be worth a try, especially since you're thinking this has not always been the case for you:  do fresh new install of Windows, install all chipset, audio, GPU drivers, then a reinstall of 2020.  DO NOT install Lossless Scaling or any other adjuncts.  Just run MSFS 2020 straight up as if it were a virgin install, keeping the native rate at 30FPS.  And then you might also try my method of frame locking which I used in 2020 and continue so in 2024:  
 

 

Let me know when you eliminate the popping… 

1 hour ago, Noel said:

Clearly exceeded this PC's processing power to create a smooth video during a runtime fly-in to KJFK but you won't see any pop-ins, or ultra few if you do.  This was done at 1500' AGL at around 270kt and if that doesn't tease out pop ins it's pretty clear it's a non-issue here.  

 

Why would you think that?   What we both agree on--there is a reason why some experience this severely like you apparently, why some experience this very intermittently and as Sonosusto reports, only in very high demand scenarios, and why some like myself rarely experience this anywhere.  All of my commentary here has to do w/ 2024 SU2 as I stopped using 2020 several months ago now.  But just as Bobsk8 reported--I didn't have significant pop in of scenery objects in 2020 either.

 

 

 

 

 

The results and the whole thing seems mystery. I will take proper video in tomorrow  morning about the issue, if we can get clearer picture.

47 minutes ago, Noel said:

If you've not already done this it might be worth a try, especially since you're thinking this has not always been the case for you:  do fresh new install of Windows, install all chipset, audio, GPU drivers, then a reinstall of 2020.  DO NOT install Lossless Scaling or any other adjuncts.  Just run MSFS 2020 straight up as if it were a virgin install, keeping the native rate at 30FPS.  And then you might also try my method of frame locking which I used in 2020 and continue so in 2024:  
 

 

Ok, will try that first thing in tomorrow morning, thanks!!! I have Windows 10 pro btw, I dont think it matters though. 

1 minute ago, IndustrialEngineer said:

Ok, will try that first thing in tomorrow morning, thanks!!! I have Windows 10 pro btw, I dont think it matters though. 

It's a big hassle to start fresh*** but again if your recollection of not seeing pop-in behavior previously is true, and you do the complete clean install of everything, w/o add-ons initially to see if the pop-in issue improves or disappears, you may well have a good chance of resolving this, I hope so.  You mentioned you have a stable 100mbps internet connection.  Is it possible other devices are impinging on that such that you do not actually have 100mbps to dedicate to MSFS?

***I routinely do this annually, spring cleaning.  Now w/ 2024 it's much quicker than it used to be.  But yes, I wipe the drive and start completely afresh.  And I'm one of the folks here who often chimes in to report I have ongoing excellence in performance, in graphics, etc.  Right now 2024 is running super smooth everywhere it's just flat out remarkable.  I'm blessed w/ good hardware thankfully.

14 hours ago, LRBS said:

A big disappointment is that, due to ASOBO's poor programming, people are fighting instead of uniting to pressure them and demand that they fix what is obvious and acknowledged by many. 

IMO, this is wishful thinking.  IMO Asobo knows full well about all of the issues you're complaining about.  I think it's end-user hubris to actually believe you're going to move their approach to development by what, "putting pressure on them"?  How?  Class action lawsuit?  Leaving MSFS en masse *might* actually have some impact hard to say.   Nor do I agree in the slightest that 'this is hugely unstable software....'  Why do I say that?  Well, you know why:  I use 2024 with 3rd party adjuncts like SLC, BATC, GSX, multiple high end planes and remarkably, all have worked very well to perfectly since I installed 2024 3 or 4 months ago.  Same same w/ 2020 before it for over four years.  Same same with Win 10, now with Win 11.  So no, 'hugely unstable software' could not possibly deliver what it does, over and over.  I'm also hardly alone in this.   Absolutely, MSFS 2020/24 are ultra complex software needing to interact with a huge array of outside content.  Therein lies the challenge for MS/A, and all end users.

Yeah, with my batc traffic set to '5' and enroute traffic set to '6' and my tlod at 65 it was no wonder why performance had some stutters on landing. Little pop ins, though.

I think limiting TLOD to 40 under 1000 agl using dynamic lod might be a good choice at big airports with tons of traffic. The sim is loading dozens of planes, dozens or more cars/trucks and the scenery at the same time.

Solution: reduce all traffic by half, tlod with autofps to 40 below 1200-1700 agl. 

I also realized I had my monitor set to 120hz (gsync) when I have capped the sim cfg to 50. I figured capping the the monitor to 100hz would be better. Maybe limit to 40fps through cfg file and set my monitor for something lower than 100fps? Frame generation can take care of the rest, i assume. It would give more cpu head room

Thoughts?

Edited August 9, 2025Aug 9 by Sonosusto

23 minutes ago, Sonosusto said:

Thoughts?

Yes, you've all gone back to the FSX days of ludicrous tweaking, that most of the user base have no idea the settings that they are changing, or what they are actually doing. All of this to fix Asobo's issues. Most of which should not be needed, especially since half of it is snake oil. And those with top systems (5090 etc) should have the sim set and forget by now. And actually just fly.  But oh no, got to keep chasing stupid external tweaks to stop taxi signs popping in, and get AI aircraft working as was advertised... using tools that hack in to MSFS and are actually banned discussing over the official msfs forums. Again, I reiterate, the sim for me is a mess. For others they are happy. 

Edited August 9, 2025Aug 9 by Ianrivaldosmith

1 hour ago, Noel said:

It's a big hassle to start fresh*** but again if your recollection of not seeing pop-in behavior previously is true, and you do the complete clean install of everything, w/o add-ons initially to see if the pop-in issue improves or disappears, you may well have a good chance of resolving this, I hope so.  You mentioned you have a stable 100mbps internet connection.  Is it possible other devices are impinging on that such that you do not actually have 100mbps to dedicate to MSFS?

***I routinely do this annually, spring cleaning.  Now w/ 2024 it's much quicker than it used to be.  But yes, I wipe the drive and start completely afresh.  And I'm one of the folks here who often chimes in to report I have ongoing excellence in performance, in graphics, etc.  Right now 2024 is running super smooth everywhere it's just flat out remarkable.  I'm blessed w/ good hardware thankfully.

Yes my internet is all good and giving good numbers. 

About the formating the PC, as you do it often, I have read somewhere that you can acticate pmdg products only two times in different pc. So I guess its going to use the second time of activation when I reset the whole system? Or how it works as you have been reseting every year?

 

It could be also that I havent noticed the pop ins as I have been focusing so much on approach and everything in the cockpit, but idk🧐

Edited August 9, 2025Aug 9 by IndustrialEngineer

1 hour ago, Sonosusto said:

Yeah, with my batc traffic set to '5' and enroute traffic set to '6' and my tlod at 65 it was no wonder why performance had some stutters on landing. Little pop ins, though.

I think limiting TLOD to 40 under 1000 agl using dynamic lod might be a good choice at big airports with tons of traffic. The sim is loading dozens of planes, dozens or more cars/trucks and the scenery at the same time.

Solution: reduce all traffic by half, tlod with autofps to 40 below 1200-1700 agl. 

I also realized I had my monitor set to 120hz (gsync) when I have capped the sim cfg to 50. I figured capping the the monitor to 100hz would be better. Maybe limit to 40fps through cfg file and set my monitor for something lower than 100fps? Frame generation can take care of the rest, i assume. It would give more cpu head room

Thoughts?

Do you have the pop ins?

56 minutes ago, IndustrialEngineer said:

About the formating the PC, as you do it often, I have read somewhere that you can acticate pmdg products only two times in different pc. So I guess its going to use the second time of activation when I reset the whole system? Or how it works as you have been reseting every year?

I would hold off on reinstalling Windows... It is unlikely to help you, and just creates a lot of work and hassle.  If you like tinkering, go ahead, but if not, simply do not do it.  😊

For the record, my 2024 runs really smoothly at 60 fps on a 1080p screen and a 4070tiS GPU.  However, I also get popping taxi way signs at airports and do my best to ignore them..   

50 minutes ago, IndustrialEngineer said:

It could be also that I havent noticed the pop ins as I have been focusing so much on approach and everything in the cockpit, but idk🧐

If you do the complete new install of everything to MSFS 2020 virgin new install state w/ no 3rd party anything added, you will get the most valid affirmation about how vanilla MSFS 2020 will run with respect to the pop-in concern.  If it turns out pop-ins continue essentially unchanged you can definitively conclude your hardware with its OS, drivers etc along with your net connection is simply unable to run the sim w/o pop-ins, and perhaps Asobo will steal something from somewhere to compensate for whatever it takes to avoid pop-ins if indeed that is what is at play.  I'm glad it's a non-issue for anyone w/ at least an identical system configuration that I have.  Maybe RTSS plays a role in it.  RTSS is a sort of post-processing frame limiter and perhaps that means ALL of the intended frames are produced encompassing the surrounding all scenery objects and textures, whereas another form of frame lock earlier in the stream end up interfering w/ a few remaining objects in the rendering pathway. 

1 hour ago, Ianrivaldosmith said:

 Again, I reiterate, the sim for me is a mess. For others they are happy. 

Thanks for letting us know this Ian.

Appreciate it🫡

1 hour ago, Ianrivaldosmith said:

Yes, you've all gone back to the FSX days of ludicrous tweaking, that most of the user base have no idea the settings that they are changing, or what they are actually doing. All of this to fix Asobo's issues. Most of which should not be needed, especially since half of it is snake oil. And those with top systems (5090 etc) should have the sim set and forget by now. And actually just fly.  But oh no, got to keep chasing stupid external tweaks to stop taxi signs popping in, and get AI aircraft working as was advertised... using tools that hack in to MSFS and are actually banned discussing over the official msfs forums. Again, I reiterate, the sim for me is a mess. For others they are happy. 

You've pretty much said it..  It is a personal choice..  If popping taxi way signs and misbehaving AI aircraft means the sim is a mess, it is just that, at present.  If that is not on your personal radar, it is a lot of fun to fly.. 🙂

10 minutes ago, Noel said:

Maybe RTSS plays a role in it.

I kind of doubt it...  Asobo decided to change the LOD rules a few system updates back, in order to improve performance and save memory, and objects that do not neatly fit into that design, pop in in a noticeable way.  Taxi way signs are the most obvious example..

I suspect that if someone would redesign all the taxi way signs with multiple LOD levels, they would behave differently.

Edited August 9, 2025Aug 9 by Bert Pieke