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
Is your feature request related to a problem? Please describe.
The issue is that the library is coded for -127/128 int value, 8bit. While many SoC's have 12bit ADCs or better. (I'm using an ESPS2 at the moment)
Describe the solution you'd like
An easy and clear way to change the settings of these values for the gamepad portion of the library.
Describe alternatives you've considered
Editing the library itself to use int_12t instead of the currently used int_8t.
Additional context
Joysticks and triggers for gamepads usually don't need more than 256 values for most casual games, but depending on the game (like simracing, or a shooter) having more accuracy can be the difference between having an enjoyable time, or not being able to pinpoint why the controller feels bad to play on but knowing you're not at fault.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The issue is that the library is coded for -127/128 int value, 8bit. While many SoC's have 12bit ADCs or better. (I'm using an ESPS2 at the moment)
Describe the solution you'd like
An easy and clear way to change the settings of these values for the gamepad portion of the library.
Describe alternatives you've considered
Editing the library itself to use int_12t instead of the currently used int_8t.
Additional context
Joysticks and triggers for gamepads usually don't need more than 256 values for most casual games, but depending on the game (like simracing, or a shooter) having more accuracy can be the difference between having an enjoyable time, or not being able to pinpoint why the controller feels bad to play on but knowing you're not at fault.
The text was updated successfully, but these errors were encountered: