Originally Posted by Cobaltikus
From what I hear it already works with those 2 apps.
I'm pretty sure the only problem with FPSECE is that the dev on that app tried to make changes to use CobaltController when no changes were necessary. You just need to use the built in button mapping setup where you choose a game button in the program and then press the corresponding button on the sixaxis.
Please let me know if you have a different experience and it doesn't work as I expected.
Schtruck had to do one or two little changes in fpsece to get L1/2 R1/2 buttons working on fpsece (your drivers were not responsible for this)
The changes he made were made on fpsece itself, something to prevent the "71" code to remain each time you tried to press L or L buttons (now an already used code can't be used again)
I've just realuzed that fpsece doesn't seem to support the "g" letter from a keyboard (why?? I don't know!) so just R1 doesn't want to answer when wanting to map it in fpsece.
Schtruck now just has to see why this last code is not supported by fpsece, fix it, and all the buttons will be working.
And yes, you can set keys in FpseCE exactly the way you sayd: push the X icon on the phone, then press X on the gamepad or whatever keyboard
So your drivers work perfectly, that's fpsece that was a little adapted to support them better
BTW: I'm amazed by the speed of the sixaxis connecting process, almost immediate, even if the bluetooth on the phone was off before starting your application. The MSI takes at least 4 or 5 seconds before being connected!
Just a small quickly-made video to show Coblatikus drivers + fpsece on my HD2, you can see the buttons mapping then wipeout playing with my DualShock3