Strange dual screen with Pi games...
Stevyn Gadd (2272) 63 posts |
Hi all, I’ve been enjoying playing Botkiller 2 recently (well, until getting stuck on Level 3! Where’s this secret passageway??) on my RISC OS Pi with Aemulor. One bit of strangeness though, is that the display is “in stereo” – repeated twice as two smallish outputs in the top half of the screen. It’s still very playable even like this which must be testament to the game somewhat! I’ve noticed the same thing when trying e.g. Populous under ADFSS. Does anyone know what I’m doing wrong? I suspect it’s something missing in the config.txt file but I haven’t found an equivalent description of the problem. Any help (incl. tips on how to get past this leve!) greatly appreciated. Stevyn |
Jon Abbott (1421) 2651 posts |
You probably want to post on the JASPP forum for ADFFS related questions, however… As you’re seeing dual screen with Populous under ADFFS, either the 4bit blitter isn’t running or you don’t have a new enough RISC OS ROM. 1. Ensure you’re running a recent RISC OS alpha build, as ADFFS requires several features that have been added to RO this year. On the page you downloaded the ADFFS beta, it details changes required to config.txt if you want to change the Pi’s upscale method, or fix it to 50Hz for smooth scrolling etc. Botkiller 2 – I’ve not tested it under ADFFS so can’t confirm this will work: You can turn on the blitter by adding “GOARM3JIT 0” to the !Run, after any “WimpSlot” command and before the game run entry. |
Stevyn Gadd (2272) 63 posts |
Thank you! I’m currently running 5.21 (08-Jul-13) so that might well be the issue. |
Chris Evans (457) 1614 posts |
Are you sure? I thought 5.21 didn’t exist until after 5.20 was released on 24 July 2013. |
Frederick Bambrough (1372) 837 posts |
5.20 – 24 July 2013 Seems there was an overlap. |
Jeffrey Lee (213) 6048 posts |
Indeed. July 24th was just the release date for 5.20, the actual ROMs were built days/weeks earlier. What happens is that the kernel is briefly bumped to an even version number, a snapshot of CVS is taken (actually, just the version tags for all the components), and then the kernel is switched back to an odd version number, ready for development of the next OS version to begin. This allows the stable release to be tested while still allowing for a (moderate) amount of development to continue in CVS (during a release cycle, changes are generally kept to a minimum to simplify the handling of any bug fixes). And if the kernel version is only briefly set to an even number, it stops the autobuilder from churning out lots of unofficial even-numbered ROM builds! |