CTD on flight restart when subscribed to all InputEvents via SubscribeInputEvent(0)

Version: Flighting SU13 -

Frequency: Consistently

Severity: High

Context: External SimConnect client, managed code

Bug description:

When being subscribed to all inputevents via SubscribeInputEvent(0) the sim will CTD when restarting a flight.
The sim sends following sequence of events:

`Entering ESC-Screen
SystemEvent: 4 Paused 0
SystemEvent: 4 Pause 1
SystemEvent: 4 Pause_EX1 8

Confirming Restart
SystemEvent: 4 SimStop 0
SystemEvent: 4 Sim 0
SystemEvent: 4 Paused 0
SystemEvent: 4 Pause 1
SystemEvent: 4 Pause_EX1 1
SystemEvent: 4 View 0
SystemEvent: 4 PositionChanged 0

Next “EventFrame” sim will crash

Calling UnsubscribeInputEvent(0) upon SimStop-event does not prevent the crash.


Confirming this issue as well. To reproduce:

  1. Spawn a plane at an airport
  2. Register to get all events via SubscribeInputEvent(0)
  3. Press Escape
  4. Select Return to Main Menu

Eventually the sim will CTD:

Faulting application name: FlightSimulator.exe, version:, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001de4f10
Faulting process id: 0x0x9E60
Faulting application start time: 0x0x1D9FA19202BEBA4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 7dd1c35c-7f06-466f-ab78-1479c905abb1
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

1 Like

Hello @c0nnex and @neile,

We have managed to reproduce the crash.

We are investigating and will keep you updated as we have more information.

Thanks for your report,


1 Like

Hi Alexandre,

did some additional investigation on this. If I unsubscribe from the Inputevents upon receiving a PAUSE_EX1 (8) the sim does not CTD.


1 Like


I can also reproduce a CTD by subscribing to just any one specific Input Event (by hash ID) and then switching airplane models.

For example:

  1. Select the stock Icon model in World Map and go back to home/main menu.
  2. Subscribe to HANDLING_ElevatorTrim_1 event, which for me is SubscribeInputEvent(18030404428114905164)
  3. Change airplanes to VL3 in World Map and go back to Home.
  4. If it doesn’t crash right away, go back and repeat step 3 but changing back to the Icon.
  5. The most times I’ve had to repeat this is 2… YMMV.

Exception info:
Unhandled exception at 0x00007FF71DDA4F10 (FlightSimulator.exe) in FlightSimulator.exe.27876.dmp: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

Note that the HANDLING_ElevatorTrim_1 has the same Hash ID in both models (as reported by EnumerateInputEvents()).

An even more reliable way to CTD, on first try every time for me:

Steps 1 and 2 as above.
3. Change to a model w/out elevator trim, eg. Cabri G2 heli, then ESC/Go Back.
4. Usually crashes before the home screen is even shown.

Exception info:
Unhandled exception at 0x00007FF71DDA4EE9 (FlightSimulator.exe) in FlightSimulator.exe.21840.dmp: 0xC0000005: Access violation reading location 0x00000162293D5554.

This is all with Dev Mode enabled, since that’s the only way to get the list of input events right now anyway.

@GentleLynx This seems to me like same or similar issue, but do let me know if you’d like me to start a separate thread. I have debug dumps if that would help anything.


PS. From what I can tell, the first indication that a new aircraft is being loaded when navigating the main menu is the AircraftLoaded system event. Calling UnsubscribeInputEvent(18030404428114905164) at this point (outside/async of ReceiveMessage() for the OnRecvEventFilename handler) leads to an immediate sim exception.

FWIW, in all the crash scenarios I mentioned, after the AircraftLoaded event I consistently get SimStop, Sim {0}, PositionChanged, and then the exception.

Confirmed this is fixed in SU14 beta, I was able to subscribe to input events, leave back to the main menu, and start a new flight without any crash.

1 Like

Hello neile,
Thank you for the feedback.
Indeed the fix is available in the current flighting SU14.