K
Korven
Guest
Tried this on my old Toshiba thrive, works good. But you have to go into setting and map the keys on every table.
Do you think there will be any time set aside soon for getting Android caught up Ryan?
Thanks.
That is my hope yes, I am currently working on tournament stuff (and will be for a while as we improve and add on to it) but in between I am going to ask/argue for time to get you folks caught up to the best of my ability.
Thanks Ryan - that would be awesome.
And remember, I am implementing functionality that is cross platform. Unfortunately, that takes higher priority to management. But I promise I will try to knock that out so I can get back to helping you folks, never ignoring you guys! =)
Nudge up will be in for the next update next week. I might not be able to get the nice interface in, but it will be cut into thirds. Left third, middle third (up nudge), and right.
Just another random dude saying:
Yay for controller love...I've been hearing my poor screen crinkle a bit lately as I smash the screen trying to get one more ramp shot
Yay for dev contact...just knowing it's coming has me so excited, I'll make random post on the verges of fanboi
simple Bluetooth keyboard here...not smart enough to get any of my other controllers hooked up w/o voiding warranty (yet)
I bought the k/b specifically for this game then went *something like fiddlesticks* when it didn't work
Ok a little update on this.
I have found that there are some api restrictions for analog controls on Android. Honeycomb and up can query the range values for things like triggers, joysticks etc. I found a white paper that describes how to do it properly, limiting certain calls to that os version and higher, so I will need to give this a good read. We will absolutely need those for plunger & nudge. Wanted to sneak that in with the build today but gonna have to do a little more work unfortunately.
http://docs.nvidia.com/tegra/data/How_To_Support_Android_Game_Controllers.html (for anyone interesting )
Here is an alpha build with the rudimentary mapping system (just the flippers for now). Currently I am only mapping left and right flipper buttons just to give this a test while I do some tournament coding for the kickstarters. For now its hacked into the controls button in the options menu (main menu).
http://androidfiles.pinballarcade.com/beta/AndroidPinballActivity15a.apk
So far I've seen a fairly encouraging selection of controllers supported in the Beta builds for controller support.
Android 4.2.x has no support for Wiimote and Classic Controller due to this controller being 'pairless'.
I have seen mention of XB360 controllers and of course the purpose-designed controllers like Moga and iCade supported well so far.
I would like a laundry list of supported controllers that meet the following:
* Can be paired on Android 4.2.x through Bluetooth.
* Work without Root.
* Work without an additional compatibility app (such as Sixaxis, USB/BT Joy Center).
Perhaps this should be a separate thread for the benefit of those that will be coming into the new controller support arena.