Frameskip skips the part where MAME renders the frames (and also input reading for skipped frames)null1024 wrote: Er, I dunno, because frameskip usually pulls the speed closer to 100%, which has been the case in everything in MAME for me until this, which appears to only slow it down because unlike normally, the graphics operations aren't what is slowing down on my machine.
Also, remember the guy who tried to run OSX in QEMU on a 68k era Mac? Yeah, doing this is a bit like that, except there's also the possibility of it actually working at a reasonable rate in this case.
In the case of the CaveSH3 driver the MAME rendering consists of 'Copy the bitmap the game rendered to the screen' which takes a fraction of a second, skipping it gets you nothing because the SH3 and blitter are doing all the work, and they can't be skipped.
Same for any primarily framebuffered game in MAME, Killer Instinct is just the same.