![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
|
Not sure how many folks around here support iCade controllers but I've put together a PDF showing relative button mappings for every iCade-compatible controller I could find: http://www.chaoticbox.com/amalgamatedicademappings.pdf
Please let me know if you spot any errors or omissions. That link will always lead to the latest revision, so just hit it anytime you think your copy might be stale. |
|
#2
|
|||
|
|||
|
Wow, this is useful, thanks! I don't support iCade (et al) yet, as it isn't fitting for my current projects, but a future project will indeed see support for these game pads!
Thanks for putting this together! Cheers, |
|
#3
|
|||
|
|||
|
Just saw this—thanks!
It’s also a good memory-jog to see all the iCade-compatible devices together like that. I had forgotten some! |
|
#4
|
||||
|
||||
|
There are some off-brand iCade compatible controllers popping up that aren't included in the PDF, like this dual-shock rip off: http://www.avitoy.com
If anyone can provide mapping info for that or any others please let me know and I'll add them to the list. Unfortunately I can't buy'em all
|
|
#5
|
|||
|
|||
|
Quote:
|
|
#6
|
||||
|
||||
|
Quote:
At any rate, I have to wonder where people get the API/mappings for this device. I can't find that info anywhere on the website, and I see no reason to include it with the device itself (since that's the consumer side, not the developer side). |
|
#7
|
|||
|
|||
|
Quote:
|
|
#8
|
||||
|
||||
|
Quote:
Personally I like the look of the SteelSeries: http://steelseries.com/products/othe...ess-controller but it's not a full-size controller, and I don't have one of these either so don't take this as a recommendation
|
|
#9
|
||||
|
||||
|
Just updated the PDF to include (slightly coocoo) mappings for the iMpulse keychain controller: http://www.chaoticbox.com/amalgamatedicademappings.pdf
|
|
#10
|
|||
|
|||
|
Thanks!
I'm increasingly thinking that if/when (when!) my game is done I'll support the iCade and Core with reasonable default mappings, but also allow people to configure the buttons freely--supporting whatever controller they might have. I'm thinking very simple: Press the button you want for Fire. Press the button you want for jump. Etc. No on-screen GUI of the control mapping. (Except for a static reference showing my iCade default mapping.) |
![]() |
| Thread Tools | |
| Display Modes | |
|
|