Amiberry.sh ... latest script not parsing rom name

[mth75]

I noticed after the Amiberry upgrade to 5.3 from 3.3 that the rom name isn't parsed anymore to Amiberry - Configurations.

This means that if you want to make a custom uae file for a certain game you have to type the name of the game (or rather rom name) manually. This is quite error prone.

Could this function be restored in a new amiberry.sh iteration?

Best from The Netherlands!

system: Rpi4, latest and greatest RetroPie updates

[nemo93]

@mth75 Thanks for your report. Can you shed more light on that issue please? I do have no issue whatsoever while running either .uae, .chd or .lha straight from my frontend with latest Amiberry.

I expect your Retropie is up-to-date as well as your OS packages. Please share a clear example with as much details as possible so that I could try to replicate. Thanks!

[mth75]

@nemo93 Yeah, sorry ... I'm only running WHDLoad packages in LHA format.

Reproducing (on my side) is easy:

1. start a Amiga Game (WHDLoad lha) from within ES
2. go to amiberry interface
3. go to amiberry "Configurations"
4. and see ...

Under the name of the configuration entry you would normally see the Rom name which you started from within ES... now the rom (game) name isn't pre-parsed you always see the: default (.uae).

All other entries you can see are manually created.

My RetroPie is 100% up to date indeed.

[nemo93]

@mth75 Thanks for the additional details. Any reason why you have to rely on that many configurations? You decide to rely on .lha and that's the best choice in my opinion (I won't elaborate here). Good news is that Amiberry implements features to ensure users a smooth experience when using .lha's, this by default. You don't need specific configs/.uae unless you absolutely know what you're doing.

Let's focus on one game for the time being: Agony. First, let's delete the "autoboot configuration" file from Amiberry conf directory. You can backup that file just in case. Second make sure your Agony .lha retains the naming convention ie. Agony_v2.1_0960.lha as Amiberry uses it to identify the game (no longer true as Amiberry checks for the sha1 of the file but let's do everything by the book for now). Once done, start the game by pointing to the .lha and Amiberry will apply best settings automatically.

Let me know how it goes.

[mth75]

@nemo93 First of all ... thank your time and help.

I tried your suggestion ... same result (no auto id/parsing).

The reason I use many different configs is I often override the auto resolution ... to ensure I have the "correct" screen dimensions and controller configs (mostly to use the joystick port of my Keyrah)

[nemo93]

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

1. use the latest Agony "package" version as above (Agony_v2.1_0960.lha) and use that exact naming.
2. 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.