moonlight-stream / moonlight-qt

GameStream client for PCs (Windows, Mac, Linux, and Steam Link)
GNU General Public License v3.0
10.94k stars 636 forks source link

Steam Deck - Steam Input 'Windows' Key is not passed to host #1108

Open ekchang opened 1 year ago

ekchang commented 1 year ago

Describe the bug On Steam Deck, 'Windows' key bindings via Steam Input are not sent to host. All other special keys are passed correctly (Ctrl, Alt, Tab, Shift, Backspace). External keyboards connected to the Steam Deck correctly pass Windows key events to host.

Steps to reproduce

Moonlight settings (please complete the following information)

Client PC details (please complete the following information)

Server PC details (please complete the following information)

Moonlight Logs (please attach)

DavidRGriswold commented 11 months ago

This is not the same as the linked issue, since that seems to apply to all Windows keys and this is specifically about the one created by SteamInput on Steam Game Mode. As stated by OP, for this issue an external keyboard works as expected, but the "Win" command from SteamInput sends nothing at all through Moonlight.

Using the Sunshine "interpret Right Alt as Windows Key" option seems to work fine for just pressing Win to get the start menu, but not for shortcuts like Win+D .

Rhystic1 commented 1 month ago

Any update on this issue? This is quite impactful for people using multiple monitors, for example, as it becomes almost impossible to move windows from one monitor to the one currently being streamed by Sunshine.

GameKing505 commented 1 month ago

Would be great to have this fixed... I'd like to use a radial touchpad menu to do window management but the Win key is not recognized...

Pao-Lumu commented 2 weeks ago

Having the same issue here. Worth noting: Moonlight running in Steam Deck's Desktop mode (with custom Steam Input bindings) passes the input correctly, but both Game Mode and Desktop Big Picture Mode do not work. All of the above register keyboard input correctly.

Could this possibly be a Gamescope issue?