Titan Bridge

Titan Bridge connects the current Helios controller path to a Titan Two and exposes the device's visible configuration and capture controls.

Device and Output

Step	Action
1	Connect the Titan Two to the PC and refresh the list.
2	Select the device and click Connect.
3	Leave Output on Automatic unless the console path needs a specific protocol.
4	Check the firmware, connection, and USB-port status.

The output list includes PlayStation 3/4/5, Xbox 360/One/Series X/S, Nintendo Switch, and Multi Interface HID.

Memory Slots and Input Translators

The panel shows the three supported Titan Two memory slots and the script/author/translator information reported for each one. While the bridge is connected, use a slot's menu to:

load a compatible GPC2 .git Input Translator;
load a local .gpc source or .gbc bytecode file;
remove the GPC script from the slot;
remove the translator.

You can also drag a compatible .gpc, .gbc, or .git file from File Explorer or Online Resources onto a slot. Helios compiles GPC source before loading the slot. Wait for programming to finish and the slot details to refresh before using it. Use Titan-compatible .gpc, .gbc, and .git files; GPC 3 files belong in the separate GPC 3 plugin.

Standard GPC headers, including console aliases, keyboard.gph, and mouse.gph, are bundled for source compilation. Slot loading and compilation before publishing use the same headers. Custom .gph files beside your source take precedence; a separate Gtuner installation is not required for these bundled headers.

Use Restart Bridge after changing device configuration when the status does not update automatically. Click Disconnect when the bridge is no longer needed. After a stop, select the device and use Connect or Restart Bridge again—start and restart both work while the bridge is stopped, as long as a device remains selected.

Script printf output

While Titan Bridge is connected, printf output from a loaded Titan GPC script appears in Helios as Info messages with the source Titan GPC. Enable the Info level in Output Panel to see them; the retained log history includes the same entries. Close Gtuner while Helios owns the connection so monitoring is not changed from elsewhere.

KMG Capture

The KMG Capture tab provides separate Keyboard, Mouse, and Controller Output selections. Choose the desired sources and click Start KMG Capture; the metrics card shows the live update rates.

Device Monitor and Visual Controller automatically show GPC 3 output while GPC 3 is active; otherwise they show the connected Titan’s report. MCP clients can inspect the Titan report separately when needed. A reported value is not confirmation that a game accepted it.

The run card’s CPU is Titan device load; CV is computer-vision data writes per second. These are not controller polling or console response-time measurements. Unavailable CPU data appears as --.

Device Configuration

Connect the bridge, then open the Titan Two configuration gear. The dialog reads the device’s current settings and offers:

input and output polling: protocol default, or 1, 2, 4, or 8 ms;
a custom device lightbar color;
force feedback enabled or disabled for each listed port;
Mouse DPI from 100 through 65,000, in steps of 100.

Mouse DPI tells Titan’s translator the physical mouse setting; it does not change the mouse sensor. Edits save automatically. Commit typed DPI with Enter or by leaving the field, then wait for Saved to Titan Two. If a save is not confirmed, reopen configuration to read what actually applied before changing it again. The PROG / Helios label reports the current USB speed; it is not a speed selector.

Firmware Updates

Helios checks for firmware when Titan Bridge loads, devices are discovered or refreshed, or another device is selected. The download icon becomes available when an update or P-mode recovery is offered. Close Gtuner before using the device from Helios.

Use the offered update action and follow the panel’s instructions. The bridge pauses during installation; do not disconnect the device while programming. Wait for the verified result and dismiss it before using Titan controls again. A previously connected bridge is restored after the result closes. If an update fails, inspect the message and reconnect or use the offered recovery action rather than assuming installation completed.

Troubleshooting

No device: reconnect the Titan Two directly and refresh.
Bridge stopped: select a device and click Connect or Restart Bridge.
Wrong console behavior: return Output to Automatic, or choose the exact target protocol when required.
Script or translator error: remove the file and load a compatible .gpc, .gbc, or GPC2 .git file.
No KMG activity: verify the relevant Titan USB ports and source checkboxes.
No script printf lines: confirm the bridge is connected, a script that calls printf is loaded, and Info messages are enabled in Output Panel.