Trigger axis thrust about crazyflie-android-client HOT 8 CLOSED

That's weird. Did you try the latest version CrazyflieControl_2014-01-29.apk? Unfortunately it's hard to debug for me because I don't have a XBox 360 Gamepad lying around.

Update: OK, after some googling I found out that the XBox360 gamepad uses a "shared axis" for the left and right trigger. That might cause this problem. What name does the axis show when you're configuring it in the preferences? (something like "AXIS_....")

Original Comment By: fredg02

from crazyflie-android-client.

I'm on the lastest version already.

AXIS_LTRIGGER and AXIS_RTRIGGER
The triggers are detected as different axis on linux systems.

I tried with 0 deadzone, just in case, but it's not that.

Original Comment By: Vaasref

from crazyflie-android-client.

I've read that it depends on the driver how the triggers get detected (as one axis or as separate axes). My question was rather what it shows in the preferences of the Crazyflie Android client. I'll upload a new version that might fix the problem.

from crazyflie-android-client.

Please try the pre-release v0.1-alpha and report back if it works.

from crazyflie-android-client.

Sorry I missed the migration to github.

Is still there an .apk to test ?

from crazyflie-android-client.

Sorry, I forgot to publish the "pre-release". The APK is attached to this release.

from crazyflie-android-client.

I'm sorry the controls are no more mapplable.

The buttons mapping still work.

from crazyflie-android-client.

This has been successfully tested with version v0.5.2 on a Nexus 5 (Android version 5.1.1). It might even work with earlier versions of the client.

The trigger buttons (L2, R2) of a wired XBox360 controller were detected as separate axes (AXIS_BRAKE, AXIS_GAS) and could therefore be assigned to thrust without a problem.

Please re-open if this is still an issue.

from crazyflie-android-client.