Titan Two KMG Capture: route computer inputs through Gtuner IV

Establish the host path first

Confirm that the computer sees the keyboard, mouse or controller. Connect Titan Two to the computer through PROG and check device recognition in Gtuner IV. Open KMG Capture and select only the input types and device you mean to capture. The official changelog documents device selection for supported gamepads and joysticks, alongside keyboard and mouse capture.

Find the configured capture exit shortcut in Preferences before starting. A deliberate way to leave capture makes it easier to move between the game test and desktop settings without unplugging hardware.

Add the matching translation

Start with a single input, such as one key bound to a known controller action. Use the matching translator if you need keyboard or mouse conversion. Watch Device Monitor while you press that key. A captured key reaching the device and a mapped action reaching the console are separate points you can test.

For mouse input, compare a short slow movement and a faster one under the same profile. A capture setting decides whether movement reaches Titan Two. A conversion profile decides how it becomes stick output. This distinction matters when movement is detected but the in-game response feels different from the expected curve.

Compare against a direct connection if capture fails

Disable capture before testing the same input directly on Titan Two, if the device is compatible with direct use. Record which path worked and which settings were active. That narrows troubleshooting to host capture, direct compatibility or the common output path instead of treating both setups as identical.