ISSUE DESCRIPTION
Description of the issue:
After the latest MSFS 2024 SU3 Beta update, 1.5.9.0, all of my previously working 3rd party sceneries are now overlapped by the included default airports. Nothing has changed in my community folder since my last flight on 1.5.8.0.
Also, to note, the default airports that do show up, are only partly shown up. The autogenerated buildings will show up, however ground markings, aprons and other objects will not. It is almost like the default and 3rd party sceneries are trying to fight for loading order.
Airports that have been created for FS2024 Native, and have the ‘Custom Airport’ tag in the package-reorder tool hint show up correctly, however ones for FS2020/FS2024 that have ‘invalid’ in the package order tool, show up incorrectly as described above.
Did you experience this issue before you joined the Beta?
No
ICAO, coordinates, or specific location:
Reproduceable at any airport.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No, as the issue only occurs with 3rd party airports.
FREQUENCY OF ISSUE
Every time when loading into a flight.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Load into MSFS 2024 SU3 Beta 1.5.9.0
- Attempt to load into an airport for which you have a 3rd party scenery installed (that does not have a package order hint from when it was created in the SDK.)
- Observe conflict between 3rd party airport expected to show, and default elements that appear.
[PC Only] Are you using Developer Mode or have you made any changes to it?
Yes, when troubleshooting and moving the 3rd party sceneries lower in the list, in the same section as those tagged ‘Custom Airport’, upon reloading the simulator, the airports show up as intended. This hints to there being an issue with package ordering in the current build.
MEDIA
Please add a screenshot or video of the issue occurring.
Screenshot of a Native FS2024 Airport, iniBuilds EGLL Premium. The airport shows up as intended, without altering the package re-order tool.
In the package order tool, it has the tag ‘Custom Airport’
Screenshot of iniBuilds EGGW, a 2020 built, but 2024 compatible scenery, which instead of having a ‘Custom Airport’ tag in the package order tool, doesn’t have one at all, and therefore shows ‘INVALID’. Note that the terrain mesh is all messed up, and the default autogenerated buildings show through, but the iniBuilds custom ground markings are present?
Upon moving the package order for EGGW further down, adjacent to the ‘Custom Airports’ in the tool, when reloading the sim, the scenery shows up correctly as intended, with the buildings showing from the iniBuilds scenery.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•