Lenovo Legion Go controller issues adressed #3682
Conversation
Do you have link to the bug? Did you try the latest version of SDL to see if it's fixed there? Also, why is this new option needed if this PR completely reloads all devices anyways so there shouldn't be any ghosts left because we didn't get removed event from SDL. |
Unfortunately, I dont have the link, I just guessed that the bug is in SDL cause nothing fixes it except reloading gamecontroller subsystem.
I tried latest version but I had problems with interop code (Playnite crashed on launch) and didn't have time to figure out yet how to properly update it, sorry. But it's reasonable to try on new version, you are right
Because there is more than one problem. In addition to SDL ghosts, there (I guessing) is an issue with Lenovo Drivers - controller being registered as new device in device manager every time it connects/disconnects, so device ID is different and if I add controller to DisabledGameControllers, after reconnect it will be unchecked because ID is not the same. So, if one uses Handheld Companion with XInput emulation they will have double triggers even after SDL reloading. The new setting 'fixes' it for this particular case (not ideal solution, but I think there is nothing we can do at the current moment, maybe you have some better ideas) Sorry for my English |
|
There shouldn't be any interop issue with updated SDL, they are not making breaking signature changes in current (2.x) release as far as I know. Just make sure you are using 32bit release dlls since Playnite is 32bit process. |
Details here: https://www.reddit.com/r/LegionGo/comments/1afc5pc/solution_for_double_inputs_in_playnite_after/