Amiberry 5.1 controller mapping problem (since upgrading from 3.x)

Rinusch

@mitu I'm sorry, you're right..

nemo93

@mbernier thanks for reporting back. I see few issues with your setup.

Kickstart ROMs have to be stored under > /home/pi/RetroPie/BIOS/amiga/
you should have a <controller_name>.cfg file under /opt/retropie/configs/amiga/amyberry/conf/
=> in your case it should be named after Logitech Gamepad F710.cfg
=> check that wiki page to be sure of the format as yours look to have many lines (there's an example at the bottom). Some lines/parameters are not even required. Please clean that file up and make sure it's located in /opt/retropie/configs/amiga/amyberry/conf/.

To wrap things up, your /opt/retropie/configs/amiga/amyberry/conf/ should contain the following files:

amiberry.conf
retroarch.cfg (in fact a symlink to /opt/retropie/configs/all/retroarch.cfg)
Logitech Gamepad F710.cfg (or any name matching your controller)
you may have 2 other default config files A500 and A1200 which are optional

Regarding your issue with Thexder do the same steps as above (ensure no .uae, run the game, assign some custom controls) but this time save the config. Open GUI > Configuration > click Save as a name should be already set for you. A file named Thexder_v1.2_0392.uae will be created in /opt/retropie/configs/amiga/amyberry/conf/. Re-run the game and see how it goes.

Not sure to understand your issue about Turrican as this looks expected. Like many Amiga games it's a one-button joystick game hence why only the fire button will work by default on your controller. There's no custom controls for that game set by default by Amiberry. You'll have to assign a custom control for binding space key to your controller.

Assuming your issue is sorted I'd like to add more custom controls to Amiberry (so that custom will be there by default and available to all users). Thus far there's only a few games with custom (list). If you're willing to help let me know. Don't worry all I require is the same as you provided above, eg. for game XYZ:

joyport1_amiberry_custom_none_b=Left Shift

Hope this helps.

mbernier

@nemo93

Good evening,

Thank you for reply :-)

I have done all the changes you proposed:

system ROM = /home/pi/RetroPie/BIOS/amiga
Configuration files = /opt/retropie/configs/amiga/amiberry/conf/
https://pastebin.com/qync2PGq (retroarch.cfg)
https://pastebin.com/yx6z6Y3n (amiberry.conf)
Controller files = /opt/retropie/configs/amiga/amiberry/conf/
https://pastebin.com/r4QUW3Kb (Logitech Gamepad F710.cfg)
RetroArch configuration file = /opt/retropie/configs/all/retroarch.cfg
https://pastebin.com/xa6scLqY (retroarch.cfg)

I also pressed the rescan path button and the save configuration (default.uae).

i also used a brand new "Logitech Gamepad F710.cfg" from here: https://retropie.org.uk/docs/Logitech-Controller/ to be sure starting clean. I added some mapping to exit emulator and access GUI but that is 99% the same file:
input_enable_hotkey_btn = "10"
input_menu_toggle_btn = "2"

I created a Thexder_v1.2_0392.uae with the LEFT SHIFT mapped to a button, a new line appeared in the file:
joyport1_amiberry_custom_none_b=Left Shift

Thexder_v1.2_0392.uae is here = https://pastebin.com/ZxWYAnww

But when i load the game, this custom control does not take effect until i go in the GUI menu at least once and going back to the game (hotkey+X in my case). After having access the GUI (and go back), all the custom mapping are working correctly. I am not sure if this is related, but in the custom control menu, the input device (Logitech Gamepad F710 has an [R] at the end, for RetroArch i suppose...

I am sorry, i do not want to waste your time because i feel that it may be specific to me. If i am the only one reporting it, it may be what i call a CODE 17 problem, that mean the problem is 17 inches in front of the screen: ME ! LOL

Concerning the custom control database, i will have to make it for myself for my own games so i will be glad to share it with your to make the amiberry experience even more "plug and play" for the community ! A couple of hours for sure parsing through the old games manuals and write custom button mapping to make games 100% playable through a gamepad without having to use a keyboard or mouse (when it make sense of course).

regards,

nemo93

@mbernier thanks again for testing and reporting. I'm now investigating this as there may be issues indeed with Custom Controls.

UPDATE: ticket created.

Regarding adding more custom controls there's no obligation! Do that only if you want and have the time. Feel free to post ticket(s) on that github (one per game).

nemo93

@mbernier ticket is progressing and a scenario identified. Not sure about a fix though. Let's be patient!

mbernier

@nemo93

Thanks ! Let's hope we will be able to customize control soon !

nemo93

@mbernier Amiberry 5.3 has just been released with fix for custom controls (among other stuff). I'll see on the best way to get it in Retropie asap.

UPDATE: 5.3 has been merged in. Once again big thanks to @mitu for the ever swift response.

sirhenrythe5th

@nemo93 thanks for the info nemo93!
I just upgraded yesterday and i am one step further indeed:
now, when i use my 8BitDo-Pad wireless i dont have the freeze anymore!
But the game selection in ES falls back to the AmiberryGUI, so it seems to loose the ability to use the direct loading of the WHD-files/*.lha.

When i connect the Pad by USB/Wire everything runs perfect.
Dont know why this happens (BT-connection produces issues?), but it is ok for me.
Just for Info ;)

nemo93

@sirhenrythe5th apparently same issue as described here which occurs only with 8BitDo. I don't have such myself and everything works fine with a Xbox One controller (over BT). Please confirm your exact controller model.

sirhenrythe5th

@nemo93 i have got the 8BitDO SN30Pro.

8Bitdo-SF30-Pro-Wireless-Bluetooth-Gamepad-Game-Controller-Dual-Classic-Joystick-For-Switch-Android-Game-Pad.jpg

mitu

I wonder if it the same issue as https://retropie.org.uk/forum/topic/31569, where SDL reports some joystick axis movement immediately after the initialization of the joystick sub-system, even if there was no input from the user.

I do have an 8BitDO SN30Pro that I use occasionally and I could test with it. @sirhenrythe5th are you using the latest firmware version on your gamepad ?

nemo93

@sirhenrythe5th thanks for clarifying. There's an open ticket with the exact same controller. The other user confirms no problem over USB only over BlueTooth.

@mitu now that you mention it I got a similar issue. Anytime I turn on my controller (xbox one over BT) > direction goes haywire like someone is pushing a direction even if I don't press any button. I can reproduce this each time. Not sure it's related and this would perhaps deserve a separate ticket in order to stay on-topic :)

mitu

@nemo93 said in Amiberry 5.1 controller mapping problem (since upgading from 3.x):

Not sure it's related and this would perhaps deserve a separate ticket in order to stay on-topic :)

Could be the same issue - SDL related. May be solved in a newer version and wouldn't need a specific fix (like I implemented for joy2key).

sirhenrythe5th

@mitu said in Amiberry 5.1 controller mapping problem (since upgading from 3.x):

I wonder if it the same issue as https://retropie.org.uk/forum/topic/31569, where SDL reports some joystick axis movement immediately after the initialization of the joystick sub-system, even if there was no input from the user.

This is interesting!
I have this effect every time i (re)connect my Pad via BT.
When it is paired it starts to move from top to bottom.
I have to push the stick in any dircetion to stop this.
So i can confirm to have this issue too.

I do have an 8BitDO SN30Pro that I use occasionally and I could test with it. @sirhenrythe5th are you using the latest firmware version on your gamepad ?

I doubt it :/, i don´t have a PC to upgrade.
Does your Pad work with Amiberry (in wireless mode)?
If so i would try to update the FW of my pads at my girlfriend who has got a laptop.

mitu

@sirhenrythe5th said in Amiberry 5.1 controller mapping problem (since upgading from 3.x):

Does your Pad work with Amiberry (in wireless mode)?

I'm not using it so much these days, my daily drivers are a pair of PS4/PS3 controllers, so I can't say I noticed it. I think I've upgraded the firmware last time it got some usage, but for sure I haven't used it with Amiberry so far.

sirhenrythe5th

@mitu i see.
I also never had these issues before the update to amiberry 5.x.
I will give the FW-update a try, maybe this will help.
At least i still can play Amiga with a wired connection or use one of my plenty PS3-Pads ;)

mitu

I tested with the AmigaTestKit and I don't get the Amiberry GUI opening up.
But I think there's a bit of confusion here - I don't have the Pro version of the SN30, your picture shows the previous version of the controller (with the analog joysticks, which is not the Pro version) which I do have (with the SNES US colors).

mitu

@sirhenrythe5th have you tried to use the Amiberry menu and update the gamescontrollerdb ?

sirhenrythe5th

@mitu said in Amiberry 5.1 controller mapping problem (since upgading from 3.x):

But I think there's a bit of confusion here - I don't have the Pro version of the SN30, your picture shows the previous version of the controller (with the analog joysticks, which is not the Pro version) which I do have (with the SNES US colors).

Gosh, you are right! SORRY!
This is the model i meant and use:

It is the SF30Pro!!!
I own 4 of them.

I updated the controllerdatabase when i had the issues for the first time (update to 5.1), but did not try again since then.
I will give it a shot!, thx

DTEAM

@mitu
Hi Mitu, I have the same problem with my TeensyLc in my handheld system. It worked fine with 3.1 but doesn't work with 5.3. Strangely, my gamepad and touchscreen work fine in the UI.

I uninstalled everything (including the configurations in the opt folder) and re-intalled and it's still the same. I can see two TeensyLc controllers instead of one in the UI like the guy in the other thread with his snes controller!

Do you have an idea of what to do? I'm continuing to dig for a solution.