UI Feature to Code Architecture Map

This master matrix directly ties every user interface control and feature in the IOBridge WPF desktop application to the exact XAML files, C# ViewModels, and backend service implementations that drive them.

It serves as the definitive reference for human developers, AI agents, and documentation writers to understand what purpose every UI component fulfills and where its operational logic lives.

Master UI Feature to Code Architecture Matrix

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.

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 beacon on port 28157 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 explicit Origin header matching streamdeck://*, http://127.0.0.1:*, http://localhost:*, or http://[::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:

1. Ensure your Android phone or tablet is connected to the same local Wi-Fi network as your gaming PC.
2. 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).
3. Open Chrome, Firefox, or Samsung Internet on your phone and navigate to:
   http://<PC_LOCAL_IP>:28156/download
   Example: http://192.168.1.150:28156/download
4. When the download completes, tap iobridge-companion.apk in your mobile notification drawer.
5. 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 uses a cryptographically verified 6-digit PIN handshake modeled after modern streaming media hardware:

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 port 28156, 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):

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.22 delta per frame (~160 millisecond transition rate).
• Holding Left Pedal: Smoothly glides the virtual rudder axis from 0.0 to -1.0 without abrupt stepping.
• Holding Right Pedal: Smoothly glides the virtual rudder axis from 0.0 to +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 zero-latency integrations with professional audio mixers and desktop media players, allowing pilots to balance audio levels or mute microphones directly from their flight stick.

Elgato Wave Link Integration (Port 1824)

Connects to the Elgato Wave Link audio engine via loopback WebSocket JSON-RPC 2.0 at ws://127.0.0.1:1824:

• 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% to 100%).
• 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:

Windows Core Audio (WASAPI)

For pilots who do not use specialized mixer software, IOBridge communicates directly with the Windows Multimedia Device API (WASAPI):

• Requires zero external servers or background drivers.
• Allows binding physical controls to Master System Volume (mute toggle, volume increment/decrement, continuous fader) and Default Communications Microphone mute.

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.

vJoy Virtual Joystick Setup

• Driver Architecture: Feeds signals to vJoyInterface.dll (WHQL signed driver). Supports up to 16 independent virtual joysticks, each with 8 axes, 128 buttons, and 4 POV hat switches.
• Configuration Utility: Open vJoyConf.exe from 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, or 128.
  • 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

• 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 + R and typing joy.cpl. When routing is armed, "Controller (XBOX 360 For Windows)" appears in the active controller list.

Nefarius HidHide: Preventing Double-Input

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.

Storage Locations & Game Binding Ingestion

IOBridge stores all user configurations, custom button labels, and operational profiles in standard Windows local application storage. User customizations are strictly separated from factory templates to guarantee that application updates never overwrite user settings.

Configuration & Profile File Locations

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:

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.

• This ensures total compatibility with modern anti-cheat systems (such as Easy Anti-Cheat in Star Citizen and BattlEye in Arma).
• Keystroke signals appear identical to physical keyboard hardware interruptions, avoiding the detection blocks associated with legacy keybd_event injection.