Remap controller buttons on Titan Two with Gtuner IV

Write a short map before changing the profile

List the physical button you plan to press and the output you expect the game to receive. Use the controller’s label or the Gtuner IV input reference where the platform names differ. Decide whether you intend a swap or a one-way reassignment. Verify what should happen to the original action on both buttons so an essential menu control remains reachable.

Test the original control first in Device Monitor. This catches a controller-side profile that already changes what the physical button sends. Keep your platform and in-game layout settings fixed while comparing the two configurations.

Configure only the intended input

Open Controller Remapper within Input Translator and apply the smallest change that meets the layout goal. Gtuner IV supports restricting the remap to selected controller inputs. If an original controller is connected as part of the console setup, confirm that the mask applies to your playing device.

ConsoleTuner’s changelog documents paddle mappings in later versions of Gtuner IV. Check Device Monitor to see whether your controller reports a separate paddle signal. A physical paddle that sends the same input as another button may not produce a separately observable control in your setup.

Verify the whole button cycle

Select the programmed slot and press, hold and release each changed control. Compare the input channel to the resulting output and check that a released button returns to idle. Repeat the test with the slot unloaded if the game shows a different action than the one you intended.