Since Gamepad was mentioned in the new build I decided to give it a go. Hooked up my Dual Shock 2 and put in some events for the gamepad and previewed. Nothing.
So I tried something else. I put x360ce
in the Chrome folder and tried it that way. Now it works.
So it seems to me that it's Xinput only (at least in Chrome). Though I don't know if it's because of the browser, or because of C2. If it's because of C2 I'd highly suggest broadening the gamepad object to support more than just Xinput. If it's because of the browser... then I don't know what could be done. Maybe someone else does.
In any case, while Xinput is decent, it doesn't cover that much of the possible peripherals people use. While enthusiast like us here at the Scirra forums may feel comfortable mucking about with experimental drivers, third party software and whatnot to make stuff work. More than likely, the common user won't, and I don't expect them to (as already stated).
Aside from the obvious Xinput issue, there're some things that I'd like to see which would make the gamepad object more useful.
The gamepad object lacks some conditions that the keybord has. Namely "on key pressed" and "on key released". Gamepad versions of these would be great.
Setting up events for both gamepad and keyboard is a bit clunky currently. I'd have to copy the entire group and redo the events in it for gamepad. If the "OR" blocks supported more than one condition per ... uh.. block(?), it would make supporting multiple control types easier. Like this:
Left Arrow Down
Player on ground
D Pad Left Down
Player on ground
This was mentioned in another post a while back, not sure what happened to that thread though.inkBot2012-09-11 16:59:37