In the MSFS 2024 SU2 beta (1.4.7.0), aircraft (such as the Fenix A320) with light .fx that define textures in the texture entry, appear to cause the sim to crash if those textures do not use mip maps.
I’m not sure what the relevance to location is, but I did try it at a couple different airports, and it didn’t happen at all of them, but the ones in particular that it did happen at were 100% every time. TNCS is one of them.
Also important - it only happens when the aircraft was already selected when the sim first loads in on the main menu.
This seems to be reproducible with the following steps:
Launch the sim and select the aircraft
Load a flight and spawn
End the flight and return to the main menu (to hopefully guarantee that the active aircraft will be the same on next sim boot)
Close the sim and restart it.
With the aircraft already selected in the main menu, spawn on the runway at TNCS
The game should now crash while the top-down loading screen is being shown.
Attached is a simple test project/package that can be used to trigger the crash: EffectsCrash.zip (269.5 KB)
Additionally, enabling mip maps on these textures causes a massive degredation in resolution/quality of the effect textures. An example:
I can confirm this. When removing the texture from an effect on our plane, the CTD on loading does not occur anymore. Before, I was completely unable to start a flight.
Good find!
@FlyingRaccoon Sorry for the tag, just want to make sure this gets seen, as it’s pretty critical, and the only solution found so far significantly hurts visuals.
The same package I provided in my first post for the CTD demonstration will also have the mip map issue if you remove the +NOMIPMAP flag from Texture.png.xml located in SimObjects\Airplanes\EffectsCrash\common\effects\texture\.
