Collect the right files
Confirm that the author identifies the script as Titan Two or GPC2. The GPC extension also appears in older Titan One material. Keep the original download intact and make an editable copy. If the instructions mention a GPH header, GIT translator, GMK macro or an associated Python program, keep those files with the project and follow the documented locations.
Open the main GPC file in the Script IDE. Read the author’s controls and any requirements for an active slot or a companion app before building. Knowing the expected result makes it possible to tell whether the script is installed but waiting for an input.
Build, then program an unused slot
Compile the source in Gtuner IV and read the Output Panel. Fix the first build error before investigating runtime behavior. With Titan Two connected over PROG, use the install command for the active work and choose a spare slot. If you are starting with a supported Online Resources item, use Gtuner IV’s installation workflow for that package.
Select the newly programmed slot on the device after installation. If the work exposes Interactive Configuration, apply the settings to the corresponding slot. An editor tab with the file open is not evidence that its code is the one currently running.
Use a controlled first test
Choose a permitted offline test screen or controller diagnostic. Observe the requested input and the resulting output in Device Monitor. If the slot runs but only one feature is missing, check the author’s settings and associated files first. Keep the known working source and slot available when testing edits.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.