Read the Gamepack’s own instructions
Identify the intended game or use case, the supported input layout and any instructions about activation. Before you install it, compare those assumptions with the controller layout you already use. If the author expects a specific action on one button and your game binds that action elsewhere, the two layouts can disagree even when the Gamepack is running.
Select a package meant for Titan Two. ConsoleTuner publishes software and resources for more than one device generation, so similar titles do not identify the correct version by themselves.
Make the configuration on a test slot
Connect Titan Two over PROG, locate the Gamepack in Gtuner IV and install it in a spare memory slot. Open the Interactive Configuration for that slot when the package provides it. Record the defaults or save a copy before changing multiple options. Apply one change, then select the slot and check the result in a permitted local test.
When changing versions, reopen the configuration on the new work. An author can rename, add or remove settings, and a configuration string from a previous revision can describe a different collection of values. Treat imported settings as a starting point you still need to verify.
Trace a setting that appears to do nothing
Confirm which slot the hardware is running. Next, check the author’s activation instructions and reproduce the expected action while observing input and output in Device Monitor. If the output differs from the expected result, return to the Gamepack’s settings and the game’s control layout before changing global Titan Two hardware settings.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.