Context: After loading in sim and looking at a particular object, it crashes with S_OK (does not crash in menu, nor while loading)
Similar MSFS 2020 issue: N/A
Bug description: When looking at the interior cabin of the aircraft, MSFS2024 hangs and the entire computer locks up for 5 seconds before crashing with S_OK. When the cabin is taken out, the sim does not crash.
Interestingly, when using the legacy MSFS2020 version of our project, the sim does not crash despite using the exact same high poly 3D model.
When I take the GLTF model from our 2020 project source, and paste it into our 2024 project source and build it with the 2024 package builder, it also crashes with S_OK when looked at in sim. The only configuration where this cabin works and does not crash the sim is when using the legacy 2020 project.
This has been tested on two different systems but with NVIDIA 30-class cards (3080 and 3090). Neither VRAM, RAM, CPU, or GPU is overheating/overfilling. Tested on Windows 11 24H2, with NVIDIA driver 591.44 and 566.36.
Repro steps: Launch sim, select the freighter variant (do not select the low poly variants). Once loaded, move camera towards the back (towards the cabin area) and observe PC lockup and sim crash with S_OK.
Attachments:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
your’e trying to compile a gltf in the 2024 sdk that was exported with a 2020 blender/3dsmax plugin?
you may need to export from the modeling app with the appropriate 2024 plugin
I tried compiling a max file exported with MSFS2024’s native SDK as well as using MSFS2020’s SDK, both crashed the sim with S_OK when using a native MSFS2024 project. It does not crash when using legacy 2020 projects compiled with 2020’s package builder, however.
The model exported with 2020’s SDK was only used to see if it was something wrong/new in the 2024 GLTF format. However, neither of them worked correctly, indicating something is wrong with the package builder or the engine as legacy 2020 projects compiled with the 2020 package builder ran fine without crashing in MSFS2024 with the same exact 3d models.
if your working on moving an aircraft project from 2020 to native 2024 then you should not even be touching the 2020 sdk or plugin, doing so can ruin the model
even saving the model once with the wrong plugin can bork everything - these games are Not interchangeable like that afaik
you want to go back to the original Model Source not the Custom Exported gltf
so the original blend or 3ds files from Before using either of the plugins
failing that, you may need to clean all that custom texture data out completely, if you have no early model save its a lot more work in my experience
having said all of that, im working with blender so … idk
sorry your having trouble, i hope you get it sorted
Thank you for your input; yes, we have exported it natively from Max with the 2024 tools and it exhibits the same behavior. The mention of attempts with the 2020 version was to demonstrate that the geometry of the model itself is not the problem.
I use a separate VM instance for exporting 2020 builds, however unlike blender the 3dsmax plug-in is not as sensitive; they both can be installed at the same time (it is in their SDK docs). In any case, neither configuration works. Blender and 3dsmax are using two different exporters, so I cannot expect your experience to work here unfortunately.
nice,
they can both be installed into the same instance of blender as well
they are just not supposed to be enabled at the same time
its not about exp, i was just suggesting that the exporter may not be to blame
if this is an integral issue others will chime in i hope
in blender the plugin can become corrupt as well, this needs a clean-out of the plugin saved settings stuff (in the user folder) - but im not sure that is the same for you
My initial post mentions it only crashes with the freighter variant in the repro steps section (NOT ANY OF THE LOW POLY VARIANTS EITHER). The passenger variants does not suffer from this. Please check this.
While we investigate the issue, as a workaround, you can disable the “Raytraced Shadows” option in the graphic settings (under Global Rendering Quality). You should no longer crash.
