This is an issue that arises due to the following facts:
This plugin uses the left stick's horizontal axis for rewinding and fast-forwarding. Let's call this the "checkpoint state"
I use the left stick's vertical axis for driving forwards and backwards.
When you perform any action, it cancels the "checkpoint state"
This makes it so that I have to be very very careful about only moving the stick horizontally. If I move it vertically even a little bit more than the deadzone, it cancels the checkpoint state since it thinks that i'm trying to drive forwards/backwards
Potential Solutions
Naive solution would be to remove the drive forwards/backwards controls from the list of actions that cancels the checkpoint state entirely. Another naive solution could be allowing the users to rebind the forward/backward controls, but I like having it them on the left stick so another solution should be looked for.
One solution to this would be to add user-customizable thresholds to cancelling the state for analogue buttons. So instead of canceling with 5% activation in the vertical direction, you could change it to 20%.
A better solution might be to make the list of actions that can cancel the checkpoint state user-configurable.
The Issue
This is an issue that arises due to the following facts:
This makes it so that I have to be very very careful about only moving the stick horizontally. If I move it vertically even a little bit more than the deadzone, it cancels the
checkpoint state
since it thinks that i'm trying to drive forwards/backwardsPotential Solutions
Naive solution would be to remove the drive forwards/backwards controls from the list of actions that cancels the
checkpoint state
entirely. Another naive solution could be allowing the users to rebind the forward/backward controls, but I like having it them on the left stick so another solution should be looked for.One solution to this would be to add user-customizable thresholds to cancelling the state for analogue buttons. So instead of canceling with 5% activation in the vertical direction, you could change it to 20%.
A better solution might be to make the list of actions that can cancel the
checkpoint state
user-configurable.