As for LODs, if you share a lot of items between sites you could make a library in 2020 to place in 2024 sceneries. And if you share a lot of the same textures it might be worth doing the same for your buildings even if they're all different. 

Or a 2020 model library for each individual site and split the 2024 download into that and its scenery file. It's a kludge that should last for a few years to come. 

That's what I'll try first as I may not have plenty of source files any more. Or the time and inclination. 

Considering the amount of grind going native sounds, I'd only do it if it was absolutely necessary. So far I have one set of animated hangar doors that don't work properly in 2024 and that appears to be the only problem. 

All of my libraries seem to work fine in 2024, apart from landing on moving boats which needs a small tweak, so I've zero intention of changing any of those to 2024. It's so much work it would never happen anyway. 

The new LODs are for Xbox users mainly who will never sample my unsettling touch. 

Edited November 26, 20241 yr by superspud

8 hours ago, martinboehme said:

Have you tried simply using Blender's "decimate" modifier? The results often look pretty horrific in Blender, but in the sim, when displayed at the distance that the LOD is actually active at, it often doesn't look bad at all.

I actually have not.  I will go in and see what I can do with it!  Thanks!

11 hours ago, Dusk said:

You might find this interesting. He is going to cover LOD in next video.

MSFS 2024 SDK Tutorial: How to (NOT) convert a 2020 project to 2024

Thanks -- great video!

In essence: Don't convert the MSFS 2020 project to an MSFS 2024 project; instead, keep the project in 2020, check for problems in 2024, then fix those problems in 2020. This sidesteps the problem of having to conform to the 2024 LOD rules. (@vbazillio I hope my post hasn't already lured you into LODding odyssey...)

The downside is not being able to use 2024 stock assets, but...

9 hours ago, superspud said:

As for LODs, if you share a lot of items between sites you could make a library in 2020 to place in 2024 sceneries. And if you share a lot of the same textures it might be worth doing the same for your buildings even if they're all different. 

Or a 2020 model library for each individual site and split the 2024 download into that and its scenery file. It's a kludge that should last for a few years to come.

Took me a while to process this -- but then it clicked. Keeping the models in a 2020 project means they aren't subject to the new LOD rules. Making the scenery itself a 2024 project means it can use all of the new assets, and it makes it much easier to make the scenery fit into the 2024 base world (terraforming, exclusions, etc.).

The best of both worlds. Genius! 👍

39 minutes ago, martinboehme said:

Took me a while to process this -- but then it clicked. Keeping the models in a 2020 project means they aren't subject to the new LOD rules. Making the scenery itself a 2024 project means it can use all of the new assets, and it makes it much easier to make the scenery fit into the 2024 base world (terraforming, exclusions, etc.).

Just done this here - https://flightsim.to/file/16991/edxh-duene-airport-helgoland-upgrade

Copied the 2020 project. Stripped out everything except the scenery file, opened in 2024 and made the required edits.

Copied it again. Ripped out the scenery file and used everything else from 2020 in 2024.

One thing you will need to do is adjust whatever LOD settings you have in the 2020 model xmls by checking them in 24. 24 brings them in a lot sooner.

Get the right number. Compile in 2020, upload as two separate files and you should be good to go.

That makes a full 2024 conversion maybe 30 minutes to a couple of hours rather than the rest of your life.

Maybe the model rules will change but it buys plenty of time until then.

Edited November 26, 20241 yr by superspud

Awesome discussion feed by so valuable participants. Thank you all!

9 hours ago, martinboehme said:

check for problems in 2024, then fix those problems in 2020. This sidesteps the problem of having to conform to the 2024 LOD rules. (@vbazillio I hope my post hasn't already lured you into LODding odyssey...)

The downside is not being able to use 2024 stock assets, but...

Great strategy. Exactly what I expect when starting this discussion.

I’m still undecided. There’s also another path. Maybe more ambitious and long term focused. I need to skill up on MSFS dev and MSFS2024 could be the perfect opportunity. I can consider my MSFS2020 sceneries done. Anyone who want to stick with MSFS2020 can enjoy my amateur work. No offense. And maybe now, should I upgrade them. Focus on MSF2024. Finally make my small objects closest to state-of-the-art (a.k.a LoD SDK rules), considering some library architecture, benefiting from the new MSFS2024 biomes, and so on.

I’m still processing all your input. Not decided yet but again thank you to all participants of this discussion.

Follow up. His next one will be about application of LODs apparently.