@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/

@nemo93 Yes, the link works fine. Thanks for the hint. Unfortunately, this worked better in older versions of amiberry.

Did the op get this fixed? This happened to me and it was (doh) because I'd just moved everything over to a new flash drive but I'd forgotten to copy the kickstarts across...

This does sound like a kickstart issue - either the required files aren't there or they're named wrong.

@nemo93 Ok thanks anyway.
I opened a topic on GitHub.
https://github.com/BlitterStudio/amiberry/issues/1022#issue-1405758532

@George-Spiggott I switched up some of the games to the new Amiberry. Wow, it's a lot better now and very easy to use.

It's been a while since I used it, and the last time I had a lot of issues with controllers being properly recognized. Now, no interaction required. One-click, and I'm playing.

I also did some performance tests between the two with A-10 Tank Killer, Knights of the Sky, Bonanza Bros, and PowerMonger.

Nearly the same performance between the two, Bonanza Bros definitely ran a little better on Amiberry Angina 500+ setting.

But other than that, they're equal. That was with overlay and shaders active on lr-puae-2021.

@max I do confirm since Amiberry 5.x the KickStart roms must go to:

/home/pi/RetroPie/BIOS/amiga

Thanks for pointing that out. Amiberry's documentation has been updated accordingly. KickStart names don't matter any longer as I explained in that other post.

Irrespective of the emulator you go with I wish you to enjoy all the great memories of the Amiga!

@mth75 anytime. I suspect something's wrong with your setup. Agony should have launched without issue and with proper settings. Usually this points to an old amiberry.conf. Please ensure to:

use the latest Agony "package" version as above (Agony_v2.1_0960.lha) and use that exact naming. backup then delete your amiberry.conf from the "conf" directory. Reinstall Amiberry from Retropie-Setup.

This should definitely fix your issue and allow Agony to run as it should with proper defaults. If this works we would continue from there.

@iss05e said in Amiberry - no sound through headphone jack:

The previous version of Amiberry inherited the Audio options set in RetroPie. I guess Amiberry v5.3 no longer does this.

It didn't, it was just a concidence that it worked. It probably just used the 'default' (which is set via the RetroPie audio settings).

You can rename the configuration file (amiberry.conf, in /opt/retropie/configs/amiga/amiberry/conf) and start again the emulator.

@Rinusch thanks again for rephrasing despite my clear lack of understanding. You did right by raising a ticket directly. Somehow I'm still convinced your issue is related to the one I've mentioned earlier about the custom controls. Anyhow thanks for your patience.

@mitu Thanks for that! I edited that file as described, rebooted and remapped my joystick. Now I'm only seeing one "SNES-to-Gamepad Device" in Amiberry and RetroArch emulators and I'm controlling player #1 in the games I tried so far. This is outstanding, I'm very pleased with this setup now. :) Cheers!

@mathan416 said in Amiberry - Using --model when launching:

Amiberry on RetroPie does not bring up the proper model with the appropriate ROMS, etc.

The entries in emulators.cfg are meant to be toggled manually, from the runcommand menu, by the user. They're not assigned automatically when you run a game.

However, if you're using the default amiberry emulator (i.e. no model), then it will attempt to guess the model needed based on the filename launched.

BTW it's like I'm hitting F12 using the right dpad button. :/

Hi, I have the same issue (frozen Black Screen with mouse arrow at top left) with all packages updated to the latest version. Any solutions in the meantime? Thanks!