Amiberry default config and saving changes to it

[TimZett]

When I start the configuration during loading of any game, for the default emulator I see entries:
amiberry a-1200
amiberry a-500
amiberry

Which one should be used as the default emulator?

The second question, when I choose "+START AMIBERRY" from the Retropie screen, whatever changes I make in the upcoming configurator, e.g. to the Custom controls (joystick mapping) they are never saved: Next time when I open it all changes are gone again.
What is causing this?

[TimZett]

...noone here dealing with Amiga stuff? :-)

[dudleydes]

@TimZett It would be helpful if you could provide information regarding your system, in particular whether you are using WHDLoads or disk images such as ADF.

There is also extensive documentation at https://github.com/midwan/amiberry/wiki.

[TimZett]

@dudleydes I use .adf files in ZIP containers.
Thanks for the links. I will have a closer look, especially to the controller definition in an own .cfg file documented here: https://github.com/midwan/amiberry/wiki/Setting-up-Input-Controllers

The only thing which is still puzzling me: Why are my joystick mappings from the Amiberry panel not saved? Well, maybe I have some wrong paths defined in there.
I will check all these things an will post an update afterwards.

[TimZett]

I need your help in this again (maybe someone is using a gamepad, preferably Sony PS3, with Amiberry)

Today I reconfigured my paths in the Amiberry GUI, according to the following documentation:
https://github.com/midwan/amiberry/wiki/Setting-up-Input-Controllers

First problem: I am wondering what the guy meant when he wrote:
"From the Amiberry GUI you should navigate to the Paths panel. From here you will need to select the location where your .cfg file(s) have been stored.
For RetroPie, you should select /opt/retropie/configs/all/retroarch/autoconfig/"

=> Did he mean this statement for Configuration files: or Controller files: or Retroarch configuration file (retroarch.cfg) ??
(at the latter you need to specify the file with, not just the path so maybe at least he didn't mean that one)

Anyway, thanks to my changes, after pressing "Rescan Paths" my Sony PS3 gamepad entry was gone for good in both the Input and the Custom controls panel :-(

I have defined my paths as follows now:

• Configuration files: /opt/retropie/configs/amiga/amiberry/conf/
• Controller files: /opt/retropie/configs/all/retroarch/autoconfig
• Retroarch configuration file (retroarch.cfg): /opt/retropie/configs/amiga/amiberry/conf/retroarch.cfg

Is this "best practice" at all, considering I am then dealing with 2 different "construction sites" regarding retroarch.cfg?

The only input devices for "Port 1" respectively "Joystick" I can still see now are:
None,
Mouse and
Retroarch Keyboard as Joystick [Input #

The problem connected to this is that now, in the Custom controls panel there is a read-only entry for Input Device saying:
"Not a valid input Controller for Joystick Emulation."

In which file does Amiberry actually store the settings from the Amiberry GUI?
Because I am considering to restore that settings, which seem to be fully messed up now.

As you might remember, before when my PS3 controller still showed up in the GUI, whenever I changed the controller button assignment in the "Custom controls" section it never saved my changes...

Is there anyone who successfully got a PS3 controller to work with Amiberry, and if yes can maybe give a kind of step-by-step description of what needs to be done to get it to work?
The already existing documentation, IMO is either misleading or incomplete (see above).

I almost reached the point where I fully give up with Amiga games on Retropie, just because I don't get the controller to work.

P.S. I switched back to the default rp-a500 Amiga emulator configuration

[TimZett]

UPDATE:
I was able to reset my Amiberry configuration GUI by renaming (or deleting) the file:
/configs/amiga/amiberry/conf/adfdir.conf

Now my PS3 controller shows up again.
I will keep on playing around with this and keep you posted.

[TimZett]

OK - one step further and new problems... whate else to expect from Amiga emuation? :-)

So I am at the point where I recognized I need dedicated .uae files for each game .adk/.zip:
https://retropie.org.uk/forum/topic/19302/tutorial-painless-amiga-emulation-using-amiberry/2

Now the problem I have is, and maybe that is because I have outsourced my game files to a USB stick, that Amiberry (and only this EMU for now) cannot browse for that ROM folder.
Whatever I try to browse for at the Floppy Drives section in the Amiberry configuration screen, I can't come further than /home/pi/RetroPie, because there is no folders or files displayed - weird.

Anyone here having the game ROMs on an external drive and use Amiberry?

[LineOf7s]

I was having similar problems (settings I'd changed not saving in the default config) until someone told me to update Amiberry from source rather than from the binary. Once I did that, my problems (with that, anyway) went away.

So... try that. :)

[TimZett]

@TimZett said in Amiberry default config and saving changes to it:

Whatever I try to browse for at the Floppy Drives section in the Amiberry configuration screen, I can't come further than /home/pi/RetroPie, because there is no folders or files displayed - weird.

This one still applies, even after updating Amiberry from source.
@LineOf7s: Are you running your game ROMs from the internal SD card where Retropie is installed, or do you have them on a drive (or stick) attached to USB?

With FTP I can browse the folder just fine: /home/pi/RetroPie/roms
Only within Amiberry setup screen the roms folder doesn't show up.

EDIT: The custom controls get stored now according to my custom "Configurations" but apart from that, without ROMs folder no games...

[LineOf7s]

@TimZett I've done both, but I'm currently running my ROMs from a USB stick.

[TimZett]

@LineOf7s Well then, probably the fact that my USB stick is formatted as exFat.
I guess I'll give it a break with Amiberry for a while.
Anyway, I am just updating my system, including the big one (second list item from the RetroPi-Setup Script). Given I get my PS3 controllers working on Bluetooth again afterwards, maybe Amiberry also behaves differently :-)