Keyboard layout doesn't match

[dkswedens]

Heya.
Im streaming from my sons gaming PC when he is fast asleep to my steam deck oled, gaming works fine but browings web and reading text outside of games is abit difficult.
Scaling doesnt seem to work, writing @ and few other things doesnt work either even thou language is set to my own one. Seems stuck on US or the like. ÅÄÖ and symbols doesnt work.

Anyone have an idea or if its just a limitation in general?

Thanks

[mad0x20wizard]

For the keyboard issue: Can you check in the system settings, while you are connected to the Duo session, which keyboard layout is used? On my system I cannot reproduce this issue. Which version of Duo do you use? There actually was a problem with some older build, that defaulted to the en-US layout every time one connected. This should be fixed right now. Do you have the Taskbar menu for keyboard layout selection visible while connected with Moonlight? I can use my German Umlauts without any problem: öäüß

For the scaling issue: This can depend on various settings and circumstances. But when I connect from my MacBook with Retina resolution to my PC via RDP, the scaling is actually a bit bigger, compared with when I connect via Duo, with the Desktop Scale set to "Dynamic". If the text is too small to read, you can set this to "Static" with an appropriate factor:

But if the text is hard to read, because it's blurry, you may actually have selected a non-native screen resolution in your Moonlight settings:

[dkswedens]

For the keyboard issue: Can you check in the system settings, while you are connected to the Duo session, which keyboard layout is used? On my system I cannot reproduce this issue. Which version of Duo do you use? There actually was a problem with some older build, that defaulted to the en-US layout every time one connected. This should be fixed right now. Do you have the Taskbar menu for keyboard layout selection visible while connected with Moonlight? I can use my German Umlauts without any problem: öäüß

For the scaling issue: This can depend on various settings and circumstances. But when I connect from my MacBook with Retina resolution to my PC via RDP, the scaling is actually a bit bigger, compared with when I connect via Duo, with the Desktop Scale set to "Dynamic". If the text is too small to read, you can set this to "Static" with an appropriate factor:

But if the text is hard to read, because it's blurry, you may actually have selected a non-native screen resolution in your Moonlight settings:

Hi, thanks for replying.
Im using the newest duo version. I think 1.5.7
The scaling thing seen on your photo is not visible for me. I can only see the supersampling and sdr nits sliders and render option.

In regards to the resolution im using native steam deck 800p most of the time and text is abit better but not optimal - when im docking steam deck to my 4k tv im using 1080p to get better clarity when gaming but reading any form of text outside of gaming is impossible, its not clear at all and seems blurry or that the text is not solid for lack of better word.
Regarding the keyboard its shown as my native language (swedish / sweden layout) so im really out of ideas here.
Its been a plague since Castor 😂

[dkswedens]

I saw the dynamic scaling, thats why I didnt see static - didnt notice.
Im testing now and also making sure keyboard language is right

[dkswedens]

Scaling works, this was my error so thanks for pointing it out.
Language as seen per screenshot is "swedish" but as you can see pressing Ö writes 1 and ? writes another symbol, cant write @ either

[dkswedens]

Changing the steam on screen layout to the US layout, Ö prints out by pressing ;
So something is really off.

[Black-Seraph]

If input generated on the machine itself prints properly, then Duo did all it could do to set the right keyboard layout.

My best guess is that your Moonlight client is sending your inputs as scancodes rather than virtual keys (or vice-versa).

You can confirm this by opening the instance's Sunshine WebUI and toggling the keyboard handler from scancodes to virtual keys (or vice-versa).

If one method isn't compatible with your client, the other usually tends to be.

[dkswedens]

If input generated on the machine itself prints properly, then Duo did all it could do to set the right keyboard layout.

My best guess is that your Moonlight client is sending your inputs as scancodes rather than virtual keys (or vice-versa).

You can confirm this by opening the instance's Sunshine WebUI and toggling the keyboard handler from scancodes to virtual keys (or vice-versa).

If one method isn't compatible with your client, the other usually tends to be.

Normal sunshine works fine. Tried your trick but didnt help. I guess its something i have to live it.
Thanks for your effort and time 😊

[Black-Seraph]

@dkswedens I'd still prefer to figure out why this happens, just in case there's other people out there that are similarly affected.

But to dig deeper we need to do some in-depth debugging on your host.

If you're willing to do that, feel free to get in touch via Discord, my handle is black5eraph.

Please let me know your Discord handle ahead of time so I can find you in the pending friend requests.

If not, that's fine too, and I'll close the issue, either at your behest or when it gets stale.