Yes, but it shouldn't be too bad.I imagine they will take a performance hit on the emulator performance?
This. Robocod AGA seems to run fine at 1GHz (maybe 900MHz suffices already).or is that simply a case for throwning more muscle like the 1Ghz units at it and seeing does that fix it? (because the speed definitely improves at higher clockrates)
JP3 Operation Starfish was only available for AGA (and Sega MegaDrive).I can't recall if James Pond Operation Starfish got an AGA version, I've a suspicion it didn't
Man I love this community.Yes fixed that two hours ago. Will release a new version tonight.
JP3 Operation Starfish was only available for AGA (and Sega MegaDrive).I can't recall if James Pond Operation Starfish got an AGA version, I've a suspicion it didn't
You probably confuse this with JP1 Underwater Agent...
No, on start it'll set the cpu speed you've previously saved with general config in uae4all. If there is no general config yet then it'll just set the cpu speed to 600MHz.If the CPU speed is set upon boot up (like at present), will that speed be what's shown in the GUI too??(stupid question I know, but it's been a long day!!)
Yes with combined forces used for the greater evil we could make a change in this world!Imagine if the passion for the Pandora was used for evil not just good what we could accomplish
That's correct - savestates are broken in the current release.
Yesterday saw the functions save_cpu() and restore_cpu() (both are only a part of saving/restoring states) are empty in this new FAME/C-version.
Replaced the functions with the ones from the older FAME/C-release and now saving works, but restoring states still crashes the emu.
Could confirm that saving works correctly because the created savestate loads fine in the old UAE4All.
I'll later debug why restoring fails.
You should unset DISPPLAY before running the overclock script:I think I'll leave it at that and also change the PND-settings back from 800 to 600 to avoid the system dialog we get now.
system("unset DISPLAY; echo y | sudo -n /usr/pandora/scripts/op_cpuspeed.sh 800");
Okay.You should unset DISPPLAY before running the overclock script:
Code:system("unset DISPLAY; echo y | sudo -n /usr/pandora/scripts/op_cpuspeed.sh 800");
No idea, sorry.Any idea what I'm doing wrong this time?