[Retroid Pocket 3+] Left Analog Stick movement is choppy/inconsistent in Giga Wing
Platform / OS / Hardware: Android / Android 11 / Retroid Pocket 3+
Flycast version: v2.3.2-232 (Sept 24, 2024)
Hardware: Retroid Pocket 3+
Description of the Issue
When playing Giga Wing, the left analog stick is not moving properly. I've tried different combinations of moving the stick slightly/all the way in any direction and have not been able to consistently move in a direction consistently.
Debugging Steps Tested
*I've tried adjusting the deadzone sensitivity from 0 to 100 *I've tried adjusting the saturation from 50 to 100
Logs Gathered
Screenshots
Have you tried running a controller test utility such as ControllerTest-DJ?
I've run a controller test and it appears that my sticks are operating as intended.
For reference, when I play Crazy Taxi, I don't seem to have any issues with controlling the movement.
I did run a few more tests in Giga Wing where I set the dead zone to 50% and saturation to 200% (and various other permutations) and I noticed that I can move in diagonals consistently, but only diagonals.
Edit: I did notice when using the gamepad tester for dead zone that if I move the stick quickly all the way to the corner or orthogonal direction, it would not draw a smooth line all the way though (I'm assuming this means that it's not catching the input as it moves to a direction). However, if I move the stick slowly to a direction, it will record a smooth line.
With that being said, when playing Giga Wing and moving the stick slowly in the orthogonal direction, I still can't move. I can only move in the diagonal directions.
I don't have a Retroid P3+, only a Retroid P2+. On GigaWing I have a hard time moving down. In general, it looks like quick moves in any direction are not always registered. With a controller test utility, it seems that the analog stick isn't registering many intermediate values, but when comparing with a desktop machine it doesn't look very different.
It's possible that the Retroid P3+ analog stick is reacting in a way that GigaWing doesn't like, but I don't know what could be done to fix it.
All good, I appreciate you looking into this!