Configure the SimConnect module
Settings are edited in HEAT Capture’s module settings UI, under HEAT.SimConnect.Msfs or
HEAT.SimConnect.Prepar3D depending on which package is installed. Both packages share the same
settings shape.
Connection
| Setting | Type | Default | What it controls |
|---|---|---|---|
RemoteHost | string | empty (local connection) | Connects to SimConnect on another machine instead of the local simulator. Setting this writes a SimConnect.cfg file next to the module’s own binaries and switches to remote connection mode. |
RemotePort | integer | 500 | Port for the remote connection. Only used when RemoteHost is set. |
ReconnectIntervalMs | integer (ms) | 5000 | Initial delay before retrying a lost or failed connection. Each further retry doubles this, capped at 30000ms. |
If the simulator is not running when this module starts, it still initializes normally and keeps retrying; there is no separate “simulator not found” failure state.
Automatic session control
This module runs continuously from HEAT Capture’s own startup (see Overview), and uses these settings to decide when a capture session should start and stop on its own, based on the simulator’s state.
| Setting | Type | Default | What it controls |
|---|---|---|---|
StartOnSimRunning | boolean | true | Starts a capture session automatically the moment the simulation starts running, if one is not already active. |
StopOnSimPaused | boolean | true | Stops the active capture session automatically when the simulation pauses or stops. |
StopOnSilence | boolean | false | Safety-net stop: ends an active session if no SimConnect data has arrived for SilenceThreshold, independent of the pause/stop signal above. |
SilenceThreshold | duration | 30s | How long without data before StopOnSilence acts. Only relevant when StopOnSilence is enabled. |
This module also exposes the generic settings every HEAT Capture module has (Enabled,
Interval, OverrideNodeId/NodeId, Timeout) - see
Manage capture modules, and it leaves
Interval at the SDK-wide default of 1000 ms. SimConnect itself feeds this module’s cache
continuously in the background, but transition events (stall warning, ground/air, engine
running) are only computed when this module’s own capture call runs, at Interval cadence - not
every time the cache updates. A transition that starts and reverses inside one Interval window
is missed entirely, the same risk documented for the
game controller input module. Lower Interval if your
scenario needs to catch brief state changes reliably.