I have added a new image file at
https://drive.google.com/drive/u/0/folde...nlPS2M4czg that now includes settings that you can tweak for the LCD (located in /boot/freeplayfbcp.cfg). If you don't want to start with a new image file, but you do want to try this update, you can do it via SSH.
Code:
cd /home/pi/Freeplay/
mv rpi-fbcp rpi-fbcp_old
git clone https://github.com/TheFlav/rpi-fbcp.git
cd rpi-fbcp
./install
sudo shutdown -h now
Also, since this thread initially talked about overclocking, I had a look at
https://github.com/RetroPie/RetroPie-Set...erclocking and did some tests. Note that even in
https://github.com/RetroPie/RetroPie-Set...eed-Issues they mention that, "Some games, especially SuperFX and SA-1 games, will be slow on a stock speed Pi 1." Kirby is a SA-1 game.
-----------
I decided to try some FPS measurements with Mario World's and Kirby's intro sequence (with dtoverlay=pi3-disable-wifi and dtoverlay=pi3-disable-bt set and logging in via ethernet to change settings). I edited /opt/retropie/configs/all/retroarch.cfg and set fps_show = "true" to see the FPS.
These weren't very scientifically measured.
Mario World intro sequence
No mods:
60FPS
Kirby's intro sequence
No mods:
36-42FPS
Setting "FREEPLAY_SCALE_TO_VIEWPORT=0" in /boot/freeplayfbcp.cfg and rebooting
37-42FPS (seemed slightly less stuttery)
Setting the Raspberry Pi Zero overclocks from
https://github.com/RetroPie/RetroPie-Set...erclocking and rebooting [still with "FREEPLAY_SCALE_TO_VIEWPORT=0"] / We definitely don't condone overclocking, but I figured I'd try it just to see what it did.
40-46FPS
Both above tweaks plus set the render resolution to the smallest possible (via runcommand launch menu)
40-47FPS (seemed a bit better)
And, since I was at it, I decided to try it on a prototype Freeplay CM3. One can imagine that it'd be faster, since it's a faster CPU.
Testing on the Freeplay CM3 (No mods):
60FPS
