I’m migrating from 2.6 where I had no problems with Mame4All recognizing my controllers. I recall doing the compile fix for axis > 6.
I’ve done a clean install of 3.0 from binary and cannot get it to recognize my controller on the new version. It works in all other Retroarch emulators so it’s definitely an issue with Mame4All. I’ve compared configs and other files endlessly. I know Retropie forked the code and did the axis patch so I wouldn’t expect that to be the problem.
I’ve tried compiling from source thinking the binary didn’t have a recent fix. Still didn’t work.
Next step is to copy the binary from 2.6 which would pinpoint an issue with the latest code.
could you explain on a noob level how to copy the 2.6 binary? I’m on 3.0 and can’t get my PS3 wireless working, although it works just fine wired, and it does pair wireless on other emulators, just not mame4all.
i also found that ps3 over Bluetooth is not working in Mame4All but it you plug up the usb cable to the same ps3 controller and reboot it works perfect over usb. I also found if you user the ir-iMame4All emu instead the controller works fine over Bluetooth. the same goes for FBA.
I’ve discovered the fix is to once again remove the axis limitation bit of code and recompile the source. It was told to have been fixed but the code was put back in with a higher limitation and the false assumption that it fixed the problem.
What seems to be happening is the wireless Bluetooth code causes the controller to utilize more axis that when directly plugged in.
You can open a ticket if there isn’t already one and we can remove the limit or increase it further. We had it removed before, but when upstream fixed it, we assumed they had tested their code, I guess not!