-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screensaver dismisses immediately if certain controllers are connected #79
Comments
My guess is the packet number is changing constantly, even when there's no input:
Long term, it'll make sense to fix this by moving away from the input library this plugin uses in favor of the valve library that Playnite also uses. Can't give any guarantee if/when I can get around to this. |
Thanks for the input, and of course massive thanks for creating this very useful plugin in the first place. |
Glad you have a work-around! The controller framework I'm using will likely shift to what Playnite uses (for xinput support) when the next version of playnite releases. |
I'm using an 8bitdo wired controller with Playnite and this screensaver plugin, and whenever that controller is connected, the screensaver never starts.
This is not a problem with other Xbox controllers. Evidently as long as the controller is connected, it's always sending some kind of polling state change to the screensaver, dismissing it as soon as it starts.
I've tried to edit the screensaver code myself to resolve the issue, but so far I've come up blank and I'm hoping anyone else might know of a fix.
The text was updated successfully, but these errors were encountered: