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

@BuZz thank you for the extra pair of eyes. I'm on a version from a week ago, but indeed going over github commits the version changed recently from 3.3 to 5.1 in the meantime.
And indeed that commit includes the change:
"Move rom location for amiberry/uae4arm/uae4all to $biosdir/amiga".

@mitu your setup works because your emulationstation is running from the environment spawned by getty@tty1 and inherits its environment, including standard input and output.

With systemd, services do not inherit the environment of another service. So a process that owns tty1, like login will prevent other processes from other services from using that descriptor, especially when the other processes are non-root, like emulationstation.

I found when running getty as a systemd service, the instance getty@tty1 needs to be stopped fully (including a stale login process that getty instances seem to leave behind) before emulationstation can make use tty1 for standard input and output. Instances on other tty's may be left as is.

The following entry in emulationstation.service will stop getty@tty1 if running:

ExecStartPre=+sh -c 'systemctl is-active getty@tty1 && systemctl stop getty@tty1 || systemctl reset-failed getty@tty1'

ps auxf shows the tty a process is running with.

@nemo93 I fixed by deleted some whlload dirs, emulation works for me again.

@Floob
Thats a good idea. I will try that next. I will use a clean retropie setup and install amiberry there.

Not sure what config files i have to look for though
Im pretty sure i wiped everthing that could have anything to do with amiberry before i installed 5.0 (or 5.1) from the setup script.

I've just tried with google kickstarts and it work !

Alright, I was able to select the second joystick in the in-game configuration - thanks for everyone who helped, it's working now!