1. Getting Started
IOBridge User Guide
Set up IOBridge, map your controls and fly. Everything here works without reading the rest of the docs; the other guides go deeper.
1. Install
- Windows 10 or 11, 64-bit. The Windows installer is self-contained and bundles the .NET runtime, so no separate .NET installation is needed.
- Run the IOBridge installer. Normal use needs no admin rights.
- Drivers, from their official pages (IOBridge never downloads or installs them for you):
- vJoy 2.2.2.0 (required) for virtual joysticks: https://github.com/BrunnerInnovation/vJoy/releases
- HidHide (recommended) to hide your physical devices from games: https://github.com/nefarius/HidHide/releases
- ViGEmBus (optional) for a virtual Xbox 360 controller: https://github.com/nefarius/ViGEmBus/releases
Without vJoy or ViGEmBus, IOBridge runs in simulated mode: you can build, test and tune everything, and the telemetry dock shows what would have been sent.
2. The window
The left rail switches views:
| View | What it is for |
|---|---|
| MAP | Bind each button, hat and axis of a device to an action. |
| MONITOR | See every device's live input; the Sim Variables tab watches MSFS values. |
| OUTPUT | Add and manage virtual joysticks and gamepads. |
| MODES | Create modes (for example Combat or Landing) and how they inherit from Default. |
| PLUGINS | Stream Deck, mobile companion, Wave Link, YouTube Music, system audio. |
| DEPENDENCIES | Driver status, download links, and the FSUIPC7 and MSFS diagnostics. |
| COLORS | Theme colors for the current profile. |
The top bar holds the profile selector, the mode selector and the routing switch. The telemetry dock on the right (Ctrl+T) lists every output IOBridge sends.
3. First setup
- DEPENDENCIES: check which drivers are found. Missing ones have a link to their official download page.
- MONITOR: move your sticks and press buttons; the indicators should react. Plugged something in? Use Tools > Rescan USB Hardware Devices.
- MAP: pick a device, then click a button, hat or axis and choose what it does. Auto-Map All assigns every button of every device to virtual joystick buttons in order, as a quick start.
- Make sure routing is on (green Routing Active in the top bar), then start your game.
Action types
| Action | Does |
|---|---|
| Emulated joystick | vJoy button, axis or hat. |
| Hat to buttons | Turns a hat into four or eight buttons. |
| Emulated gamepad | Xbox 360 button, stick or trigger (ViGEmBus). |
| Game action | A command from a detected game's bindings (Star Citizen, Elite Dangerous, MechWarrior 5). |
| FSUIPC | An MSFS action from Common actions or the My actions builder. See fsuipc/README.md. |
| Keyboard macro | Keystrokes sent as hardware scancodes. |
| Wave Link, YouTube Music, system audio | Volume, mute and playback control. |
| Sound cue | Plays a sound. |
| Action chain | A sequence of steps with delays: keys, game actions, sounds, audio, HTTP requests. |
| Smart toggle | One button that alternates between two actions. |
| Mode switch | Changes the active mode (hold to shift, toggle on press, set mode, cycle to next). |
| HTTP request | Calls a URL you enter (for your own tools). |
| No action | Leaves the input unmapped (produces no output). |
Clearing bindings
To remove an assignment without affecting your other inputs, click the trash can icon at the right end of any bound input in the routing matrix. The input returns to unmapped status immediately with no action assigned, any repeating simulator action stops, and a notification banner appears with an Undo button. Click Undo within 10 seconds to restore the previous binding with all its settings.
Axes and curves
Select an axis on the MAP view to open the curve editor: linear, exponential, S-curve, spline or Bezier, plus deadzone, sensitivity, slew rate and inversion. Curves never overshoot, so the output always stays in range.
For MSFS axes bound through FSUIPC, the output range is set automatically (full range for flight controls, 0 to 16383 for levers), or you can force full, lever or a custom range. Reverse zone maps the bottom 10 percent of a throttle to reverse thrust.
2. Mapping Your Controls
Hardware and Input Mapping
IOBridge allows you to map every button, hat, switch, and analog axis on your hardware flight controllers.
5. Hiding physical devices (HidHide)
If a game sees both your real stick and the virtual one, inputs arrive twice. In the HidHide configuration client:
- Applications tab: add
IOBridge.UI.exe. - Devices tab: tick your physical devices.
- Tick Enable device hiding.
The MONITOR view shows a HidHide badge per device so you can confirm the state.
Hardware & Device Customization Guide
This guide details supported flight simulation hardware, custom button and dial labeling, DIY button box integration, and the authoritative user device database (device_db_user.json).
1. Supported Hardware Overview
IOBridge interfaces directly with any USB controller that exposes DirectInput endpoints on Windows.
Factory hardware templates are provided out of the box in device_db.json for major flight and space simulation peripherals:
| Manufacturer | Devices with templates (from device_db.json) |
|---|---|
| VKB-Sim | Gladiator NXT and EVO (left and right), Gladiator EVO Omni Throttle, Gunfighter with MCG, STECS throttle, T-Rudder |
| Virpil Controls | Constellation ALPHA and ALPHA Prime (left and right), MongoosT-50CM3 throttle, ACE, ACE-1, ACE-2 and ACE Torq pedals |
| Thrustmaster | T.16000M, TWCS throttle, HOTAS Warthog stick and throttle, TCA Sidestick and Quadrant (including Airbus editions), TPR, TFRP and T-LCM pedals |
| Logitech / Saitek | X56 Rhino stick and throttle, X52 and X52 Pro, Extreme 3D Pro, Flight and G Pro rudder pedals, Pro Flight rudder pedals |
| WinWing | Orion 2 stick and throttle bases, Ursa Minor Fighter (left and right), F18 panels, ICP, MFDs |
| Others | Turtle Beach VelocityOne Flightstick, CH Pro Pedals |
Any other DirectInput device works too; it just shows generic names (Button 12, Axis 3) until you label it (section 3).
2. Authoritative User Overrides (device_db_user.json)
To ensure custom physical button names, dial labels, and layout overrides are never lost during software updates or profile imports, IOBridge utilizes two separate database layers:
device_db.json: Shipped with the application. Contains read-only factory hardware definitions.device_db_user.json: Stored locally in your user profile directory. This file is authoritative. Any label, button name, or axis description you specify here takes precedence over the factory database and is never overwritten or reset.
Storage Location
%LOCALAPPDATA%\IOBridge\Config\device_db_user.json
This path is the same for installed and development builds. Older builds read device_db_user.json from the install Config folder; that copy is still loaded as a migration fallback, but the file under %LOCALAPPDATA% wins.
Database Architecture Rules
- User Name Integrity: IOBridge never invents, guesses, or renames authentic custom labels (such as
"SEM - Mode 1","SEM - Mode 2", or"SEM - Start (Red)"). - Non-Destructive Index Fallback: If a physical button index is omitted or set to an empty string in the JSON, the engine automatically exposes it as
Button {N}without filtering it out or failing device initialization.
3. Customizing Button & Axis Names
To label custom buttons, rotary dials, or toggle switches for your specific hardware:
Step 1: Identify Your Device Hardware IDs
- Press
Win + R, typejoy.cpl, and press Enter. - Select your flight stick or button box and click Properties. Note the exact controller name.
- Open Windows Device Manager (
devmgmt.msc), expand Human Interface Devices, right-click your device, select Properties, and switch to the Details tab. - Select Hardware Ids from the property dropdown. Note the 4-digit hexadecimal VID (Vendor ID) and PID (Product ID), for example
VID_231D&PID_0126.
Step 2: Add Entry to device_db_user.json
Open %LOCALAPPDATA%\IOBridge\Config\device_db_user.json in a text editor. Add an object matching your device:
{
"revision": 1,
"devices": [
{
"vendor_id": 8989,
"product_id": 516,
"name": "VKBsim Gladiator EVO R SEM",
"mapping": "vkb_gladiator_evo_custom"
}
],
"mapping": {
"vkb_gladiator_evo_custom": {
"Axis 1": "X Roll",
"Axis 2": "Y Pitch",
"Axis 3": "Trim Lever",
"Axis 6": "Twist",
"Button 1": "GRIP - Trigger 1",
"Button 2": "GRIP - Trigger 2",
"Button 37": "SEM - Mode 1",
"Button 38": "SEM - Mode 2",
"Button 52": "SEM - Start (Red)",
"Button 58": "SEM - Flaps 1",
"Button 59": "SEM - Flaps 2",
"Button 62": "SEM - Landing Gear (Down)",
"Button 64": "SEM - Landing Gear (Up)",
"Hat 1": "MiniStick (POV1)"
}
}
}
Step 3: Reload in IOBridge
Save the file and switch back to IOBridge. Click Rescan Hardware (Monitor view) or press F5. The mapping view and live monitor will now display your custom button names immediately.
4. DIY Button Boxes & Custom HID Hardware
IOBridge fully supports custom DIY flight simulator hardware, including:
- Microcontroller Boards: Arduino Pro Micro / Leonardo (ATmega32U4), Teensy 2.0 / 3.x / 4.x, Raspberry Pi Pico / RP2040 running GP2040-CE or custom USB HID joystick firmware.
- Commercial Interface Boards: Leo Bodnar BBI-32 (32-button interface), BU0836X, BU0836A, DSD (Derek Speare Designs) button boxes.
Integration Steps for Custom Hardware
- Connect your DIY button box to a USB port.
- In IOBridge, navigate to the Monitor tab. Your custom device will appear in the device list (e.g. "Arduino Micro Joystick" or "Leo Bodnar BBI-32").
- Press each physical switch, push button, and toggle to verify that the live detection indicator lights up.
- To assign authentic cockpit labels (e.g. "Landing Gear", "Master Caution", "Ejection Seat", "Quantum Spool"), follow Section 3 above and add the device Vendor ID and Product ID to
device_db_user.json.
5. DirectInput Polling & Precision Timing
IOBridge implements high-performance hardware polling via Vortice DirectInput with millisecond scheduling guarantees:
- Multimedia Timer Resolution: Windows default thread sleep times can fluctuate by up to 15.6 milliseconds due to power throttling and thread timeslicing. IOBridge invokes
timeBeginPeriod(1)upon initialization. This reduces kernel timer resolution to 1 millisecond, ensuring minimal input latency and smooth axis response curves. - Hot-Plug Resiliency: If a controller disconnects during flight (such as an accidental cable tug or power fluctuation), IOBridge retains your active profile configuration in memory. Reconnect it and rescan hardware; all mappings and curves apply again without restarting the simulator. While it is unplugged, held buttons are released, self-centering axes go to center, and throttles and sliders keep their last value.
3. Modes and Profiles
4. Modes
On the MODES view, add modes. Each one is either:
- Additive: only what you bind in that mode changes; everything else keeps working as in Default.
- Independent: the mode stands alone; unbound inputs do nothing.
Bind a button with the Mode switch action to change modes in flight.
6. Profiles
Profiles hold all bindings, modes and colors. Use the profile selector or the File menu to create, open, save and save as. IOBridge asks before discarding unsaved changes. With MSFS, profiles can switch automatically when you load a different aircraft (File > Aircraft Profiles & Auto-Switching). Profiles and application settings are stored locally on your PC; see Data files for complete storage locations and backup instructions.
7. Colors
COLORS (or Ctrl+Shift+C) sets the profile's theme. Presets per game: Quantum Cyan (Star Citizen), Cockpit Orange (Elite Dangerous), Battlemech Gold (MechWarrior), HUD Emerald (DCS), Aviation Azure (MSFS), Neon Magenta (Cyberpunk), Constellation Amber (Starfield), Tactical Crimson (Flight Deck default), or your own two colors. The paired phone companion uses the same colors.
8. Running in the background
Closing or minimizing the window keeps routing running in the system tray. The tray menu opens the window, turns routing on or off, rescans hardware and quits. If the exit warning is enabled, IOBridge reminds you that routing stops when you quit.
10. Keyboard shortcuts
| Shortcut | Action |
|---|---|
Ctrl+N |
New profile |
Ctrl+O |
Open profile |
Ctrl+S |
Save profile |
Ctrl+Shift+S |
Save profile as |
Ctrl+Shift+C |
Profile colors |
Ctrl+T |
Show or hide the telemetry dock |
F5 |
Rescan USB hardware |
4. MSFS and FSUIPC Integration
FSUIPC7 and MSFS Action Guide
IOBridge integrates with Microsoft Flight Simulator through FSUIPC7 and its companion WASM variable module. This guide explains how to map your hardware switches, encoders, and axes to cockpit actions using Common actions and the My actions builder.
1. Common Actions
The Common tab in the Sim Action Picker provides standard flight deck controls. These actions are standard simulator events that work with stock aircraft and aircraft using the simulator's own systems, without requiring knowledge of simulator internal variables.
Aircraft add-ons with their own custom avionics or complex systems often ignore standard simulator events. If an add-on aircraft does not respond to a Common action, build a My action for it instead.
Common actions are organized into logical flight systems:
- Autopilot: Master switch, flight director, heading hold, altitude hold, vertical speed hold, nav hold, approach mode, and heading/altitude bug adjustments.
- Flight Controls: Primary flight controls, elevator and rudder trim, flaps (extend, retract, set, step), spoilers, and landing gear.
- Instruments: Altimeter calibration (baro set, standard baro 29.92), gyro heading drift, and master caution/warning acknowledge.
- Lighting: Master lights switch, landing lights, taxi lights, beacon, strobe, navigation lights, and cockpit panel illumination.
- Engines and Fuel: Throttle cut, fuel pumps, engine starters, magnetos, mixture controls, and fuel tank selectors.
- Radios and Navigation: COM1/COM2 and NAV1/NAV2 standby frequency swaps, transponder ident, and audio panel selectors.
When assigning a button or switch, check the Common tab first. If the desired function exists there, select it directly.
2. My Actions (Personal Presets) and the Action Builder
When flying advanced community or third-party add-on aircraft (such as Fenix, FlyByWire, PMDG, or iniBuilds), cockpits often use custom internal variables (L: vars), HTML gauge events (H: vars), or simulator events (K: events) not covered by default controls.
The My actions tab lets you author, test, and save custom actions using the built-in Action Builder. Presets are saved locally in %APPDATA%\IOBridge\fsuipc_personal_presets.txt in standard FSUIPC preset format. They can also be exported to FSUIPC's myevents.txt file for use in other utilities. For details on how personal presets are saved and backed up, see data-files.md.
Creating an Action
- In the Sim Action Picker, switch to the My actions tab and click Build new action (or click the edit pencil on an existing action).
- Choose the Target:
- K: Simulator event or control.
- L: Local panel variable (L:var).
- H: HTML gauge event (H:var).
- Offset: Low-level FSUIPC memory offset.
- Choose the Operation:
- For K:
Send(trigger without parameter) orSend with value. - For L:
Set(assign specific value),Toggle(invert boolean state),Increase, orDecrease. - For H:
Send(trigger HTML event).
- For K:
- Enter the variable or event Name (prefixes like
K:orL:are optional; the builder formats them automatically). - (Optional) Enter the Value for operations that accept a parameter.
- Enter a Friendly name (e.g. "Parking Brake Set") and assign it to an Aircraft (e.g. "Generic" or "FlyByWire A320neo").
- Click Test to execute the action live in the simulator, then click Save.
Worked Example 1: K: Event with Value (Parking Brake Set)
To configure an explicit command that engages the parking brake:
- Target:
K - Operation:
Send with value - Name:
PARKING_BRAKE_SET - Value:
1 - Friendly name:
Parking Brake Set - Aircraft:
Generic
The builder automatically compiles this configuration into standard RPN calculator code:
1 (>K:PARKING_BRAKE_SET)
Saved metadata comment:
// iobridge-builder: K|SendWithValue|PARKING_BRAKE_SET|1|Parking Brake Set|Generic
Worked Example 2: L: Variable Toggle (Chrono Pushbutton)
To configure a toggle switch for the captain's clock chrono button on the FlyByWire A320neo:
- Target:
L - Operation:
Toggle - Name:
A32NX_EFIS_L_CHRONO_PUSHED - Value: (none)
- Friendly name:
Captain Chrono Toggle - Aircraft:
FlyByWire A320neo
The builder generates the self-inverting RPN expression:
(L:A32NX_EFIS_L_CHRONO_PUSHED) ! (>L:A32NX_EFIS_L_CHRONO_PUSHED)
Saved metadata comment:
// iobridge-builder: L|Toggle|A32NX_EFIS_L_CHRONO_PUSHED||Captain Chrono Toggle|FlyByWire A320neo
Deleting a My Action
When you delete an action from the My actions list in the picker, IOBridge checks all input slots in the active profile as well as other profile files saved on disk:
- Confirmation Prompt: Before removing the preset, IOBridge displays a confirmation dialog summarizing its usage:
- If the action is bound to buttons, it warns:
Delete '<friendly name>'? It is used by N buttons in this profile and M other profiles. They will be cleared. - If the action is unused, it reports:
Delete '<friendly name>'? It is not used by any button.
- If the action is bound to buttons, it warns:
- Active Profile Cleanup: When you confirm deletion, every slot referencing that action in the active profile (press, release, encoder, selector position, axis zone, and hat direction) is cleared immediately. Repeat-while-held sessions for those buttons stop at once, mappings left with no actions return to Unmapped state, and the profile is marked with unsaved changes. A status notification confirms:
Removed '<friendly name>' from N buttons. - Other Profiles Cleanup: Profiles on disk are cleaned automatically when they are next loaded. Any slot pointing to a deleted personal preset is reset, and a notification informs you:
N buttons used actions that were deleted and have been cleared. - Deleted Actions Never Fire: Unresolved personal preset bindings never fall back to cached calculator code. If a binding points to a deleted action, dispatch stops and sends nothing to the simulator.
Renaming and Editing a My Action
When you edit an existing My action in the builder:
- Code Updates: Any changes to calculator code, friendly name, or aircraft metadata take effect across all bound buttons in the active profile right away.
- Renaming: If you change the preset name, IOBridge updates every binding in the active profile to the new key immediately. To ensure bindings in your other profiles do not break, IOBridge records the pending key mapping in
%APPDATA%\IOBridge\fsuipc_personal_presets.renames.json. When each profile is next loaded, its bindings are automatically updated to the new key. Once all profiles on disk have been updated, the rename entry is purged.
3. Test and Read-Back
The Test Button
While creating or editing an action, click the Test button. IOBridge sends the generated calculator code immediately to MSFS through the FSUIPC WASM module. This allows you to verify that the virtual cockpit lever or dial moves correctly before saving the binding.
Simulator Read-Back
Many cockpit switches and annunciators require two-way synchronization:
- Button Box LEDs and Indicators: When an autopilot mode or gear state changes inside the simulator, IOBridge reads the corresponding simulation variable or offset and updates hardware LED states.
- Rotary Encoders and Multi-Position Switches: Reading back switch positions ensures that physical hardware dials stay synchronized with on-screen instruments.
4. Capture Mode
If you do not know the exact variable name for a switch in an add-on cockpit, use Capture Mode:
- In the Sim Action Picker, click Capture mode.
- Switch to Microsoft Flight Simulator and click the desired switch or knob in the 3D cockpit.
- IOBridge continuously samples all active L:vars and detects which variable changed value.
- Return to IOBridge. The candidate panel displays the detected variable name along with its before and after values.
- Click Use this:
- For single button actions: The builder opens pre-filled with the variable name and target value.
- For two-way toggle switches: You can assign both the primary slot (ON state) and the release slot (OFF state) in one step.
5. Migration of Legacy Bindings
Earlier versions listed every action found in your FSUIPC install (simulator controls, FSUIPC controls, presets and add-on events). That list was long and full of duplicates, so it was replaced by the Common list and My actions.
Starting with IOBridge 0.1.0, existing profiles are automatically updated to use Common actions and My actions.
When loading an existing flight profile created with an earlier version:
- Bindings referencing legacy controls (
k:,h:,fsuipc:,preset:) are automatically migrated. - If a legacy binding matches a standard flight control, it is mapped directly to the equivalent Common action.
- Other custom bindings are converted to standard RPN calculator code actions.
- Your hardware mappings continue to function without interruption. When you open a migrated binding, you can edit it directly in the Action Builder.
6. Reference Tables
When authoring custom actions in the My actions builder, consult these reference tables to look up exact event names, offsets, and IDs:
| Reference Table | Description |
|---|---|
| Appendix A: MSFS Controls | Lookup table for 1,896 native simulator event names (K: events). |
| Appendix D: Offsets | Lookup table for 1,604 FSUIPC memory offset addresses, byte sizes, and data types. |
| Appendix E: Cockpit SDK Events | Lookup table for third-party cockpit SDK controls, including PMDG 737, 777, and 747 event IDs. |
FSUIPC common actions
The short list of simulator actions IOBridge ships for MSFS through FSUIPC. These actions work on any aircraft that uses the simulator's standard systems. Anything else (an add-on aircraft's own switches, a specific variable, an offset) is built by the user as a My action: see README.md.
Rules for this list:
- One entry per job. No duplicates: when the simulator has two events that do the same thing, only one of them is listed.
- Every entry is a standard MSFS event (
K:) from Appendix A (appendix-a-msfs-controls.md), sent as calculator code. - Behavior says how to bind it: Press sends it once per button press; Hold sends it repeatedly while the button is held (every 100 ms by default); Value sends the number shown.
- The app ships this list in
Config/common_actions.json, with the same ids, names, groups, code and descriptions. This file is the source; when the list changes, both change together. - Read-back (showing the current state) uses the shipped state source table (
Config/fsuipc_state_sources.json) wherever an entry matches one of its patterns.
Brakes and gear
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
parking-brake-toggle |
Parking brake (toggle) | (>K:PARKING_BRAKES) |
Press | Sets or releases the parking brake. |
parking-brake-on |
Parking brake on | 1 (>K:PARKING_BRAKE_SET) |
Value | Sets the parking brake, whatever its current state. |
parking-brake-off |
Parking brake off | 0 (>K:PARKING_BRAKE_SET) |
Value | Releases the parking brake, whatever its current state. |
brakes |
Brakes (both) | (>K:BRAKES) |
Hold | Applies both wheel brakes while held. |
gear-toggle |
Landing gear (toggle) | (>K:GEAR_TOGGLE) |
Press | Moves the gear handle to the other position. |
gear-up |
Landing gear up | (>K:GEAR_UP) |
Press | Moves the gear handle up. |
gear-down |
Landing gear down | (>K:GEAR_DOWN) |
Press | Moves the gear handle down. |
Flaps, spoilers and trim
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
flaps-down-step |
Flaps down one step | (>K:FLAPS_INCR) |
Press | Extends the flaps by one notch. |
flaps-up-step |
Flaps up one step | (>K:FLAPS_DECR) |
Press | Retracts the flaps by one notch. |
flaps-full-up |
Flaps fully up | (>K:FLAPS_UP) |
Press | Retracts the flaps completely. |
flaps-full-down |
Flaps fully down | (>K:FLAPS_DOWN) |
Press | Extends the flaps completely. |
spoilers-toggle |
Spoilers (toggle) | (>K:SPOILERS_TOGGLE) |
Press | Extends or retracts the spoilers. |
spoilers-arm-toggle |
Spoilers arm (toggle) | (>K:SPOILERS_ARM_TOGGLE) |
Press | Arms or disarms automatic spoilers. |
elevator-trim-nose-down |
Elevator trim nose down | (>K:ELEV_TRIM_DN) |
Hold | Trims the nose down while held. |
elevator-trim-nose-up |
Elevator trim nose up | (>K:ELEV_TRIM_UP) |
Hold | Trims the nose up while held. |
aileron-trim-left |
Aileron trim left | (>K:AILERON_TRIM_LEFT) |
Hold | Trims the roll to the left while held. |
aileron-trim-right |
Aileron trim right | (>K:AILERON_TRIM_RIGHT) |
Hold | Trims the roll to the right while held. |
rudder-trim-left |
Rudder trim left | (>K:RUDDER_TRIM_LEFT) |
Hold | Trims the yaw to the left while held. |
rudder-trim-right |
Rudder trim right | (>K:RUDDER_TRIM_RIGHT) |
Hold | Trims the yaw to the right while held. |
Lights
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
light-beacon-toggle |
Beacon light (toggle) | (>K:TOGGLE_BEACON_LIGHTS) |
Press | Turns the beacon on or off. |
light-strobe-toggle |
Strobe lights (toggle) | (>K:STROBES_TOGGLE) |
Press | Turns the strobes on or off. |
light-landing-toggle |
Landing lights (toggle) | (>K:LANDING_LIGHTS_TOGGLE) |
Press | Turns the landing lights on or off. |
light-taxi-toggle |
Taxi lights (toggle) | (>K:TOGGLE_TAXI_LIGHTS) |
Press | Turns the taxi lights on or off. |
light-nav-toggle |
Navigation lights (toggle) | (>K:TOGGLE_NAV_LIGHTS) |
Press | Turns the navigation lights on or off. |
light-panel-toggle |
Panel lights (toggle) | (>K:PANEL_LIGHTS_TOGGLE) |
Press | Turns the instrument panel lights on or off. |
light-logo-toggle |
Logo lights (toggle) | (>K:TOGGLE_LOGO_LIGHTS) |
Press | Turns the logo lights on or off. |
light-wing-toggle |
Wing lights (toggle) | (>K:TOGGLE_WING_LIGHTS) |
Press | Turns the wing lights on or off. |
light-cabin-toggle |
Cabin lights (toggle) | (>K:TOGGLE_CABIN_LIGHTS) |
Press | Turns the cabin lights on or off. |
Autopilot
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
ap-master |
Autopilot master | (>K:AP_MASTER) |
Press | Engages or disengages the autopilot. |
ap-flight-director |
Flight director (toggle) | (>K:TOGGLE_FLIGHT_DIRECTOR) |
Press | Shows or hides the flight director. |
ap-heading-hold |
Heading hold | (>K:AP_HDG_HOLD) |
Press | Turns heading mode on or off. |
ap-altitude-hold |
Altitude hold | (>K:AP_ALT_HOLD) |
Press | Turns altitude hold on or off. |
ap-nav-hold |
NAV mode | (>K:AP_NAV1_HOLD) |
Press | Turns navigation tracking on or off. |
ap-approach-hold |
Approach mode | (>K:AP_APR_HOLD) |
Press | Turns approach mode on or off. |
ap-vertical-speed-hold |
Vertical speed mode | (>K:AP_VS_HOLD) |
Press | Turns vertical speed mode on or off. |
ap-flight-level-change |
Flight level change | (>K:FLIGHT_LEVEL_CHANGE) |
Press | Turns flight level change mode on or off. |
ap-yaw-damper |
Yaw damper (toggle) | (>K:YAW_DAMPER_TOGGLE) |
Press | Turns the yaw damper on or off. |
ap-autothrottle-arm |
Autothrottle arm | (>K:AUTO_THROTTLE_ARM) |
Press | Arms or disarms the autothrottle. |
ap-heading-bug-inc |
Heading bug right | (>K:HEADING_BUG_INC) |
Hold | Turns the heading bug clockwise. |
ap-heading-bug-dec |
Heading bug left | (>K:HEADING_BUG_DEC) |
Hold | Turns the heading bug counterclockwise. |
ap-altitude-inc |
Selected altitude up | (>K:AP_ALT_VAR_INC) |
Hold | Raises the selected altitude. |
ap-altitude-dec |
Selected altitude down | (>K:AP_ALT_VAR_DEC) |
Hold | Lowers the selected altitude. |
ap-vertical-speed-inc |
Selected vertical speed up | (>K:AP_VS_VAR_INC) |
Hold | Raises the selected vertical speed. |
ap-vertical-speed-dec |
Selected vertical speed down | (>K:AP_VS_VAR_DEC) |
Hold | Lowers the selected vertical speed. |
ap-speed-inc |
Selected speed up | (>K:AP_SPD_VAR_INC) |
Hold | Raises the selected airspeed. |
ap-speed-dec |
Selected speed down | (>K:AP_SPD_VAR_DEC) |
Hold | Lowers the selected airspeed. |
Engines and electrical
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
battery-master-toggle |
Battery master (toggle) | (>K:TOGGLE_MASTER_BATTERY) |
Press | Turns the main battery on or off. |
alternator-master-toggle |
Alternator (toggle) | (>K:TOGGLE_MASTER_ALTERNATOR) |
Press | Turns the alternator or generator on or off. |
avionics-master-toggle |
Avionics master (toggle) | (>K:TOGGLE_AVIONICS_MASTER) |
Press | Turns the avionics bus on or off. |
fuel-pump-toggle |
Electric fuel pump (toggle) | (>K:TOGGLE_ELECT_FUEL_PUMP) |
Press | Turns the electric fuel pump on or off. |
pitot-heat-toggle |
Pitot heat (toggle) | (>K:PITOT_HEAT_TOGGLE) |
Press | Turns pitot heat on or off. |
anti-ice-toggle |
Engine anti-ice (toggle) | (>K:ANTI_ICE_TOGGLE) |
Press | Turns engine anti-ice on or off. |
engine-auto-start |
Auto start engines | (>K:ENGINE_AUTO_START) |
Press | Runs the simulator's automatic engine start. |
engine-auto-shutdown |
Auto shut down engines | (>K:ENGINE_AUTO_SHUTDOWN) |
Press | Runs the simulator's automatic engine shutdown. |
throttle-cut |
Throttle idle | (>K:THROTTLE_CUT) |
Press | Moves all throttles to idle. |
throttle-full |
Throttle full | (>K:THROTTLE_FULL) |
Press | Moves all throttles to full. |
throttle-inc |
Throttle up | (>K:THROTTLE_INCR) |
Hold | Advances all throttles. |
throttle-dec |
Throttle down | (>K:THROTTLE_DECR) |
Hold | Pulls back all throttles. |
prop-pitch-inc |
Propeller RPM up | (>K:PROP_PITCH_INCR) |
Hold | Increases propeller RPM. |
prop-pitch-dec |
Propeller RPM down | (>K:PROP_PITCH_DECR) |
Hold | Decreases propeller RPM. |
mixture-inc |
Mixture richer | (>K:MIXTURE_INCR) |
Hold | Richens the mixture. |
mixture-dec |
Mixture leaner | (>K:MIXTURE_DECR) |
Hold | Leans the mixture. |
Radios and instruments
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
com1-swap |
COM1 swap | (>K:COM_STBY_RADIO_SWAP) |
Press | Swaps the COM1 active and standby frequencies. |
nav1-swap |
NAV1 swap | (>K:NAV1_RADIO_SWAP) |
Press | Swaps the NAV1 active and standby frequencies. |
transponder-ident |
Transponder IDENT | (>K:XPNDR_IDENT_ON) |
Press | Sends a transponder ident. |
altimeter-set |
Altimeter to local pressure | (>K:BAROMETRIC) |
Press | Sets the altimeter to the current local pressure. |
Simulator and ground
| Id | Name | Code | Behavior | What it does |
|---|---|---|---|---|
sim-pause |
Pause (toggle) | (>K:PAUSE_TOGGLE) |
Press | Pauses or resumes the simulator. |
sim-rate-inc |
Simulation rate up | (>K:SIM_RATE_INCR) |
Press | Speeds up the simulation rate. |
sim-rate-dec |
Simulation rate down | (>K:SIM_RATE_DECR) |
Press | Slows down the simulation rate. |
pushback-toggle |
Pushback (toggle) | (>K:TOGGLE_PUSHBACK) |
Press | Requests or stops the pushback tug. |
jetway-toggle |
Jetway (toggle) | (>K:TOGGLE_JETWAY) |
Press | Connects or disconnects the jetway. |
smoke-toggle |
Smoke (toggle) | (>K:SMOKE_TOGGLE) |
Press | Turns the smoke system on or off. |
5. Game Profiles and Native Bindings
Game Profiles & Native Binding Ingestion
IOBridge features automated discovery and ingestion of game keybindings directly from simulator configuration files. This eliminates the need to manually memorize or duplicate game keybinds across tools.
1. Automated Game Detection System
The GameBindingsService automatically scans local configuration directories on startup and when refreshed from the Dependencies or Mapping views.
Simulator Config File
│
▼
┌─────────────────────────────────┐
│ GameBindingsService │
│ XML and INI readers │
└────────────────┬────────────────┘
│
▼
┌─────────────────────────────────┐
│ AvailableGameActions │
│ Categorized Actions & Scancodes│
└────────────────┬────────────────┘
│
▼
┌─────────────────────────────────┐
│ DirectInput Dispatch │
│ Win32 SendInput (Scancodes) │
└─────────────────────────────────┘
Supported Games & Configuration Paths
| Simulator | Supported Versions | Configuration Path Detected | Ingestion Format |
|---|---|---|---|
| Star Citizen | LIVE, PTU, EPTU | %LOCALAPPDATA%\StarCitizen\...\actionmaps.xml |
XML (<actionmap>, <action>) |
| Elite Dangerous | Horizons, Odyssey 4.0 | %LOCALAPPDATA%\Frontier Developments\Elite Dangerous\Options\Bindings\*.binds |
XML (<Binding>, <Primary>, <Secondary>) |
| MechWarrior 5: Mercenaries | Steam, EGS, Game Pass | %LOCALAPPDATA%\MW5Mercs\Saved\Config\WindowsNoEditor\GameUserSettings.ini |
INI (CustomBindings, ActionMappings) |
| MechWarrior 5: Clans | Steam, EGS, Game Pass | %LOCALAPPDATA%\MW5Clans\Saved\Config\Windows\GameUserSettings.ini |
INI (CustomBindings, ActionMappings) |
| MSFS 2024 / 2020 | Detected install folders | The sim's default keyboard input profiles (fs-input-profiles) |
XML |
For MSFS, FSUIPC Common and My actions are usually the better route; see fsuipc/README.md.
2. Ingestion Mechanics by Simulator
Star Citizen (actionmaps.xml)
Star Citizen structures its bindings within XML action maps corresponding to ship flight, combat, vehicles, EVA, mining, and FPS gameplay:
- Discovered Categories: Spaceship General, Flight Movement, Flight Targeting, Quantum Travel, Flight Systems, Mining, Salvage, Turret Controls, Emotes.
- Modifier Parsing: Detects single keys and combined inputs (e.g.
lalt+w,lctrl+r). - Live XML vs Presets: If
actionmaps.xmlis present, IOBridge extracts the user's live custom bindings. If no file is detected, IOBridge falls back to authentic built-in presets covering the full Star Citizen flight deck.
Elite Dangerous (*.binds)
Elite Dangerous saves custom control schemes as XML files in the local options directory:
- Active Scheme Detection: Scans the folder and selects the most recently updated
.bindsfile (e.g.Custom.4.0.binds). - Multi-Button Modifiers: Correctly parses modifier tags such as
<Modifier Device="Keyboard" Key="Key_LeftShift" />. - Discovered Categories: Flight Controls, Throttle, Targeting, Weapons, Systems (Cargo Scoop, Landing Gear, Night Vision), Supercruise/FSD, SRV Driving.
MechWarrior 5: Mercenaries & Clans (GameUserSettings.ini)
Unreal Engine stores custom action mappings in GameUserSettings.ini under [/Script/Engine.InputSettings]:
- Discovered Actions: Fire Weapon Groups 1 to 6, Alpha Strike, Chain Fire, Torso Twist, Arm Lock, Center Legs to Torso, Jump Jets, Zoom In/Out, Thermal Vision, Night Vision, BattleGrid.
- Direct Scancode Extraction: Keys are mapped directly to physical keyboard scancodes for low-level injection.
3. Scancode Injection & Anti-Cheat Compatibility
Many modern space and combat simulators utilize kernel-level or user-mode anti-cheat systems (such as Easy Anti-Cheat in Star Citizen). High-level virtual key events generated by keybd_event or standard Windows forms can be filtered or ignored by DirectInput and RawInput game engines.
IOBridge sends keystrokes with SendInput using KEYEVENTF_SCANCODE (see VirtualOutputManager), adding KEYEVENTF_EXTENDEDKEY for extended keys (arrows, Home, End, Insert, Delete, numpad Enter). Games that read hardware scancodes see them like keys from a real keyboard. We cannot guarantee how any game's anti-cheat behaves.
4. Rebinding with Ingested Game Actions
Once game configurations are scanned, all discovered actions appear in the Mapping tab:
- Click any physical button or dial on your joystick to highlight it in the active device list.
- In the Target Action Type dropdown, select Game Action.
- In the Game Category / Action dropdown, select from the discovered bindings (e.g.
[Star Citizen] Flight Systems: Quantum Drive - Engage). - Choose whether to execute on press, on release, or hold while pressed.
- Save the profile.
5. Creating Custom Profiles
Profiles are saved as human-readable JSON files in:
%LOCALAPPDATA%\IOBridge\Profiles\
Profile file
Each profile is one JSON file (ProfileModel in Services/ProfileService.cs) with ProfileName, Version, LastModified, ActiveMode, ThemeCustomization, Modes (OperationalModeItem) and Mappings (InputMapping). Files are written atomically and the previous version is kept as <name>.json.bak. Edit profiles in the app rather than by hand; the mapping format is large and versioned.
6. Configuring Generic & Non-Ingested Simulators
While IOBridge provides automated keybind extraction for Star Citizen, Elite Dangerous, and MechWarrior 5, it is equally capable of powering simulators without automated configuration parsers.
Supported non-ingested flight and combat simulators include:
- DCS World (Digital Combat Simulator)
- IL-2 Sturmovik: Great Battles
- Falcon BMS
- War Thunder
- Starfield
Integration Strategy: Virtual Controller Routing
For generic simulators, use virtual controller routing rather than direct key emulation:
[Physical Flight Stick] ──► [IOBridge Engine] ──► [Virtual vJoy Device #1] ──► [Simulator Input Settings]
(Curves, Deadzones) (Monotone Math) (Standard DirectInput) (Bound to Pitch/Roll)
- Configure Axes in IOBridge:
- Navigate to the Map tab.
- Select your physical joystick or throttle axis.
- Set the action type to Emulated joystick (or Emulated gamepad) and pick the target axis.
- Tune response curves, center deadzones, and sensitivity to your preference.
- Cloak Physical Devices via HidHide:
- Open the HidHide configuration client from the Start Menu.
- Cloak your physical joystick hardware so the game cannot see the raw USB endpoints.
- Ensure
IOBridge.UI.exeis whitelisted.
- Bind Controls in the Simulator:
- Launch your simulator (e.g. DCS World or MSFS).
- Open the in-game control settings menu.
- In the device dropdown, select vJoy Device #1 (or Controller Xbox 360).
- Move your physical axis: the simulator detects the clean, smoothed output from vJoy.
- Keyboard Scancode Fallback for Cockpit Switches:
- For simulator switches that only accept keyboard inputs (e.g. Autopilot Toggle, Master Arm, Speedbrake), set the action type in IOBridge to Keyboard macro.
- Pick the exact key combination configured in the game (e.g.
Left Ctrl + A). - IOBridge injects low-level hardware scancodes that pass directly through game input hooks.
7. Profile Organization & Manual Switching
Flight simulation cockpits often require distinct control schemes for different airframes, spacecraft, or games.
Profile Switching Methods
- Desktop: the profile selector in the top bar, or the File menu.
- Automatically for MSFS: File > Aircraft Profiles & Auto-Switching links profiles to aircraft.
- Mobile companion: the profile switcher on the phone (companion API
POST /api/companion/profiles/select).
Auto-Save & Dirty State Tracking
- Whenever mappings, curves, or modes are modified in the GUI, IOBridge tracks dirty changes via
IsProfileDirty. - Save with Save Profile (
Ctrl+S) to write changes to%LOCALAPPDATA%\IOBridge\Profiles\. - When switching profiles with unsaved modifications, IOBridge prompts you to save changes, preventing accidental loss of complex curve calibration.
More
User guide, Mobile companion, Troubleshooting, Hardware and devices, HTTP API.
6. Mobile Companion Guide
Mobile Companion Guide (Android APK)
The IOBridge Mobile Companion is a dedicated Android touch application designed for flight simulation cockpits, space sim pilots, and multi-controller rigs. It enables in-game mode switching, profile selection, routing control, and real-time input rebinding without Alt-Tabbing away from full-screen simulators.
1. Key Capabilities
- Zero Alt-Tab Interruption: Adjust controller mappings, switch operational layers, and monitor output status from a secondary screen (phone, tablet, or mounted cockpit display).
- Live Hardware Input Sensor: Pressing any physical button, toggle switch, hat direction, or rotary dial on your joystick immediately highlights that specific input on your phone screen.
- In-Game Rebinding & 4-Way Hats: Tap any highlighted physical control on your phone to assign it to native simulator keybinds (Star Citizen, Elite Dangerous, MechWarrior 5 Mercenaries & Clans, MSFS), virtual joystick buttons (vJoy), keyboard macros, operational mode shifts, or individual 4-way POV hat directions.
- Touch Button Pad: 16 customizable touch tiles on the Pad tab that act as virtual deck buttons mapped directly in IOBridge.
- Rescan Games & Default-Key Badges: Re-scan installed game bindings remotely with Rescan Games and see
[KEY]indicators on actions that use a game's default keybind. - Cockpit Quick Controls: Oversized, high-contrast touch buttons to switch operational modes (e.g. Flight, Combat, Docking, Mining) and toggle routing on or off.
- Secure 6-Digit PIN Pairing: Modeled after modern media streaming remotes. Generates a temporary 6-digit verification code on the PC screen to prevent unauthorized access across local Wi-Fi networks.
- In-App Update Banner: Checks
GET /api/companion/update-checkagainst the bundled APK metadata and prompts when a newer companion APK is available from the connected PC. - Flight Deck Theming: Dynamically inherits the desktop application's primary and secondary accent colors and dark cockpit aesthetic.
2. Installing the companion
The companion APK ships with IOBridge (iobridge-companion.apk in the install folder) and the desktop app serves it to your phone. It is not on any app store.
From the PC over Wi-Fi
- Put the phone on the same Wi-Fi as the PC (not a guest network), and make sure the PC's network is set to Private in Windows.
- In IOBridge, open Plugins > Mobile Companion. The card displays a QR code for the download URL alongside reachable IPv4 network addresses.
- Point your phone's camera at the QR code (or open the displayed URL in your phone's mobile browser) to download the companion APK directly.
- Open the downloaded APK file. When Android prompts, allow your browser to install unknown apps, then complete installation.
The MSI installer automatically configures Windows Firewall exceptions on Private and Domain networks. If your connection is set to Public, Windows blocks incoming phone traffic; set the network profile to Private in Windows Settings. If the download times out or pairing fails, see Troubleshooting: phone cannot reach the PC.
By cable or file share
Open APK Folder on the Mobile Companion card opens the folder with the APK. Copy it to the phone and open it there.
Updates
Once paired, the companion asks the PC whether a newer APK is available and offers to install it.
3. Pairing
Phone PC (IOBridge)
| 1. Connect & Pair (PC address) |
|-------- POST /api/pair/request ------------>| only while "Pair a Device" is open
| | 2. shows a 6-digit PIN
| 3. enter the PIN |
|-------- POST /api/pair/confirm ------------>| 4. checks the PIN, issues a token
|<======= authenticated API and WebSocket ===>|
- On the PC, click Pair a Device on the Mobile Companion card. Pairing stays open for a limited time, with a countdown.
- In the companion, tap Scan Network. The companion uses native UDP broadcast discovery on port 28156 to automatically locate your PC on the Wi-Fi network and list it under discovered instances. Tap Connect next to your PC (or type the PC IP address manually if network isolation blocks UDP broadcast).
- Enter the 6-digit PIN shown on the PC. A PIN is valid for 2 minutes and allows 5 attempts.
- The phone is paired and keeps its token until you revoke it.
Removing a phone
On the Mobile Companion card, use the revoke button next to the phone. Its token stops working immediately.
4. Mobile Interface Overview
The mobile interface is optimized for one-touch operation in low-light cockpit conditions:
┌────────────────────────────────────────────────────────┐
│ IOBRIDGE COMPANION [● ROUTING ACTIVE] (X) │
├────────────────────────────────────────────────────────┤
│ PROFILE: Star Citizen - Hornet Ghost │
│ │
│ OPERATIONAL MODES: │
│ ┌───────────────────────┐ ┌───────────────────────┐ │
│ │ [ DEFAULT ] │ │ [ COMBAT ] │ │
│ └───────────────────────┘ └───────────────────────┘ │
│ ┌───────────────────────┐ ┌───────────────────────┐ │
│ │ [ LANDING ] │ │ [ MINING ] │ │
│ └───────────────────────┘ └───────────────────────┘ │
├────────────────────────────────────────────────────────┤
│ LIVE HARDWARE SENSOR: │
│ Device: VKB Gladiator NXT EVO Left │
│ Active Input: Button 12 (Trigger Second Stage) │
│ │
│ [ REBIND INPUT ] [ RESTORE DEFAULT ] │
├────────────────────────────────────────────────────────┤
│ CURRENT MAPPING: │
│ Target: [Game Action] SpaceShip_FireGroup1 │
│ Action Mode: While Pressed │
└────────────────────────────────────────────────────────┘
Live Rebinding & Button Pad
- While sitting in your simulator, press the physical button on your joystick or throttle that you wish to reconfigure.
- The Live Hardware Sensor card on your mobile screen will highlight in green and display the exact device and button name.
- Tap Rebind Input. For a 4-way POV hat switch, select each direction slot (North, East, South, West) independently.
- Select a new target action:
- Game Action: Pick from detected Star Citizen, Elite Dangerous, MechWarrior 5 Mercenaries & Clans, or MSFS commands (
[KEY]highlights fallback default keybinds; tap Rescan Games after changing in-game keybinds). - vJoy Output: Route directly to a specific virtual joystick button.
- Keyboard Scancode: Inject a hardware keyboard key sequence.
- Mode Shift: Assign this physical button to trigger or hold an operational mode.
- Game Action: Pick from detected Star Citizen, Elite Dangerous, MechWarrior 5 Mercenaries & Clans, or MSFS commands (
- Tap Apply. The new mapping takes effect immediately without needing to restart the game or IOBridge.
- Switch to the Button Pad view for 16 touch tiles you can map as a dedicated cockpit deck over Wi-Fi.
5. Technical details
- Web app (HTML, CSS, JavaScript bundled with Vite) wrapped as a native Android app with Capacitor 7. Minimum Android 6.0 (SDK 23), target SDK 35.
- Talks only to the PC on your local network: HTTP and WebSocket on TCP 28156, discovery on UDP 28156. No internet access needed. API reference: http-api.md.
More
7. Troubleshooting
IOBridge Troubleshooting
This guide provides troubleshooting solutions for common hardware, driver, network, and simulator integration issues encountered in flight and space simulation rigs.
1. Virtual Driver Diagnostics
vJoy Virtual Joystick (Required)
Issue: "vJoy Driver: (Not Installed / Unavailable)"
- Cause:
vJoyInterface.dllis missing from the system path, or the vJoy kernel driver is not active. vJoy is required for virtual joystick feeds. - Resolution:
- Download and run the signed vJoy 2.2.2.0 installer from the vJoy releases page. This is the maintained vJoy build IOBridge is developed and tested against.
- Ensure the installer registers
vJoyInterface.dllinC:\Windows\System32\orC:\Program Files\vJoy\x64\. - Restart the computer if prompted by Windows driver manager.
- Launch IOBridge and navigate to Dependencies to verify the driver displays
(Installed & Active).
Issue: "Failed to Acquire vJoy Device #1" / Device Busy
- Cause: Another application (such as Joystick Gremlin, UCR, or an active simulator process) has already opened vJoy device #1 in exclusive mode.
- Resolution:
- Close any background mapping utilities (Joystick Gremlin, FreePIE, UCR).
- Open vJoyConf from the Start Menu or with Configure vJoy on the Dependencies view.
- Verify that the virtual joystick device is enabled and has axes, buttons, and POV hats configured.
- In IOBridge, click Rescan Hardware or toggle the master routing switch off and on again.
ViGEmBus Virtual Gamepad (Optional)
ViGEmBus is optional and only needed if a target game requires an Xbox 360 controller rather than a DirectInput joystick. Gamepad output is less tested than vJoy output.
Issue: "ViGEmBus: (Not Installed / Unavailable)"
- Cause: The Nefarius ViGEmBus system driver is not installed.
- Resolution:
- Download the latest installer from the official repository: ViGEmBus Releases.
- Run the installer and accept the driver installation.
- Restart IOBridge. The Dependencies tab will immediately reflect the active driver status.
Issue: Virtual Xbox 360 controller not detected by game
- Cause: The game engine only enumerates controllers attached before launching, or requires controller #1 slot.
- Resolution:
- In IOBridge, ensure master routing is active before starting the simulator.
- Press
Win + R, typejoy.cpl, and press Enter to open the Windows Game Controllers control panel. - Confirm that "Controller (XBOX 360 For Windows)" appears in the list and responds when moving mapped inputs.
Nefarius HidHide (Device Cloaking, Recommended)
HidHide is recommended to prevent double-input conflicts by hiding physical controllers from games.
Issue: Simulator detects both physical joystick and virtual controller ("Double-Input")
- Cause: Physical flight sticks are visible to games alongside the virtual output device, causing conflicting simultaneous inputs.
- Resolution:
- Open the HidHide Configuration Client from the Start Menu.
- In the Applications tab, ensure
IOBridge.UI.exeis added to the application whitelist (marked with an active checkmark). This allows IOBridge to read the physical hardware. - In the Devices tab, locate your physical joysticks, throttles, and rudder pedals. Check the box next to each device to cloak it from other applications.
- At the bottom of the client, check Enable device hiding.
- Restart your simulator. The game will now only see the virtual vJoy or ViGEm output controllers.
Issue: IOBridge shows no inputs after enabling HidHide ("Complete Lockout")
- Cause:
IOBridge.UI.exewas not added to the HidHide whitelist, causing HidHide to cloak the hardware from IOBridge itself. - Resolution:
- Open the HidHide Configuration Client.
- Uncheck Enable device hiding temporarily to restore hardware access.
- Navigate to the Applications tab, click +, and browse to
IOBridge.UI.exe(e.g.C:\Program Files\IOBridge\IOBridge.UI.exeor your development folder). - Re-enable Enable device hiding. Verify that IOBridge can read inputs in the Monitor view.
2. Network & Mobile Companion Diagnostics
The companion server listens on port 28156 for both TCP (download, pairing, control) and UDP (discovery). Phones must be on the same local network as the PC.
Phone cannot reach the PC (download times out, Scan Network finds nothing)
- Cause: Windows Firewall blocks inbound connections to IOBridge. This happens when the network is set to Public, or when the firewall question Windows shows on first start was dismissed (Windows then adds Block rules named
IOBridge.UI). Guest Wi-Fi networks that isolate devices also block it. - Resolution:
- Make sure the PC's network is Private: Windows Settings > Network & internet > your connection > Network profile type. The MSI installer automatically configures firewall exceptions for Private and Domain profiles, but never for Public profiles.
- If using the installed app, the MSI registers firewall rules for
IOBridge.UI.exeon port 28156 (TCP and UDP) and removes them on uninstall. If rules are missing or blocked, reinstall IOBridge or check Windows Security > Firewall & network protection > Allow an app through firewall. - If running a portable or development build from source, open PowerShell as administrator and add the rules manually:
netsh advfirewall firewall add rule name="IOBridge Companion TCP" dir=in action=allow protocol=TCP localport=28156 profile=private
netsh advfirewall firewall add rule name="IOBridge Companion UDP" dir=in action=allow protocol=UDP localport=28156 profile=private
- Check the server itself on the PC:
http://127.0.0.1:28156/api/companion/pingin a browser must return JSON. - Put the phone on the same Wi-Fi as the PC (not a guest network).
Scan Network does not find the PC
- Cause: The companion's scan currently only tries addresses it already knows. Automatic discovery on real phones is being added (IOBridge#248).
- Resolution: In IOBridge, open Plugins > Mobile Companion and note the PC address in the download link. In the companion, enter that address and tap Connect & Pair.
Android blocks installing the APK
- Cause: Android asks for permission before installing apps downloaded by a browser.
- Resolution: When Android asks, allow your browser to install unknown apps (Settings > Apps > Special app access > Install unknown apps), then open
iobridge-companion.apkfrom your downloads again.
Pairing
- "Pairing is not open": on the PC, click Pair a Device on the Mobile Companion card first. The pairing window stays open for a limited time and shows a countdown.
- PIN not accepted: enter the 6 digits shown on the PC. A PIN is valid for 2 minutes and allows 5 attempts; after that, start pairing again. Too many failed attempts from one phone block it for a while.
- Remove a phone: use the revoke button next to it on the Mobile Companion card.
3. Simulator & Anti-Cheat Compatibility
Mapped keys do nothing in the game
- Cause: The game runs as administrator and IOBridge does not. Windows does not let a normal program send input to an elevated window.
- Resolution:
- Start the game normally, without "Run as administrator". IOBridge never needs admin rights.
- Check the binding: open Notepad, press the mapped button, and see whether the key appears. If it does, IOBridge works and the game is not reading that key.
- Check the telemetry dock: every key IOBridge sends is listed there.
Anti-cheat
IOBridge sends keys with SendInput using hardware scancodes (KEYEVENTF_SCANCODE), like a real keyboard, and virtual controllers through the signed vJoy and ViGEmBus drivers. We know of no anti-cheat that blocks this, but we cannot guarantee how any game's anti-cheat behaves. Avoid macros that press keys faster than a person could.
4. Hardware Ingestion & DirectInput Issues
USB Device Disconnects & Sleep
Issue: Flight stick stops responding after leaving PC idle
- Cause: Windows Power Management put the USB root hub or controller into selective suspend sleep state.
- Resolution:
- Press
Win + Xand select Device Manager. - Expand Universal Serial Bus controllers.
- Right-click your USB Root Hub (or USB 3.0 eXtensible Host Controller) and select Properties.
- In the Power Management tab, uncheck Allow the computer to turn off this device to save power.
- Repeat for each USB Root Hub connected to flight hardware.
Issue: Hot-plugged controller not visible in IOBridge
- Cause: DirectInput lists attached hardware at startup or on an explicit rescan.
- Resolution: Use Rescan Hardware on the Monitor view, Tools > Rescan USB Hardware Devices, or Refresh Hardware Devices in the tray menu.
5. System Tray & Routing Status
The tray icon shows signal waves next to the joystick while routing is on, and a plain joystick while it is paused. Right-click the tray icon and use Input Routing: ON / OFF to switch it, or the routing switch in the main window.
6. FSUIPC7 & Flight Simulator Diagnostics
IOBridge works with Microsoft Flight Simulator (MSFS 2020 and MSFS 2024) through the user's own FSUIPC7. The free, unregistered FSUIPC7 is enough; no paid license is needed.
Diagnostic Health Checks
The FSUIPC health panel (under Dependencies, and as a status button in the Sim Action Picker) runs 7 checks:
- FSUIPC7 installed: found through the registry and its install folder. If missing: Download FSUIPC7 opens fsuipc.com.
- FSUIPC7 running: if installed but stopped: Start FSUIPC7.
- Connected to the sim: warns when FSUIPC7 is waiting for MSFS.
- FSUIPC7 version: compared with the recommended version (7.5.0 or later).
- Starts with MSFS: checks whether
FSUIPC7.inihasAutoConnectToSim=Yes. - FSUIPC WASM module:
fsuipc-lvar-modulein the MSFSCommunityfolder, needed for calculator code, L:vars, H:vars, and capture mode. It comes with the FSUIPC7 installer. - Registration: shown for information only (unregistered/free version is fully supported by IOBridge).
Presets and Custom Actions in the Sim Action Picker
- Cause: custom actions, L:vars and H:vars need
fsuipc-lvar-modulein your MSFSCommunityfolder. - Resolution: rerun the FSUIPC7 installer with the WASM module selected, use Open Community folder to confirm it is there, and restart MSFS.
7. Diagnostic Logs & Data Files
When diagnosing unexpected errors, server disconnects, or crash events, consult the log files recorded by IOBridge:
- Crash log:
%APPDATA%\IOBridge\crash.logrecords unhandled application exceptions, stack traces, and error details. - Stream Deck server log:
%APPDATA%\IOBridge\streamdeck_server.logtracks client connections, handshakes, and communication on port 28155.
For the complete guide to data file locations, protection mechanisms, deletion safety, and backup procedures, see data-files.md.
Technical Reference
Comprehensive technical architecture, network port specifications, Windows firewall rules, integration protocols, driver configuration, and local storage locations.
Network Architecture & Port Configuration
IOBridge embeds two independent, non-elevated background server engines (hosted via System.Net.Sockets.TcpListener and HttpListener) to facilitate local desktop automation surfaces and remote cockpit companion displays.
| Port | Protocol | Interface | Service Name | Access Scope & Authentication |
|---|---|---|---|---|
| 28155 | TCP (HTTP / WebSocket) | Loopback (127.0.0.1) |
StreamDeckServerService |
Local automation, Stream Deck plugin. Origin header check enforced. |
| 28156 | TCP (HTTP / WebSocket) | LAN (0.0.0.0) |
CompanionServerService |
Mobile Companion APK, cockpit tablets, OTA installer download (/download). 6-digit PIN handshake with Bearer token. |
| 28156 | UDP (Discovery) | Subnet Broadcast (255.255.255.255) |
CompanionServerService |
Answers discovery requests: a phone sends iobridge_discover over UDP and the PC replies with its name, port and version. The PC never broadcasts on its own. |
Set by Wave Link (from ws-info.json; 1884 to 1893 if not found) |
TCP (WebSocket JSON-RPC) | Loopback (127.0.0.1) |
Elgato Wave Link Client | Outbound client connection to Elgato Wave Link audio mixer. Queries channels and sends volume/mute RPC commands. |
| 9863 | TCP (HTTP REST) | Loopback (localhost) |
YouTube Music Desktop | Outbound client connection to YouTube Music Desktop Companion Server. Requires OAuth 4-digit token approval. |
Windows Firewall Setup (netsh Commands)
Port 28155 binds strictly to the local loopback adapter (127.0.0.1) and requires zero firewall modifications. However, the Mobile Companion Server on port 28156 and UDP discovery on port 28156 accept inbound connections from phones or tablets on your local Wi-Fi.
If Windows Defender Firewall prompts you upon first launch, check Private Networks. To configure or verify firewall access manually via an Administrator PowerShell prompt, execute:
Origin Validation & CSRF Security (Port 28155)
To prevent malicious web pages executing in your browser from toggling flight stick routing or injecting keystrokes into your running simulator via local port brute-forcing, IOBridge enforces strict origin filtering on all state-changing requests to http://127.0.0.1:28155:
- State-changing mutations (e.g.
POST /api/routing/toggle) require an explicitOriginheader matchingstreamdeck://*,http://127.0.0.1:*,http://localhost:*, orhttp://[::1]:*. - Requests originating from untrusted web browser domains or cross-origin requests lacking trusted headers immediately receive
403 Forbidden.
Mobile Companion APK: Setup & Pairing
The IOBridge Mobile Companion is a native Android application designed to sit on a secondary tablet, phone, or cockpit MFD mount. It displays live hardware telemetry, active operational modes, and allows real-time input rebinding without Alt-Tabbing away from your simulator.
Step 1: Over-the-Air (OTA) APK Download
IOBridge embeds an Over-the-Air file distribution server directly inside the desktop application. You do not need to connect your phone via USB or download tools from third-party app stores:
- Ensure your Android phone or tablet is connected to the same local Wi-Fi network as your gaming PC.
- Launch IOBridge on your PC, click the PLUGINS tab, and select Mobile Companion. Note your displayed local IPv4 address (e.g.
192.168.1.150). - Open Chrome, Firefox, or Samsung Internet on your phone and navigate to:
http://<PC_LOCAL_IP>:28156/downloadExample:
http://192.168.1.150:28156/download - When the download completes, tap
iobridge-companion.apkin your mobile notification drawer. - If Android displays an "Install Unknown Apps" prompt, tap Settings, toggle Allow from this source for your browser, and tap Install.
Step 2: Secure 6-Digit PIN Pairing Walkthrough
To prevent other devices on your home network from altering your flight controls, IOBridge pairs a phone with a 6-digit PIN shown on your PC:
- On your PC, open PLUGINS > Mobile Companion and click Pair a Device to open the pairing window.
- Launch IOBridge Companion on your mobile device.
- The app sends a discovery request on UDP port
28156; your PC answers within 3 seconds and appears in the Discovered Hosts list. - Tap your host name and press Connect. The mobile app sends a
POST /api/pair/requestcontaining its unique device ID. - A pairing window on your PC shows a temporary 6-digit PIN (e.g.
482 195) valid for 2 minutes (up to 5 attempts). - Type the 6 digits displayed on your PC into the prompt on your phone and tap Pair.
- The desktop verifies the PIN hash and returns an authenticated Bearer token. The mobile app stores this token in secure device storage and opens the interactive cockpit MFD.
Step 3: Network Discovery & Fallbacks
If your mobile app fails to discover your host PC automatically:
- Router AP Isolation: Many mesh routers or Wi-Fi guest networks isolate wireless devices from communicating with wired ethernet PCs. Ensure your phone is connected to the primary home Wi-Fi network and that "AP Isolation" or "Client Isolation" is turned off in your router settings.
- Manual IP Fallback: If UDP broadcast packets are filtered by your network hardware, tap Manual IP in the mobile app, enter your PC local IPv4 address (e.g.
192.168.1.150) and port28156, then tap Connect to trigger the PIN handshake directly over TCP.
Device Authorization & Revocation
You can inspect or revoke authorized mobile devices at any time:
- In IOBridge desktop, open PLUGINS > Mobile Companion.
- The Paired Devices table lists every authenticated phone or tablet with its device name, pairing timestamp, and last active ping.
- Click Revoke Access next to any device to immediately invalidate its authorization token and disconnect the remote session.
Stream Deck & Hardware Integrations
IOBridge provides official native support for the Elgato Stream Deck, Stream Deck MK.2, Stream Deck XL, Stream Deck+, and the 3-pedal Stream Deck Pedal.
Stream Deck Plugin Communication (ws://127.0.0.1:28155/ws)
The official IOBridge Stream Deck plugin runs inside the Elgato Stream Deck application background process and communicates directly with IOBridge via an asynchronous WebSocket connection:
- Connection Endpoint:
ws://127.0.0.1:28155/ws - Origin Header:
http://127.0.0.1:28155 - Bidirectional Feedback: The desktop app broadcasts JSON state frames whenever profiles change, modes shift, or master routing is armed/disarmed. Stream Deck keys update their icon and title states in real time without polling.
Stream Deck+: Dials as 16-Bit Analog Axis
The 4 optical rotary encoders on the Stream Deck+ can be mapped to continuous analog flight axes (such as Pitch Trim, Elevator Trim, Throttle, Flaps, Radiator Cowl, or Scanner Zoom):
- Step Sensitivity:
Fine (2%): Ideal for precise pitch and elevator trim wheels.Normal (5%): Standard response for throttle and mixture levers.Coarse (10%): Rapid actuation for flaps, shields, or power distributor triangles.
- Range Modes:
Bipolar (-1.0 to +1.0): Standard centered flight control surfaces (Pitch Trim, Yaw Trim, Rudder).Unipolar (0.0 to 1.0): Absolute forward sliders (Throttle, Collective, Mining Laser Power).
- Push-to-Center Reset: Pressing down on the rotary encoder dial instantaneously resets the virtual axis deflection back to neutral dead-center (
0.0).
Stream Deck Pedals: Digital-to-Analog Rudder Yaw
Many flight sim pilots own digital foot pedals (such as the 3-pedal Elgato Stream Deck Pedal) but lack dedicated analog flight rudder pedals. IOBridge solves this by converting discrete pedal switch inputs into a continuous, physical analog rudder axis:
- 60Hz Fast Lerp Physics Loop: When a digital pedal switch is pressed, IOBridge executes an internal 60Hz linear interpolation loop with a
0.22delta per frame (~160 millisecond transition rate). - Holding Left Pedal: Smoothly glides the virtual rudder axis from
0.0to-1.0without abrupt stepping. - Holding Right Pedal: Smoothly glides the virtual rudder axis from
0.0to+1.0. - Releasing Pedal: The virtual axis smoothly springs back to neutral (
0.0). - Dual Pedal Conflict Cancellation: Depressing both left and right pedals simultaneously cancels inputs and holds the axis at dead-center (
0.0) to prevent control conflicts during intense combat maneuvers.
Audio Engine & Media Plugins
IOBridge provides integrations with Elgato Wave Link and YouTube Music Desktop, allowing pilots to balance audio levels or mute microphones directly from their flight stick.
Elgato Wave Link Integration
Connects to the Elgato Wave Link audio engine via loopback WebSocket JSON-RPC 2.0 (port read from ws-info.json, otherwise ports 1884 to 1893):
- Pre-requisite: Elgato Wave Link software must be running on your PC.
- Channel Auto-Discovery: When connected, IOBridge queries all available software channels: Microphone In, Game, Voice Chat, Music, Browser, Sound Effects, Aux, and System.
- Continuous Axis Volume Faders: Assign physical rotary knobs or throttle levers to continuous volume control (
0%to100%). - Discrete Mute Toggles: Bind any joystick button, 2-stage trigger, or toggle switch to mute/unmute a specific audio channel.
- Monitor Mix vs Stream Mix: Choose whether inputs control the pilot local headset output (Monitor Mix) or the broadcast/recording feed (Stream Mix).
YouTube Music Desktop Companion (Port 9863)
Integrates with the official YouTube Music Desktop application via its built-in Companion REST API:
- Launch YouTube Music Desktop. Navigate to Settings > Integrations > Companion Server and ensure it is enabled (runs on port
9863). - In IOBridge, open the PLUGINS tab and select YouTube Music.
- Click Request Pairing Code. IOBridge issues a pairing request to
http://localhost:9863/api/v1/auth/request. - A 4-digit verification prompt will pop up inside the YouTube Music Desktop window. Click Allow.
- IOBridge receives the persistent authorization token and saves it to local app settings.
- You can now bind flight stick buttons to: Play/Pause, Next Track, Previous Track, Volume +/-, and Like Track. Live track title and playback status appear directly in the desktop app.
Windows Volume & Media Keys
For pilots who want audio control without third-party mixer software, IOBridge dispatches standard Windows media keys (volume up, volume down, and mute).
- Works universally with any audio device or output endpoint.
- Requires zero external servers, background drivers, or special software.
- Enables binding physical switches, buttons, or rotary encoders directly to system volume and mute toggles.
Virtual Drivers & Device Cloaking (HidHide)
IOBridge is a 100% user-mode application that feeds signed, industry-standard virtual joystick and gamepad drivers. It requires zero custom kernel-mode drivers and is fully compatible with Windows 10/11 Secure Boot.
| Driver | Label | What It Is For |
|---|---|---|
| vJoy | Required | Feeds virtual DirectInput joystick axes, buttons, and POV hat switches to flight and space simulators. |
| HidHide | Recommended | Cloaks physical gaming controllers from games to prevent device conflicts and double-input. |
| ViGEmBus | Optional | Emulates an Xbox 360 gamepad for titles requiring XInput controller input. |
vJoy Virtual Joystick Setup (Required)
- Driver Architecture: Feeds signals to
vJoyInterface.dll(vJoy 2.2.2.0, installed by the user). Supports up to 16 independent virtual joysticks, each with 8 axes, 128 buttons, and 4 POV hat switches. - Configuration Utility: Open
vJoyConf.exefrom your Start menu to configure virtual devices:- Enable vJoy Device #1.
- Check all desired axes (X, Y, Z, Rx, Ry, Rz, Slider0, Slider1).
- Set the button count to
32,64, or128. - Click Apply.
- Driver Fallback Guarantee: If vJoy is not installed on your system, IOBridge automatically activates an internal simulated loopback mode. You can build, edit, and test all mappings, curves, and macros without needing drivers installed.
ViGEmBus Virtual Xbox 360 Gamepad Setup (Optional)
Only needed if a game must see an Xbox controller. Gamepad output is less tested than vJoy output.
- Driver Architecture: Emulates an official virtual Microsoft Xbox 360 controller via
Nefarius.ViGEm.Client. - Use Case: Perfect for space sims or flight games (such as MechWarrior 5 or Star Wars Squadrons) that natively expect standard XInput gamepad thumbsticks and triggers.
- Verification: Open Windows Game Controllers by pressing
Win + Rand typingjoy.cpl. When routing is armed, "Controller (XBOX 360 For Windows)" appears in the active controller list.
Nefarius HidHide: Preventing Double-Input (Recommended)
When using physical flight sticks alongside virtual controllers, many simulators will detect both the physical joystick and the virtual vJoy feeder simultaneously. This causes severe input conflicts, double-firing triggers, and axis jitter.
- Download and install Nefarius HidHide. Launch the HidHide Configuration Client from your Start Menu.
- Step 1: Whitelist IOBridge (MANDATORY):
- Click the Applications tab.
- Click the + button and browse to
IOBridge.UI.exe(e.g.C:\Program Files\IOBridge\IOBridge.UI.exe). - Verify that
IOBridge.UI.exehas an active checkmark. (CRITICAL: If IOBridge is not whitelisted, HidHide will cloak the joysticks from IOBridge itself!)
- Step 2: Cloak Physical Devices:
- Click the Devices tab.
- Locate your physical USB hardware (e.g. Primary Flight Stick, Throttle Quadrant, Rudder Pedals).
- Check the box next to each physical hardware device.
- Step 3: Arm Cloaking:
- At the bottom of the HidHide client, check the box labeled Enable device hiding.
- Result: Your simulators now only see the clean virtual vJoy or ViGEm output devices, while IOBridge retains exclusive, low-level DirectInput access to your physical hardware.
Storage Locations & Game Binding Ingestion
IOBridge stores all configuration files, controller profiles, custom labels, and diagnostic logs in standard, user-accessible Windows application folders. No user data is written to the Windows Registry or remote cloud databases. All files use readable JSON or plain text formats that you can inspect, back up, or migrate between computers.
To create a complete backup of your configurations, or to transfer your profiles and settings to a new PC, copy these two folders:
%LOCALAPPDATA%\IOBridge\(machine preferences, profiles, and custom hardware labels)%APPDATA%\IOBridge\(personal FSUIPC presets, aircraft matches, paired mobile tokens, and logs)
Note on safety files: Inside these folders you may see files with .bak or .corrupt-<timestamp> extensions. These are safety copies created automatically by atomic writes. Copying them is optional.
1. Your Data (Back These Up)
These files contain your custom controller configurations, button names, operational profiles, and personal settings:
| File / Directory | Storage Location | Purpose & Persistence Behavior |
|---|---|---|
| Controller Profiles | %LOCALAPPDATA%\IOBridge\Profiles\*.json |
Stores individual controller profile JSON files (e.g. StarCitizen_Gladius.json). Stores all button, axis, hat, and dial bindings for each mode, response curves, deadzones, and sensitivities. Protected by atomic file replacement with .bak backups. |
| Application Settings | %LOCALAPPDATA%\IOBridge\settings.json |
Global application preferences: last active profile name, window size and position, dark theme preference, telemetry dock visibility, exit confirmation prompt state, favorite simulation actions list, and automatic aircraft profile switching settings. |
| User Device Database | %LOCALAPPDATA%\IOBridge\Config\device_db_user.json |
Custom user labels assigned to physical hardware in the Device pane, including custom device nicknames, button labels, and axis names. Never overwritten or reset during updates. |
| YouTube Music Integration | %LOCALAPPDATA%\IOBridge\ytm_config.json |
YouTube Music Desktop client connection details, port settings, and authentication bearer tokens for media player controls. |
| Paired Mobile Devices | %APPDATA%\IOBridge\companion_paired_devices.json |
Cryptographic authentication tokens and client identifiers for paired mobile companion devices on port 28156. |
| Aircraft Profile Matches | %APPDATA%\IOBridge\aircraft_matches.json |
Custom aircraft title matching rules configured in File > Aircraft Profiles & Auto-Switching for automatic profile switching upon loading a flight. |
| Personal Presets (My Actions) | %APPDATA%\IOBridge\fsuipc_personal_presets.txt |
Custom Microsoft Flight Simulator actions built with the My Actions Action Builder. Presets are stored in standard FSUIPC calculator code format with IOBridge metadata comments. |
| Pending Renames | %APPDATA%\IOBridge\fsuipc_personal_presets.renames.json |
Temporary mapping dictionary recording renamed personal presets so unopened profiles update when loaded. |
2. Logs
Log files record diagnostic information to troubleshoot hardware connections, network servers, or unexpected errors:
| Log File | Storage Location | Purpose & Diagnostics |
|---|---|---|
| Crash Log | %APPDATA%\IOBridge\crash.log |
Stack traces, timestamped exception reports, and diagnostic information from unhandled application errors. Appended when an unhandled error occurs. Safe to delete. |
| Stream Deck Server Log | %APPDATA%\IOBridge\streamdeck_server.log |
Diagnostics, client connection events, origin verification results, and WebSocket activity for the local Stream Deck plugin integration on port 28155. Safe to delete. |
3. Shipped with IOBridge (Read Only)
These read-only data files ship with the IOBridge installer in the application installation directory under Config\:
| Configuration File | Installation Location | Purpose & Shipped Asset Role |
|---|---|---|
| Common Actions | Application Root\Config\common_actions.json |
The 72 standard flight deck actions for Microsoft Flight Simulator (autopilot, flight controls, lighting, instruments, engines, radios). |
| Factory Template DB | Application Root\Config\device_db.json |
Factory hardware definitions, physical button and axis counts, and default layout labels for major flight sim peripherals (VKB, Virpil, Thrustmaster, Logitech, Honeycomb, Winwing). |
| Simulator State Sources | Application Root\Config\fsuipc_state_sources.json |
Pre-defined simulator variables, L:vars, and FSUIPC offsets used for the variable monitor and hardware read-back synchronizations. |
| Default Aircraft Match Rules | Application Root\Config\aircraft_match_rules.json |
Default regular expression rules matching simulator aircraft titles to profile names. |
| Variable Capture Filters | Application Root\Config\capture_ignore.json |
High-frequency or noisy simulator internal variables filtered out during variable capture sessions. |
| Controller Profile Templates | Application Root\Config\devices.json |
Built-in controller profile templates. |
Files Outside IOBridge's Folders
IOBridge interacts with external files and directories only when explicitly requested:
- FSUIPC
myevents.txt: Located in your FSUIPC7 installation folder (for example,C:\FSUIPC7\myevents.txt). Written only when you click Export to myevents.txt in the My actions builder. IOBridge appends personal preset calculator code to FSUIPC's custom event dictionary. - Elgato Stream Deck Plugin: Located in
%APPDATA%\Elgato\StreamDeck\Plugins\com.iobridge.streamdeck.sdPlugin\. Installed or updated only when you click Install Stream Deck Plugin on the Plugins tab. - Exported Binding Packs: Saved as
.ziparchive files at whichever directory path you choose in the Export Binding Pack dialog.
Native Simulator Binding File Paths
IOBridge automatically parses existing keybindings from major simulation titles on launch and exposes game actions as one-click assignment targets:
| Simulator | Detected File Path | Format & Action Ingestion |
|---|---|---|
| Star Citizen | %LOCALAPPDATA%\StarCitizen\...\actionmaps.xml |
Parses XML <actionmap> and <action> tags across LIVE, PTU, and EPTU channel installations. |
| Elite Dangerous | %LOCALAPPDATA%\Frontier Developments\Elite Dangerous\Options\Bindings\*.binds |
Scans for the latest Horizons and Odyssey 4.0 XML binding files. |
| MechWarrior 5: Mercs | %LOCALAPPDATA%\MW5Mercs\Saved\Config\WindowsNoEditor\GameUserSettings.ini |
Parses Unreal Engine INI CustomBindings and ActionMappings across Steam, EGS, and Game Pass. |
| MechWarrior 5: Clans | %LOCALAPPDATA%\MW5Clans\Saved\Config\Windows\GameUserSettings.ini |
Parses Unreal Engine 5 INI input action mappings across Steam, EGS, and Windows Store. |
| MSFS 2024 / 2020 | Detected install folders | The sim's default keyboard input profiles (fs-input-profiles) (XML). FSUIPC Common and My actions are usually the better route for MSFS. |
Low-Level Win32 Scancode Standard
When mapped inputs trigger simulated game keystrokes, IOBridge exclusively dispatches hardware OEM scancodes via the Win32 SendInput API with the KEYEVENTF_SCANCODE flag set.
- Keys are sent as hardware scancodes, like a real keyboard. We know of no anti-cheat that blocks this, but we cannot guarantee how any game's anti-cheat behaves.