[garbear]

But your quite correct that at some point you have to assign the connected devices to the players.
It would be cool if we could add controller icons to a VID/PID buttonmap so we can make this a bit more graphical?
Maybe also a controller description to the buttonmap could be usefull? Or is the devicename uique for a VID/PID?

One of the assumptions I decided upon early on was an infinite number of both proprietary and DIY controllers. Under this assumption, it's impossible to collect icons for all controllers. It also makes any additional GUI info very difficult - When an infinite (or large number) of controllers are attached, how do you show every buttonmap at once?

I actually have a solution to this difficult problem that makes the process much more graphical. The image of the virtual controller in the center could render the pressed buttons according to the instantaneous button map. This holds up against the infinite-controllers assumption, as input from all controllers can be multiplexed into a single image.

OFC, I'm welcome to any other ideas or thoughts on this problem!

I'd love that idea about high scores and statistics. Were you thinking of creating some kind of user/player accounts?
These accounts can mabe also be used for personal savestates, netplay, parental controls etc.
(Sounds like a lot of work though)

Yes, too much work for the near future, unfortunately. However, I think it could be paired with a rewrite of our existing profile support to good effect. Adding game support to profiles would make a good GSOC project (for this year's GSOC we had an almost identical project, but the student had to back down early).

Well i also think it is related to the "analog" button on the controller. (The one with the red led above it, between the analog sticks)
When this button is enabled or disabled the d-pad and analog axis work differently.
I'll try to find out what is causing this. I don't think you can detect if the ps dualshoch controller is in analog or digital mode?

Yes, the "Analog" button is a hardware feature that can't be detected by software. From my experience, enabling the analog LED works better more often than being disabled. I have controllers that simply can't be fully mapped, because the analog button always disables some features. I just created button maps for the analog mode that enabled the most features. Maybe add a comment in the button map XML or its commit's header about this?

Can you do a little more investigating here and let me know what you discover in regards to the analog button?