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
In Playnite Fullscreen on WIndows 11, the "Swap confirmation/cancelation button binding" option under Input settings correctly swaps the A/B controller functions for everything except for when selecting games from the list of cover tiles. To select a game from the (filtered) list, I have to press B on my controller (incorrectly acting as confirm), and then on the game details screen pressing B again returns to the list (acting as cancel as expected). Occurs when using a Xbox Series controller or 8bitdo Lite.
To Reproduce
No response
Diagnostics ID
6cebd9d7-56fe-4fea-a523-d290eed0ead3
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Can't reproduce with Xbox Series controller. B button does nothing on the main screen with game list (as expected) no matter if swap is enabled or not.
So strange. Well, let me know if you have any changes I can try to troubleshoot. Tried wired and Bluetooth, same thing. It's a new Win11 install with no joystick software running. Tried a resinstall of Playnite.
I also notice that with the swap setting checked, X/Y are inverted so Y on my controller launches the game and X starts a search.
Bug Description
In Playnite Fullscreen on WIndows 11, the "Swap confirmation/cancelation button binding" option under Input settings correctly swaps the A/B controller functions for everything except for when selecting games from the list of cover tiles. To select a game from the (filtered) list, I have to press B on my controller (incorrectly acting as confirm), and then on the game details screen pressing B again returns to the list (acting as cancel as expected). Occurs when using a Xbox Series controller or 8bitdo Lite.
To Reproduce
No response
Diagnostics ID
6cebd9d7-56fe-4fea-a523-d290eed0ead3
Screenshots
No response
The text was updated successfully, but these errors were encountered: