Open GoogleCodeExporter opened 9 years ago
MAME4iOS currently support wii and ps3 controllers natively (JB version).
Anyway, I would like to add MFi support. I'm currently a little busy with no
time to develop, but i will add in a future update when i have some free time.
Original comment by seleuco....@gmail.com
on 30 Jan 2014 at 4:24
[deleted comment]
Sorry.
All my devices are on iOS 7.1.
I was tired to beg with buggy 7.0 on my iPad Air. Las time I checked btstack
was only arm32. I'm not sure if ps3 controllers are working or not on arm 64 or
iOS 7.
Original comment by seleuco....@gmail.com
on 13 Mar 2014 at 7:20
Actually I've reinstalled and can confirm Bluetooth to the dual shock 3 now
works with the iPad air and ios 7.06 so happy days. Just thought I'd post back
so you know its working mate
Original comment by jrbailey...@gmail.com
on 13 Mar 2014 at 9:27
Would be great to have mfi support. Best iOS app ever
Original comment by hay...@gmail.com
on 3 Apr 2014 at 8:53
I second that!, My 8y/o son would love to be able to play BombJack &
Ghost'n'Goblins w/ real buttons on our Logitech PowerShell
Original comment by hjgabrie...@gmail.com
on 16 May 2014 at 11:22
MFI Support ll be verry appreciate if possible ;) thx
Original comment by franck.g...@gmail.com
on 24 Sep 2014 at 8:57
I would be happy to implement support for MFi controllers(it's not that hard,
in fact Les Bird did this on the old version of mame4all) but I am having the
hardest time compiling the project - getting libmamearmv7 built... An updated
makefile that works with clang(Xcode 5/6) would help me a lot.
Original comment by cristian...@gmail.com
on 12 Oct 2014 at 3:05
is there any update for MFI controllers ? I have amazing controller but I can't
use. It shouldn't be hard. And if you need help I can be tester for you guys.
Cheers
Original comment by melih.da...@gmail.com
on 4 Apr 2015 at 10:49
Yes, please add MFI controller support.
It will be the best way to play on non jailbreak devices.
Thanks!!!
Original comment by studioi...@gmail.com
on 5 Apr 2015 at 12:01
Original issue reported on code.google.com by
g...@garypearson.co.uk
on 30 Jan 2014 at 1:30