Locate the point you want to change
Open a copy of the GMK file. Find the controller channel and time range associated with the behavior you want to adjust. Read the states immediately before and after that range. A timing edit is easier to check when you know the press and release that bound it, rather than selecting a segment based on the visible game effect alone.
Decide whether the issue belongs in editing or recording. A single extra delay is a good reason to edit a saved timeline. An entire sequence captured from the wrong menu state may be quicker and more reliable to record again.
Treat each timeline tool as a separate change
ConsoleTuner’s release notes describe editing tools for selecting nodes, adjusting speed and working with interpolation. Apply one kind of edit at a time. Changing speed affects timing, while interpolating analog values can affect how movement transitions between recorded states. Test the changed segment and the moment it rejoins the rest of the recording.
Save a new version with a name that identifies the intended change. Keep notes on the reference start state and whether the edited sequence ends with every control released. This makes a playback issue easier to repeat without reverse-engineering the entire file.
Confirm the edited file is the one being played
If a slot or script refers to a specific GMK filename, verify that the installed file and the configured name match. Test from the same start state as the source recording in a permitted local session. Compare the controller output around the edited section against the original before replacing your known working copy.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.