No wonder I was struggling to find the time in memory - the tenths are based on a byte that counts from 0 to 59 over and over as I expected, but the minutes and seconds use their hex values rather than decimal values, e.g. when the timer ticks up from 9 to 10 seconds, you'd think the hex would increment from 09 (9) to 0A (10), but instead it jumps to 10 (16). Turns out it's the same for your position in the race, too.

Making good progress. Now I've figured that out, I've got it outputting IGT when you split, which was my end goal with this all along.

Still a few bugs to work out - during my testing I've had a couple of instances where the timer has registered a time 0.1s more than what's shown on the race results screen. I'm guessing it's a rounding issue due to the framecount and I just need to round down (e.g. finishing on frame 5/60 would round up from 0.08333 to 0.1 in LiveSplit and the results screen in-game would show 0.0 because I was still under 0.1) but I need to confirm that's actually what's happening before I go fiddling about.

This is very much in the experimental stage at the moment, but if anyone wants to try an autosplitter, I've made one available on github: https://github.com/Dalimyr/RoadRash2Autosplitter

It supports auto-starting the timer when you press the start button on the title screen, it auto-splits as soon as you cross the finish line, and it auto-resets if you hard reset Kega Fusion.

I was hoping to be able to get something that could automatically record in-game time since that's how we're ranked, but I'm really struggling to find the memory associated with the timer. Hopefully with a little more digging I might find something useful but for now the splitter just handles the real-time timer.

There are also some issues I'm aware of that would need to be fixed at some point - most notably the auto-start is set to trigger when the title screen starts to fade out...but it triggers regardless of whether you pressed start on your controller or it's about to start playing the rolling demo (both of which will cause the screen fade-out)

When I finish work tonight I'll release an updated version that will only split if you finished high enough in the race to qualify, now I've figured out a way to handle the garbage data that the position variable gives me.