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
I wrote an automatic gearbox Python app a while back. Some people seem to enjoy it as it behaves like a real auto gearbox. Great for a Sunday drive.
It works by reading multiple parameters to make a decision, taking into account the current driving style.
Upon decision, it sends keyboard.press_and_release('o') or keyboard.press_and_release('p').
This used to work until CSP 0.1.79, starting at CSP 0.2.0, the keypress are mostly ignored.
Some (1%?) seems to filter through, but that breaks the behaviour of the App anyways.
I have double-checked my code, and the keypress are indeed being sent/pressed, confirming that the issue is out of my scope.
Could you please either :
fix what's blocking the keystrokes on CSP ?
provide me with alternative means of sending upshift/downshift instructions that CSP won't interfere with ?
Thanks!
The text was updated successfully, but these errors were encountered:
Note that, I can bruteforce my way into having the keypress honoured (basically, a loop pressing until one keypress gets through).
But that hangs the game for 1sec at each up/downshift and is hacky as.
Hi,
I wrote an automatic gearbox Python app a while back. Some people seem to enjoy it as it behaves like a real auto gearbox. Great for a Sunday drive.
It works by reading multiple parameters to make a decision, taking into account the current driving style.
Upon decision, it sends
keyboard.press_and_release('o')
orkeyboard.press_and_release('p')
.This used to work until CSP
0.1.79
, starting at CSP0.2.0
, the keypress are mostly ignored.Some (1%?) seems to filter through, but that breaks the behaviour of the App anyways.
I have double-checked my code, and the keypress are indeed being sent/pressed, confirming that the issue is out of my scope.
Could you please either :
Thanks!
The text was updated successfully, but these errors were encountered: