Keyboard layout changed / not matching Windows setting in sim with some recent patch?

[Eldur]

I'm having a rather severe problem after not having flown since 2.7.2.7910.1.

 

Regardless of my Win 10 regions setting (German/Germany with both German and US keyboard layouts, usually using my native one), I get some kind of Japanese keyboard layout with latin letters (all the special keys are like OADG 109A though) in DCS now. This breaks quite a lot of my keybinds, especially all the stuff that's in between the letters and the Enter key. Switching in Windows from German to EN-US or back doesn't do anything. I don't even have any other languages installed...

Anyone else experiencing this lately or having an idea of how to fix this?

 

Edit: Outside of DCS everything is just fine

 

Edit 2: Windows just forced an update to 21H1 (from 2004), but that didn't change anything

 

But: I noticed that when I type something into the search box in the button/key mapping dialogue, it enters correctly, just what I type in by my German keyboard layout. But when pressing, let's say, ü (english: [ ) or + (english: ] ) to get the kneeboard next/prev keys, it doesn't react on ü/[ at all, brings [ on +/] though and I get ] when pressing # (directly below +) which normally brings up the general comms menu. Same in the sim, the key mappings are off. What an weird issue...

 

I've uploaded a log, maybe that will help finding the root cause. Weirdly, DCS even generated a crash dump even though I exited it normally.

 

PS: All that on my old 3570k rig, don't know yet if it's the same on the new one. I wanted to have DCS updated and running fine before taking it over to the new one - and replacing the GPU.

dcs.20210728-182424.zip

 

Edit 3: I could finally solve the problem, after I noticed it was not just DCS related. Had the same issue in DOSBox, didn't need to try other games to know it's not and DCS issue actually.

Simple as-is: I went Win+I, devices, removed my Digital Media Keyboard Pro, a Logitech 106 keys keyboard (I don't even know I have or even had, I'm using the very same Microsoft keyboard since 2003) and a HID keyboard thingy (basically everything that identified as a keyboard), replugged the thing and it worked normally again. Anyway, the weird thing is that issue only appearing in games where the keys are polled directly.

 

Edit 4: Now, that I've thunk about it, I might have found the reason. I was visiting my mom within the last few weeks (which is why I didn't run DCS for so long), and I always take my mouse with me when I do that. Because I ordered my new hardware to her location and built the thing there, I needed a keyboard - and I took a Logitech K520 she has and paired it to the dongle of my MX Anywhere 2 mouse with the Unifying Software. The thing is, that keyboard has a Swiss layout. Apparently the dongle still has it registered even though it's actually far away and switched off now and that might have changed the internal mapping somehow. I got the initial idea that it might be a Japanese layout because the key left of the alpha numbers reported back as "KANJI" in DCS.

 

TL;DR: Tech issues can be weird. Very weird. I edited the title a bit and will leave the post, maybe someone will find it useful at some point in the future.

Edited July 28, 2021 by Eldur

[Flappie]

Many thanks for your feedback, @Eldur.

 

@chromium Come and read this if you're still having this issue!

[chromium]

acknowledge, I'll check twice next time I pair the keyboard!

[Nealius]

Do Swiss keyboards also have a 106-key layout? You are correct on the Japanese keyboard assumption. They are also 106 keys with the punctuation in very different locations than standard QWERTY. The left-most "kanji" key you referenced, tilde on most US keyboards if I recall correctly, toggles between Roman input and Japanese input.

[Y0SCHI]

Thanks a lot it was the Keybord Unifying. Delete and rebind.