You could just get rid of the symlink-ed Kickstarts and keep them as files in the whdboot/save-data/Kickstarts folder. Amiberry should still work and the files would be backed-up like regular files.

@skidiver Cool. Glad you found a solution. As a courtesy for other users (and search engines) please mark your subject post with something like [solved].

EDIT: i maybe didn't test enough -- the "remaining values are filled" in the .conf, only when run the +Start Amiberry.sh. When launch by one of the .lha roms instead, no values are filled, but the game still seem to work. They load and play anyway, did not test saving. But it's late and I've shut down for the night. Will test saving tomorrow.

Yes, saving works:

pi@retropie:/opt/retropie/configs/amiga/amiberry $ cat conf/amiberry.conf rom_path=/home/pi/RetroPie/BIOS/amiga floppy_path=/home/pi/RetroPie/roms/amiga harddrive_path=/home/pi/RetroPie/roms/amiga cdrom_path=/home/pi/RetroPie/roms/amiga lha_path=/home/pi/RetroPie/roms/amiga pi@retropie:/opt/retropie/configs/amiga/amiberry $ ls -l whdboot/save-data/Savegames/ItCameFromTheDesert/ total 16 -rwxr----- 1 pi pi 12444 Dec 20 11:36 ICFTD pi@retropie:/opt/retropie/configs/amiga/amiberry $ file whdboot/save-data/Savegames/ItCameFromTheDesert/ICFTD whdboot/save-data/Savegames/ItCameFromTheDesert/ICFTD: data

...save file exist, and I can quit and restart amiberry, then re-load the save in-game.

It's the same with either github/retropie version binary: no values are written (and file NOT created) when loading from .lha rom, saves still work at default location. Values are written (and file is created, with github version) when launch from +Start Amiberry.sh.

Edit: Launch from .lha rom, then open amiberry config and change eg. Rom path: all values are written to file (for both RP version with minimal conf, or github version with no conf.) But, if open config then quit with no change == no write values.

@Alfa How did you solve the problem?

I have now gained new insights into the VSync problem, because it seems that the TV or the HDMI detection is really to blame. I just had my Raspberry Pi connected to my 13-year-old Panasonic 3D TV and the VSync option works exactly as it should. What I also noticed is that the screen modes are swapped in the video setup menu, which you can select when selecting a game before starting Amiberry via Retropie. On my old TV, the 50 Hz modes are first in the list and only then do the 60 Hz entries follow. On my Philips TV from 2014, it is the exact opposite, so that I have to set the correct mode every time I change TVs. However, it does not seem to take the 50 Hz modes into account at all or does not switch despite the selection and only runs at 60 Hz instead of 50 Hz, which I find very strange, because the TV is definitely capable of handling both refresh rates. This also works with all other emulators, whether with VICE (C64) or all RetroArch cores such as NES, SNES, Mega Drive, Arcade, etc. Just not with Amiberry, which I find very unfortunate. The Retropie team would probably have to release an update to detect the connected screen in the Amiga Setup Menu. I actually thought that HDMI screens were all standardized by now and the only explanation I can think of is that it has something to do with an error in the setup script for Amiga core.

I had the same problem.
In the bottom of this link is my solution. Generel advice is to make a backup before updating RetroPie.
https://github.com/BlitterStudio/amiberry/issues/1392

@mitu Hotkey + X worked, changed Sound to HDMI, perfect. Thank you both!

@mitu ah I shall try that many thanks buddy:)

@mitu thanks a lot. 5.6.4 has been released with many fixes indeed!

Hi @KingZambo

Amiberry did have an issue and has just been fixed in v5.6.4 that was released yesterday. I'm updating as we speak and will hopefully be back on track.

For puae-2021, I amended the gamelist.xml and added an entry that points to my .hdf file. After I realised my kick roms were named wrong (I had to remove the .rom extension.... Doh!) then puae-2021 is now working.

Can you add more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

Does this happen to all games or just a few games ? Which version did you have installed before the update (or when was the previous time you updaed) ?

I think the Bios changed position. It is now in home\pi\retropie\bios\amiga and it must contain

Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom
Kickstart v2.05 rev 37.350 (1992)(Commodore)(A600HD).rom
Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom

I am not sure about the 600 rom if it is necessary though.

@Sfora hello! Which version of the games are you relying on? I trust it's the .lha version, right? I just tried ChambersOfShaolin_v2.0_3049.lha as well as DizzyPrinceOfTheYolkfolk_v2.0_1146.lha and both work without any issue on a similar setup.

If you're seeing the Amiberry logo instead of a typical WHDBooter page whenever you run a game then something's off on your setup. Please make sure to use the .lha as-is do not rename these files.

amiberry.log is the right place to look for errors. Feel free to share it. Then ensure you're using the exact same KickStart mentioned on that page. Also do not hesitate to read the wiki for further details about WHDLoad/WHDBooter.

Hope this helps.

@mitu said in amiberry second joystick fire button:

@22marco77 Make sure you update the RetroPie-Setup script first, if you want to install from source. You can also update from binary the amiberry package, the binaries have also been updated to version 5.6.1

Ok thanks for the information. Can't wait to update I'm super excited to resume challenges to sensible soccer

@preciouscattle

What type of Amiga ROMs are you using? If you're using WHDLoad packages you should just be able to load them like any other ROM (eg direct from the ROM list).

The only time I got a black screen was because I'd messed up the kickstarts - do you have the correct ones?

@Turrican2k I had the same problem, played with all settings but none of them did the trick. Only downgrading to 3.3 worked for me.
ssh to the system then

wget https://github.com/BlitterStudio/amiberry/releases/download/v3.3/amiberry-v3.3-rpi3-dmx-32bit.zip unzip amiberry-v3.3-rpi3-dmx-32bit.zip cp amiberry /opt/retropie/emulators/amiberry/ cp capsimg.so /opt/retropie/emulators/amiberry/