Troubleshooting the SimConnect module
The module never connects, but the simulator is running
Cause. The installed package doesn’t match the running simulator - SimConnectMsfs cannot
connect to Prepar3D, and SimConnectPrepar3D cannot connect to MSFS, since each bundles a
different simulator’s own SimConnect client library.
Fix. Confirm which package is installed matches the simulator on that workstation. See Overview.
A capture session never starts on its own
Cause. StartOnSimRunning is off, or a session is already active (this module never starts
a second one on top of an existing session).
Fix. Enable StartOnSimRunning, or start the session manually if automatic start isn’t
wanted. See Configure.
The session ends the moment the simulator is paused
Cause. StopOnSimPaused defaults to on. This is deliberate - it exists so pausing the sim
does not keep recording a frozen aircraft state - but it means a routine pause during a long
exercise ends the session, it does not resume it when unpaused.
Fix. Disable StopOnSimPaused if you need the session to survive a pause, and stop it
manually at the real end of the exercise instead.
The first frame of a session shows an event that didn’t really happen
Cause. The event detector’s internal “previous state” always starts as grounded, engine off. Starting a session with the aircraft already airborne, or the engine already running, produces a spurious transition event on the first tick - see Data produced.
Fix. Treat the very first tick’s transition events as unreliable; this is expected behavior, not a data-quality fault to chase further.
The overspeed warning never seems to clear
Cause. There is no overspeed_warning_off event in this module’s output at all - once
overspeed_warning_on fires, nothing in the event stream signals the warning clearing, even
though the stall warning does have a matching on/off pair.
Fix. This is a real gap in this version, not a symptom to debug. If you need the cleared state, it is not available from this module’s events today.
A weapons or display event never appears (MSFS)
Cause. Weapons/combat capture and the cockpit-display probe are Prepar3D-only. The MSFS package has neither.
Fix. This is not supported on MSFS in this version; it is not a configuration issue.
A countermeasure event fired but with no name
Cause. This module cannot identify which type of countermeasure (chaff, flare, decoy) was
dispensed - countermeasure_name is always published empty. See
Data produced.
Fix. Nothing to configure; this is a known limitation, not a misconfiguration.