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
First off - thank you so much for building this, I adore this library and it's helped me make some really fun projects. The base of one of those projects is building something that proxies controller input from a Linux PC to the Switch using sys-botbase. I've got everything working without any noticeable delay, except for the stick movement.
I've confirmed that I'm receiving stick events the moment they happen on my end and going through the socket immediately, but they take a few seconds to actually reflect on the switch. Buttons and d-pad functionality work great and are reflected instantaneously.
I believe this is because the library is trying to slide between stick values instead of jumping immediately? But I could be wrong.
The text was updated successfully, but these errors were encountered:
I was wrong and the issue was more one of documentation. Moving an analog stick generates a lot of events very quickly, and with the sleep calls in the main loop/button loop, this translates to very real input lag.
Sending configure mainLoopSleepTime 0, configure buttonClickSleepTime 0, and configure keySleepTime 0 immediately after connecting made it much more responsive.
First off - thank you so much for building this, I adore this library and it's helped me make some really fun projects. The base of one of those projects is building something that proxies controller input from a Linux PC to the Switch using
sys-botbase
. I've got everything working without any noticeable delay, except for the stick movement.I've confirmed that I'm receiving stick events the moment they happen on my end and going through the socket immediately, but they take a few seconds to actually reflect on the switch. Buttons and d-pad functionality work great and are reflected instantaneously.
I believe this is because the library is trying to slide between stick values instead of jumping immediately? But I could be wrong.
The text was updated successfully, but these errors were encountered: