@Rutjes Hey
I had the sam issue with my arcade china controllers. I rotated the joystick 180 ( up to down ) and now it works. ( Only on the Pi 3+)
My new problem is, on retropie x86 ( on ubuntu), the reicast controller configurations doesn't work. When i launch the game no button works.
Could you fix your problems with your cabinet?

@kristjan1111 As other services started on boot, the splashscreen has to wait until the system is minimally start before it can start. Since the splashscreen image/videos are on your local disk, there's nothing that can be done before the disk check is complete.
I remember that there was a bug on RPI's related to fake-hwclock that would make the disk check trigger every boot - https://www.raspberrypi.org/forums/viewtopic.php?t=198937&start=25 - so try to run a system update and see if it fixes the long boot time.

@mitu Thank you so much! ApplePiBaker worked so much better!!!

hey hi
how did you solved your problem? I have similar issues with the arcade controller of my cabinet. After configured the arcade Control in the reicast conf/menu, I launched a game and try to play. But no buttons work.

@mitu I just did it and now seems to work correctly. Thank you. I'll let you know if I get other issues

@AndersHP Yeah, since ES loads the artwork on the fly, the access speed is relevant for the user experience. Apart from slow USB drives, network drives are another bottleneck that can be avoided by putting the artwork on the internal SD.

@SlipperyPickle Just happened to get back to this project and turns out this was the problem! Thanks!

@3dpprofessor Did you install from source or from binary ? Update your RetroPie-Setup script and then re-install the Solarus Engine again.

Turns out that the dead zone was set too high.
When the joystick finally tilted out of the dead zone it had gone too far for the smaller motions. I set it to almost nothing in comparison to what it was and now everything is nicer to play.

@staller It has nothing to do with the controller type you are using.

@oscarw You can edit your original post and change the title to reflect that it's resolved.

@Denko please fill out https://retropie.org.uk/forum/topic/3/read-this-first

Welcome to Retropie and to this forum.

Thanks for sharing your solution. It would be nice if you'd edit your opening post and add [Solved] before its title.

Backup the ROMs and BIOS folders, the \\retropie\configs\ folder - the emulationstation folder contains your collections and ES settings/own themes`. Here's a topic discussing this in detail - https://retropie.org.uk/forum/topic/16866/.

The Bluetooth stack stores the all peripheral pairing information in the filesystem (in /var/lib/bluetooth/), so the problem is definitely on the side of your controller, which likely stores the pairing in some kind of battery-backed volatile storage.

My advice: ensure that you don't allow your controllers' batteries to drain completely. Make sure to install the sixaxis package, as this will install install a service that automatically turns off your controller after being idle for 10 minutes (or any user-set time). Without that, your controller will remain paired indefinitely until either the battery is completely dead or you turn off your Pi.

See here (and avoid using the ps3controller driver, as it's only needed for more obscure third-party clones).

@mitu one success for us. The edition on that .cfg worked. One interesting thing I've noticed is: every value was 11 more than normal.
If my select button value is 10, on that .cfg he was 21.
If my B button value is 4, there was 15.

On a side note, I've used @Clyde "mc" tip and man, it saved at least 1h of my time.

Again, guys. Thanks for your time, for your effort, for your attention and for caring and sharing your knowledge with us.
I request now my promotion to Private 1st Class Noob.

Well I am starting to think that this USB audio chip I have is simply not compatible with the Raspberry Pi Zero W. My reasoning:

1 - USB Circuit works fine with Windows Desktop and with Raspberry Pi 2.
2 - USB Circuit not detected through USB Hub on my original Pi Zero W.
3 - Loaded Retropie 4.5.1 on spare SD card and plugged it into spare Pi Zero W. Without modifying config and overlays to run DPI I was able to get wifi working without any trouble.
4 - Using SSH logged into the Pi and then plugged the USB audio circuit directly into USB on Pi Zero W.

USB audio still not detected.

I think I am going to have to look for a different chip.

I do find it curious that it works on a Pi 2 but not a Pi Zero.

Thanks everyone for the help. I will check back in when I have a different chip.

Thanks!
KB

@nemo93 said in [Tutorial] "Almost" perfect amiga emulation - UAE4ARM and WHDLoad images [Amiga]:

All,

I've found an even better method, even simpler. Please have a look at this post:

https://retropie.org.uk/forum/topic/12656/agency-amiberry-whdload-holy-grail

Thanks! This method is simpler and faster but the best thing is all packages being versioned.

@ibonihs You could try increasing the cycles to 20000, 25000 etc.

If this doesn't work then could you post the contents of your config file dosbox-SVN.conf at a site like pastebin.com?