Hmm, just double checked and it still working okay on mine. I'll have to test at 50Hz, as I can't think of another differences. It does do some odd things to work out the screen refresh rate - as noted by the fact it doesn't work and thinks that 50Hz on the Pi is too high!Vanfanel wrote:-Overload shows a red message on the loading screen "Warning: screen rate is to high! Game will run too fast", and stays there playing the loader music.
Good, I suspect it's using FPU instructions then.Vanfanel wrote:-Magnetoids: This one works now! What a music! True MOD love there...
There momentary are gaps in the tittle music, once in a while.
I hadn't noticed it before but now you've mentioned it I'm not sure how I didn't notice it. They seem to be consistent at the same points in the music so I suspect a Tracker issue. It uses DSymphonyPlayer internally, which I've already had to patch up on two other games as it exits leaving IRQ/FIQ disabled - it was this that was causing the issues in Overload and Burn 'Out. Watching the CPU state under the debug build, I can see FIQ's are randomly being left disabled and IRQ's are always disabled at VSync.
These has been around since 2.55f, not sure how we missed it previously, I'll investigate.Vanfanel wrote:The regressions are still there.
Ending on a positive note...I received Arcade Soccer in the post today . I've imaged it, created the boot script and put it on the dev site, seems to work okay on the Pi. Not the best football game, but pretty rare as it's taken five years to locate a copy. I was seeing a random crash after pressing SPACE at the title screen on the RiscPC, although haven't reproduced it under emulation yet to diagnose.
EDIT: Lemmings etc are fixed in today's build - it was using the wrong MODE VIDC_list table on GPU's.