How to read Titan Two inputs and outputs in Device Monitor

Capture one reproducible input

Connect Gtuner IV through PROG and open Device Monitor. Leave the controller idle, then press and release one button. For a stick, move along one axis and return to center. Using a repeatable input helps separate real changes from values produced by another connected device or another control you moved at the same time.

Plot the relevant signal when the immediate value is too brief to interpret. Gtuner IV includes plotting support for controller data, with the changelog documenting input and output plotting features and additional channels in later builds. A plot helps compare timing and neutral positions without treating a screenshot as the whole test.

Interpret the two sides of the trace

If input does not change, check the controller and input connection before looking for a script bug. If input changes and output changes on a different control, look at the active translator or script. If the expected output appears but the game does not respond, check the gaming system’s connection and in-game binding.

Compare a clean baseline with the same test on your programmed slot. Keep the controller, cabling and game settings fixed for both runs. One controlled difference makes the result more useful than changing the script and the device settings together.

Record enough context to reproduce it

Note the input you pressed, the channel you observed and the active slot. When sharing a bug report, include whether the symptom also appears with the slot unloaded. That detail often identifies whether another person needs your exact script or only your hardware layout to reproduce the problem.