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 use Sunshine/Moonlight to stream my PC games to my TV. An Xbox controller is connected via Bluetooth to an Android device which is plugged to the TV.
Playnite is configured as an application in Sunshine with the --startfullscreen option. I start this Playnite application in Moonshell. Everynthing works great except that the icons showing the possible actions do not match my XBox controller. This is a little bit confusing.
Not sure if you can solve this. I don't know if Moonlight/Sunshine manage to tell Playnite that the controller is an Xbox one...
To Reproduce
set up Sunshine on the PC
add an application Playnite with the command "Playnite.DesktopApp.exe" --startfullscreen
connect via Bluetoth a XBox controller to an Android device that is plugged to the TV
install Moonshell on the Android device
start Moonshell
select Playnite
Everything works perfectly fine, except that the icons do not match the Xbox buttons which is confusing
Diagnostics ID
66e5e579-3cb0-4182-b349-335e08b6fd39
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Bug Description
I use Sunshine/Moonlight to stream my PC games to my TV. An Xbox controller is connected via Bluetooth to an Android device which is plugged to the TV.
Playnite is configured as an application in Sunshine with the --startfullscreen option. I start this Playnite application in Moonshell. Everynthing works great except that the icons showing the possible actions do not match my XBox controller. This is a little bit confusing.
Not sure if you can solve this. I don't know if Moonlight/Sunshine manage to tell Playnite that the controller is an Xbox one...
To Reproduce
Everything works perfectly fine, except that the icons do not match the Xbox buttons which is confusing
Diagnostics ID
66e5e579-3cb0-4182-b349-335e08b6fd39
Screenshots
No response
The text was updated successfully, but these errors were encountered: