Game controller input module

The game controller input module reads button presses and analogue axis input from gamepads, joysticks and racing/flight controllers, using Windows’ two device APIs: DirectInput (any HID game controller) and XInput (Xbox-class pads, up to four). It opens each device in shared, background mode: the same controller stays available to a simulator or any other application at the same time.

Unlike most modules in this catalogue, it can capture from every connected controller simultaneously, not only one configured device.

What you need

• A gamepad, joystick, or racing/flight controller connected before the capture session starts.
• Xbox-class controllers need XInput, not DirectInput, to deliver data to a background process like HEAT Capture - see Troubleshooting for why, with measured evidence.

Interface Control Document

See Interface control document for DirectInput and XInput device identity, polling, button and axis event schemas, disconnect behavior and hidden-window requirements.

Pages

• Configure: device selection, polling rate, and what each toggle actually does.
• Data produced: the entity and event shapes, and why DirectInput and XInput devices report axes differently.
• Troubleshooting: symptoms, causes and fixes.

HEAT Capture team. Last updated 2 October 2026.