5 hours ago, DAD said:

How do I do this? Is that a new setting option?

Activate developer mode. In the Debug section the second from the bottom. Should be ticked to work.

16 hours ago, DAD said:

May then need to be adapted to the new LOD SDK before changes apply and we see an improvement? But no development knowledge here, so maybe Flic1 can shed some light on this 

I am certainly no expert on the subject and the math behind it, but I did do a deep dive into learning how to implement LOD's over the last 8 months while working on a freeware airport for 2024 (W29).  The new 2024 SDK enforces these new LOD's rules whereas 2020 did not (although there were recommended LOD suggestions in the SDK docs).  So an airport made natively and compiled for 2024 such as the one I did, will have them strictly enforced so I had to spend a decent amount of time making them so that you would not notice the changes when going from one LOD to the next (I used 3-4 LOD levels on my objects). 

The biggest issue I think was the fact the last LOD (lowest detail) had to be less than 150 vertices.  This was hard to do and you literally have just a shell. Once below that 150 limit is when the entire building disappears.  There were also issues with extremely detailed buildings up close (detailed terminals,interiors, A/C instruments etc) but my airport did not have anything super-detailed like that but I know that was an issues for many other Devs.  Since I did my LOD's to accommodate the 'old curve', when I go in and test the airport now on the latest Beta update, I can definitely see the difference as the buildings are still there while very far out when before I could see when they disappeared as well as some of the LOD changes in-between.  So, a natively built airport for 2024 should show improvement for sure with this change. If a developer built an airport in the 2020 SDK and imported it to 2024 (and not actually compiled in 2024 SDK), the objects will not abide by the new rules anyway and the buildings will likely not be popping in/out.  If that airport was converted to a native 2024 version, unless they did a really great job on the LOD's initially for 2020 or totally rebuilt their models, the objects would then be disappearing pretty close to you.  This is probably why there are so few "Native 2024" airports, many are still building them in 2020 and simply placing them in 2024 since you could get around the strict LOD rules (but missing out on new 2024 SDK features).

I won't mention names, but there is one developer that Asobo uses for their bespoke airports and many of the airports have poorly done LOD's and they also place large invisible cubes around their objects to get around the LOD recommendations.  So any airport you see that is both 2020/2024 compatible means it was ported into 2024 and does not have to follow the rules so may have poor performance if the dev did not pay attention to LOD's.  Only a natively built 2024 airport would follow them and that is where the Dev needs to be very good at doing LOD's.  So in theory, a natively built 2024 airport should perform much better than an airport that is "2024 compatible" but was compiled in the 2020 SDK.

One way to test is if anyone owns one of the 'Premium' IniBuilds airports such as EGLL (I don't have any of these) that are 2024 native.  If you noticed a lot of popping in/out of objects on those airports before, my guess is that it should be much less of an issue on the latest Beta update.

Edited July 3, 2025Jul 3 by Flic1

54 minutes ago, Vitold69 said:

Activate developer mode. In the Debug section the second from the bottom. Should be ticked to work.

You don't need to do this on the latest Beta.  That was for developers to use and test when placing their 3d objects in Dev mode.  The new system may or may be noticeable because it still depends on how efficient the developer was when implementing the LOD's on their 3d objects.

29 minutes ago, Flic1 said:

So in theory, a natively built 2024 airport should perform much better than an airport that is "2024 compatible" but was compiled in the 2020 SDK.

Let’s assume Frankfurt is not a native 2024 airport then. 

In the middle of my flight from Amsterdam to Toulon.

On the ground here and there small stuiters but I am using FT Amsterdam Schiphol.

In the air all smooth. Clouds look better and the ground textures are very sharp.

Will see how the landing goed within an hour.

( AutoFPS + PSXT live Traffic ) 

Edited July 3, 2025Jul 3 by GSalden

4 hours ago, abrams_tank said:

Do you have Dynamic Settings on?  Dynamic Settings is MSFS 2024's version of dynamic FPS, or Auto FPS.  Turn off Dynamic Settings to improve your ground textures, but it can lead to more stutters, that's the trade off.  If you get stutters after you turned Dynamic Settings off, then your graphics settings are too high and you need to lower them.

I don't know if you know this, but since the release of FS24 there are settings that don't do anything, whether ON or OFF. The problems are completely random! The solution is at  Asobo / Microft, There will be no mirale. I fly all day and believe me when you fly a lot it's frustrating to see so many defects. Thank anyway.

3 hours ago, Piotr007 said:

I know, still my fav in SU2 it works great.

There are a lot of bugs. Fenix is in Experimental version.I fly 40/50 hours per week with. Between the FS20 and FS24 versions it's day and night.

45 minutes ago, Ianrivaldosmith said:

Let’s assume Frankfurt is not a native 2024 airport then. 

I am actually not sure. If you are seeing a lot LOD popping, it is possible that the airport was compiled for 2024 without doing much work on adjusting the objects to comply with the 2024 LOD rules.  That would definitely cause those issues.  I would think if it was still the 2020 version being used, you would actually NOT see as much LOD popping (but possibly bad performance).  I have not checked out the default EDDF, I'll have to take a look at it....

Edited July 3, 2025Jul 3 by Flic1

I doubted Asobo. I was wrong. 2024 with SU3 is unbelievably good. 

3 hours ago, Vitold69 said:

Activate developer mode. In the Debug section the second from the bottom. Should be ticked to work.

Hi,

After enabling it, can I exit dev mode or I have to stay in order to work?

Greetings

 

Edited July 3, 2025Jul 3 by John Fields

Hi,

Sorry for the last post.

The new LOD curve is activated by default!

Greetings

 

1 hour ago, jarmstro said:

2024 with SU3 is unbelievably good. 

Ok, if YOU are saying this, I am truly excited to see the result. I sat this beta out cause I'm enjoying career mode a lot and didn't want to pause my progress, but now I want SU3 to release soon 🙂

2 hours ago, Ianrivaldosmith said:

Let’s assume Frankfurt is not a native 2024 airport then. 

It is, Gaya just seems to have not done great work on it.

Jorg has said the last couple dev streams that Gays is currently working on optimizing the LODs on all the handcrafted airports 

28 minutes ago, JonathanC said:

Ok, if YOU are saying this, I am truly excited to see the result. I sat this beta out cause I'm enjoying career mode a lot and didn't want to pause my progress, but now I want SU3 to release soon 🙂

I don't know about career mode or any of the gamey stuff but as a non serious flight simmer flying about from A to B  2024 SU3 is now the best experience that I've ever had. NVidia and Intel aren't going to be happy because I now have no need to upgrade from my 4070 and 13700. The only thing I've noticed is that the AI traffic goes a bit squirrely at times. 

Edited July 3, 2025Jul 3 by jarmstro

2 hours ago, filou said:

I don't know if you know this, but since the release of FS24 there are settings that don't do anything, whether ON or OFF. The problems are completely random! The solution is at  Asobo / Microft, There will be no mirale. I fly all day and believe me when you fly a lot it's frustrating to see so many defects. Thank anyway.

Turning off dymamic settings works for me. I have tried it already. It fixed the blurry terrain tiles for me.