CTD when Syncing Files in the Aircraft Editor with a Flight Loaded in the Sim

Using:
MSFS 1.37.19.0 (latest update as of 09/9/2024)
SDK 0.24.3 (last update)

Hello Microsoft/Asobo,

We are experiencing a new issue in Developer Mode similar to the ones reported in one of our previous posts (see below): MSFS crashes to desktop when syncing files in the Aircraft Editor when a flight is loaded, and the aircraft is - for example - on the runway.

This abnormal behavior seems to occur only when a flight/aircraft is loaded in the simulator in real time. Apparently, MSFS will not crash to desktop when syncing files in the Aircraft Editor from the main menu with a project open but with no flight/aircraft loaded in the sim.

Without certainty (it may or may not be related), we believe this started to occur after the last “mandatory update” of the simulator (sometime last week). We didn’t have this issue before and were able to sync files “in real time” in the Aircraft Editor with a flight/aircraft loaded in the simulator.

At first, we thought it was due to some changes we’ve made to our model behaviors and panel.cfg, so we reverted to our previous project iteration and still experienced the issue.

Then we thought it might have been a screen resolution or refresh rate issue because at some time we switched to a monitor with a higher resolution, and we remembered MSFS crashing in Developer Mode when using two monitors (previous post, see below). So, we reinstalled the old monitor and still had the same CTD issue when syncing files. We made our tests with only one monitor connected to the PC.

We then tested different screen resolutions and refresh rates in Windows (and NVIDIA control panel), to no avail. We also tested different resolutions in the Graphics options panel of MSFS.

We noticed that the files were updated correctly after clicking “Save” in the File dropdown menu of the Aircraft Editor. However, after clicking “Resync”, MSFS would always freeze and crash to desktop with no other explanations or error message.

This is very exasperating and it slows down our production: We now need to exit the flight to sync our files in the Aircraft Editor from the main menu, and then reload the flight to test the changes we just made in order to prevent MSFS from crashing to desktop. We didn’t have to do this before and could test our changes almost in real time - which was a great improvement and a blessing for developers over previous versions of the simulator.

(Our previous post on a similar issue: https://devsupport.flightsimulator.com/t/ctd-in-developer-mode/9562

Any idea on how this can be resolved and what might have gotten wrong?

Thank you,

Alain
Producer
Xtreme Prototypes Development Team
Montreal, Canada

SPECS:

Using MSFS v1.37.19.0, SDK 0.24.3.
Latest versions

Dell Alienware R15 AMD
AMD Ryzen 9 7900 12-Core Processor 3.70 GHz
Windows 11 Pro
NVIDIA GeForce RTX 4090

All drivers are up to date

Monitors tested:

Samsung Odyssey S49CG932SN
Multiple resolutions up to 5120 x 1440
120, 240 Hz

LG 38WK95C-W
Multiple resolutions up to 3840 x 1600
75 Hz

Dell S2721QS
Multiple resolutions up to 3840 x 2160
60 Hz

Quick Update: CTD Issue Seems Resolved

After reinstalling the new (ultrawide) monitor, rebooting the computer a few times, relaunching the simulator, and rebuilding the latest iteration of our project in Developer Mode, everything came back to normal. MSFS no longer crashes to desktop when syncing files in the Aircraft Editor while a flight/aircraft is loaded in the simulator.

We believe the issue was not related to our project and probably not to the latest “mandatory update” of the simulator. It might have been caused by installing a new monitor with a higher resolution and refresh rate. Except for the sim’s mandatory update and the new monitor, nothing else has changed in our setup.

I must emphasize that the CTD issue reported earlier occurred only when syncing files in the Aircraft Editor when in Developer Mode. Otherwise, we could fly the aircraft in or out of Developer Mode without issues.

We are suspecting a resolution-linked problem that may be similar to the CTD issue reported in our previous post when using multiple monitors with different resolutions when in Developer Mode:https://devsupport.flightsimulator.com/t/ctd-in-developer-mode/9562

Hope this helps.

Alain
Producer
Xtreme Prototypes Development Team
Montreal, Canada