Is the Android Game Controller Object good?

Hi guys.. I have some questions about this extension thingy.
Please login to see this link.

Does it exhibit the same "lagging-behind buffered-like inputs" behaviour as when using the Android Object KeyEvent events? (As in, the key presses are super delayed if you press/release many buttons simultaneously, I did a Please login to see this link..). How precise are the analogue controls' values (like what's the range and stuff)? Does it work similarly to the OUYA extension controls?

Is it worth getting or is there a cheaper workaround/alternative without having to rely on the Android KeyEvent events? Is there a way to make the OUYA extension do the same thing on stock android? I know I can use the Arrow Keys Key Press events like on PC and the BACKSPACE key for the B and Y buttons; but I wanna know if there's an alternative for the more common buttons like A or X. Up until now I've used exclusively used the button press events from the Android object, with the corresponding KeyCodes for the Android gamepad buttons, but it gets difficult to play faster-paced games when the input is all buffered like that.

so yeah, is this extension the real solution i'm looking for? or is there a slight chance I might be able to find a workaround with what I currently have?

thanks in advance

Hi

Just wanted to let you all know that I bought the extension and while it does work unfortunately it does exhibit the "lagging-behind buffered-like inputs" behaviour. It's mostly noticeable when pressing all the buttons at the same time (R1,L1,A,B,X,Y,L2,R2). You can clearly see how the buttons aren't released all simultaneously in game, but one at a time.

Here's a controller test APK to test it. (API 22)
Please login to see this attachment.

(And here's the source: Please login to see this attachment.)

But oh well at least I've got analog controls now, both for the analog sticks and the trigger buttons.

So, if you don't need analog controls, or support for multiple simultaneous controllers, and can work around the limitations of having to use the KeyEvent events [*Read Button State on Android Object], then you probably don't need to get this extension.

Also, is there any way to have the Left stick controls be separate from the D-pad controls?
I'd like so that I can have both control independently. So I can push the D-Pad in one direction, and the Left stick in another direction without one conflicting with each other.
Also so I can have the D-Pad assigned to some other actions without the Left Stick triggering those events. (I know I could do this by adding a LeftStickX==0 & LeftStickY==0 to all the D-Pad events, but that would mean that D-Pad Actions can only be done while the stick isn't being moved... and that's a bit awkward). Also the start button triggers the D-Pad center event but there are no events that correspond to the select button (Although it still can be detected using the KeyEvent events).

But yeah, so far, the one advantage of this extension (over simply using Android Object) so far is the analog controls, which allow you to use the right stick and the L2/R2 analog values if the controller support them; also the chance to use multiple controllers and being able to tell one's input from another.

anyway tl,dr, the gamepad extension suffers from the same input lag from simultaneous button presses/releases as the android object read-button-state method does...

This is a good enough extension, but it costs 25$, and surely these issues can be solved to make it really worth the money!

Quick update, the input is tied to the framerate. Only one button can be pressed down, or released, per frame. If more than one button is pressed at the same frame, the second button press lags behind 1 frame.
Also, analog controls are ignored if there's button presses/releases that still need to be accounted for; so if the framerate falls too low, the sticks will be frozen in place until all the button presses/releases are processed.
Since it pretty much uses the same interface, using the "Read Button State" events from the Android Object exhibit the exact same input lag.

Sorry if my words were too harsh yesterday. The extension works just fine, it's just in my opinion a little bit too expensive for what it does.

But-- yeah, it's just what it says on the tin. Full access to gamepad controls.

yeah, fair enough on the price.

the analog events are these two:
Please login to see this attachment.
they move the Actives according to the analog data.
my mfa also accounts for L2 and R2 analog.

I'm using two different controllers to test it. One is my GPDXD, and the other one is a generic bluetooth joystick (and yea both work fine in the Game Controller KeyMapper app)
Please login to see this attachment. Please login to see this attachment.

Maybe I'm pressing the buttons too quickly? Try pressing all four face buttons at the same time, repeatedly, while moving the d-pad quickly; for a good 5 seconds or so, and see if that creates any lag...

but yeah thanks for the reply! I guess you don't have an analog joystick to test the app but...
I think the only issue I'm having right now is that moving the left analog stick also trigger the d-pad events (like, moving the stick to the left also triggers the dpad left event).Can be worked around but-- it'd be nice if those were completely separate controls

but yeah, in retrospective, I think the lag-behind issue isn't as tough now as it seemed when I first tested it.