For the GTA IV test drives: a scripted L2 or R2 pulls the trigger axes
too (the profile binds them there, so a core reading the triggers saw
nothing); a SCREENSHOT is encoded on the task thread at zlib's fastest
level (port patch 0100; a 4K frame at level 9 held a thread about 20 s);
SAVE_STATE and LOAD_STATE take a slot number for that action only, so a
run can start from a second saved scene without replacing the first;
MARK prints the core's new frames and the longest gap between two since
the last MARK (port patch 0101 counts them), a run's frame rate over
exact script times. Two port patches more: the count test's 223.
Mihawk
f661b8dd00