- jiggawattParticipant08/25/2015 at 05:11Post count: 6
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.
Unless I’m overlooking something obvious.jiggawattParticipant08/25/2015 at 05:51Post count: 6
Copying the Binary from my 2.6 image worked. Wireless PS3 functional. There’s something wrong with the new updates to mame4all-pi that is causing the issue.ninjatoolParticipant08/25/2015 at 21:51Post count: 8
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.dawezeParticipant08/27/2015 at 15:10Post count: 3
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.robertusParticipant08/28/2015 at 00:08Post count: 22
i have the same problem
i don’t understand why with wired, i can map my button, and over bluetooth i can’t..
is impossible set up buttons and disconnect the cable because doesn’t work! why? :( very weird…
also with mortal kombat 2 in mame4all, i can’t open tab menu, maybe i set up wrong and i delete the tab menu.
how can i restore it?
and there is a fix to get bluetooth controller in mame4all?jiggawattParticipant08/30/2015 at 20:23Post count: 6
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.petrockblogKeymaster08/31/2015 at 01:20Post count: 1828
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!jiggawattParticipant09/01/2015 at 04:21Post count: 6
Will do Buzz. I did open a ticket. I’m polishing up a fork and then I’ll submit a pull request for the change.robertusParticipant09/01/2015 at 23:24Post count: 22
So WE need to wait an update of mame4all?robertusParticipant09/09/2015 at 19:30Post count: 22
Was fixed a week ago or so.
oh i see so how can i fix it? Sorry about question.
( update binary maybe? Take a long time)
Inviato dal mio Nexus 5 utilizzando TapatalkpetrockblogKeymaster09/09/2015 at 20:05Post count: 1828
menu 5 of retropie setup – install individual emulators from binary / sourcerobertusParticipant09/13/2015 at 17:55Post count: 22
[quote=105736]menu 5 of retropie setup – install individual emulators from binary / source
i tried now to binary and doesn’t work, needed to source ?
because i tried now with binary and source, but doesn’t work my ps3 genuine controller over bluetooth ( i can’t remap button, with TAB menu )
- The forum ‘Controller Configuration in RetroPie’ is closed to new topics and replies.