Context: Scenery Package, happens when editing and when mounted.
Bug description: I have seen that the LOD system has changed, including the hability to change LOD on the editor, however, I am having trouble with some smaller sized objects disappearing way too soon, and I have found no LOD % that could change that. The light pole in my airport disappears at about 9% screen size no matter that I put on the LOD numbers. I even tried smaller than 1 values (0.3 for LOD 0, 0.2 for LOD 1 and 0.1 for LOD 2) and not even that prevents the object from disappearing - This issue is also happening with both my custom jetways.
Repro steps:
Small objects with LOD - the object has not been re-exported for 2024, editing a package from 2020.
LOD logic appears to be way too aggressive. Objects are disappearing at close range. This is also happening with in-sim fs-base objects also for example the āGrizzly Bearā
Am i the only one not seeing any changes made in the scenery editor i make until i build the project. Then if i want to see any modification after that i have to build again?
I understand the need for a strict LOD policy, but it does make a mockery of the limits set when the base game assets are so badly optimised that they can disappear from just meters away.
Here is Terrace_Table01_A, where the legs go invisible when standing next to it:
@EPellissier is it not correct to assume an scenery made inside MSFS 2020 should continue to apply the LODs rules from MSFS 2020? like you mentioned in the QA it happens with aircraft?
Looks like all sceneries from MSFS 2020 are now being enforced into the MSFS 2024 new LOD system which of course will make most of the objects get culled at shorted distances.
Most scenery developers will be converting slowly towards MSFS 2024, but is a long time to re-do all the LODs, nobody has access to Simplygon at 35K USD per year, is not affordable and most scenery devs perform their LODs with tools that are not as fast and efficient as Simplygon via the āAutoLODā setting.
So perhaps giving time to scenery developers to adapt to the new LOD setting when they compile inside MSFS 2024 could be considered? just like it occurs to aircraft?
The MSFS 2020 LOD rules are applied as long as the object comes from an MSFS 2020 package (SimObject, BGL) - unless you have just discovered a bug. If you create an MSFS 2024 package with the same assets used for MSFS 2020, the MSFS 2024 rules will apply.
To cut a long story short: porting an MSFS 2020 package to MSFS 2024 may indeed require to redo several LODs.
Perfect, thank you for clarifying, so in this case we are having packages from 2020 (sceneries) with the objects being culled more aggressive such as if the new rules are in placeā¦
Hello, I desperately need some clarification. So all my airports are the community folder. I have issue with terraforming on many which is likely due to the new DEM in the new sim, this would require me to rebuild the packages in the Fs24 SDK so i can fix the terraforming issues.
However Iām having other issues like the blender addon not exporting the Xml file name for objects, so i have to name them individually myself.
Then when i do get them in the FS24 Scenery editor, the elevations of some objects are fine but after i compile and load back in to see how it looks, the object is about 3 feet lower then it was set to in the Scenery editor.
While Iām there, Iām trying to implement other new features such as the passengers. They donāt always appear, i get the red place holder man for some, while others simply donāt show up.
Then there is the HUGE issue of grass. Most airports have short grass like it was in Fs20, now there is tall grass with no way to change the height. If i change the biome I may find one that has shorter grass, but it adds plenty sticks and shrubs that i canāt remove or control. We need more control for these Biomes and grass materials.
Are these oversights?, or are they just not implemented in the build we have? Is this dev alpha meant for us to fix our Products for Release, or is it just for Asobo to make old FS20 projects look the best they can and then after release weāll have all the necessary tools and Parameters in the full releases build to really get our airport to look how we want them to look. Because as it stands even if the bone animations were to start working, with the current sdk in hand, I canāt get my airfield to look even remotely accurate in terms of the ground and vegetation.
Turning off Displacement Mapping fixes all the terraforming issues.
In another thread Asobo said theyāre looking into allowing us to control displacement mapping with polygons.
When reporting LOD issues found when using a specific package, please create a new bug report rather than adding to the list here - this topic lists problems that may be unrelated to each other (even if it looks like they are) and it will make tracking (and reporting) difficult in our bug database.
