You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the SDL forum, they confirm that the Stadia controller's analog triggers work correctly. It is understood that the problem lies in Godot.
A video is provided showing that the analog triggers work correctly in SDL.
Link to the post: https://discourse.libsdl.org/t/sdl-supports-stadia-pad/55314/2
Godot only reads 0 or 1, there are no intermediate values using "get_action_strength".
Initially this error also occurred on Windows.
For windows I solved it using this method:
This generated two new fields in the windows application:
But godot doesn't read those fields, it seems, and only returns two fixed values: 0 or 1.
Tested versions
v4.4.dev2.official [97ef3c8]
v4.3.beta3.official [82cedc8]
v3.6.rc1.official [cfc4a0e]
System information
w10 64
Issue description
From the SDL forum, they confirm that the Stadia controller's analog triggers work correctly. It is understood that the problem lies in Godot.
A video is provided showing that the analog triggers work correctly in SDL.
Link to the post:
https://discourse.libsdl.org/t/sdl-supports-stadia-pad/55314/2
Godot only reads 0 or 1, there are no intermediate values using "get_action_strength".
Initially this error also occurred on Windows.
For windows I solved it using this method:
This generated two new fields in the windows application:
But godot doesn't read those fields, it seems, and only returns two fixed values: 0 or 1.
This utility reads stadia triggers correctly:
https://gamepad-tester.com/
2024-10-15.12-03-04.mp4
Steps to reproduce
Press the right trigger and see the values in output, 0 or 1.
Minimal reproduction project (MRP)
Test.zip