Help! Keyboard not recognized in IL2 1946

[RPS69]

He stated that he uses a notebook, and that he already uninstalled the wireless keyboard, and tried to use the NB keyboard alone with no results.

Can you edit your pilot name, within safe mode or normal mode?

Can you use it while flying?

Those two different times in game are not evaluated on your post.

[Pursuivant]

Originally Posted by RPS69

He stated that he uses a notebook, and that he already uninstalled the wireless keyboard, and tried to use the NB keyboard alone with no results.

I somehow missed the notebook part.

My idea was that testing using a cheap USB keyboard that Win 7 recognizes by default might prove/disproof a problem with the wireless keyboard device drivers.

Since IL2 doesn't recognize the NB keyboard either, that idea probably won't work.

I'm thinking that it might be a problem with a driver upgrade that's incompatible with IL2, since the problem came on suddenly after several weeks with no problems.

Clean the registry. Upgrade Win 7 to the latest version. Reinstall drivers. Make sure that both keyboards are recognized as input devices in the Device Manager. Upgrade IL2 to the latest version. If that doesn't work, roll back the keyboard drivers to an older version.

Originally Posted by RPS69

Can you edit your pilot name, within safe mode or normal mode?

Can you use it while flying?

Those two different times in game are not evaluated on your post.

Good points. But the problem with being able to use the keyboard in the FMB or to change key bindings makes me think that he'll get the same problem from the other UI screens. It can't hurt to try, though.

[RPS69]

I doubt it to be IL2 fault. Well... a bit, because windows management of devices changed a lot since IL2 was continuously being upgraded. Now, those glitches that could be generated by a desktop configuration are annoying and hard to detect.

Also, I don't believe the drivers to be bad. There must be something else related to keyboard usage that is generating that kind of behavior.

The only thing I may suggest to confirm this is to make an image of your hard drive, (always good to have a backup), and select an older restore condition, where your il2 worked fine. If it do works, then see which updates are missing and go installing them one by one until shit happens again. A tough job for sure.

[f6f5hellcat]

Hello,

Originally Posted by RPS69

I doubt it to be IL2 fault. Well... a bit, because windows management of devices changed a lot since IL2 was continuously being upgraded.

I completely agree with you RPS69, it’s nothing wrong with IL2 it worked for years without any problem, including about 3 years on my current laptop. The drivers seems to be ok, there are no conflicts in Device Manager.
Just to mention the laptop keyboard is US standard (bought in US), but the wireless keyboard is UK standard.

Anyway, following your suggestions here are the results:

Normal boot
a) Add new pilot name => OK! (backspace key is weird – it is not working on one char, it only deletes the whole word);
b) Binding new keys (Controls): Not working! No keys are recognized;
c) In game: Not working! No keys are recognized => exit by killing the application in Win Task Manager;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).

Safe Mode
a) Add new pilot name: OK! (backspace key works – deletes one char);
b) Binding new keys (Controls): OK! Keyboard input is recognized;
c) In game: OK! Game responds to keyboard commands;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).

Originally Posted by RPS69

The only thing I may suggest to confirm this is to make an image of your hard drive, (always good to have a backup), and select an older restore condition, where your il2 worked fine.

Regarding restoring to an older restore point, unfortunately I don’t have one from before the wireless keyboard installation. I have a system disk image but it is more than a year and half old. The other disk images are more recent than the moment when my wireless keyboard messed up.
I’ve compared the keyboard drivers in Device Manager between Normal boot and Safe Mode and the same drivers are loaded. One difference is in HID Keyboard Device -> Properties -> Details -> Physical Device Object Name. For normal boot the value is \Device\00000096, while in Safe Mode is: \Device\0000008f. I don’t think it is relevant, but there it is.

Thank you all for your suggestions!

[f6f5hellcat]

Hello,

For some reason my previous two replays have not been posted - I do not know what I'm doing wrong

RSP69, I completely agree with you, it’s nothing wrong with IL2 it worked for years without any problem, including about 3 years on my current laptop.

Anyway, first of all thank you Pursuivant and RSP69 for your advice!
Second - good news, I found the culprit !!!

So to summarise:

<> Issue: loss of keyboard (laptop built-in) input into IL-2 1946 (see the initial post for details)

<> Behaviour:
** Normal boot
a) Add new pilot name => OK! (backspace key is weird – it is not working on one char, it only deletes the whole word);
b) Binding new keys (Controls): Not working! No keys are recognized;
c) In game: Not working! No keys are recognized => exit by killing the application in Win Task Manager;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).

** Safe Mode boot
a) Add new pilot name: OK! (backspace key works – deletes one char);
b) Binding new keys (Controls): OK! Keyboard input is recognized;
c) In game: OK! Game responds to keyboard commands;
d) FMB->Mission Description: keys are recognized but behave like they are stuck (aaaaabbbbbccc, etc.).

<> Solution (applicable to Alienware laptops only???):
The culprit was "HappyOSD" service, which in my case was listed as 'Running'. Deactivating it solves my problem!
To do this go to: Control Panel -> System & Security -> Administrative Tools -> System Configuration -> Services tab. Then look for HappyOSD service and disable it.

This restored IL2 1946 access to the keyboard inputs for both the laptop built-in keyboard and the wireless one (Logitech K800). I'm now patched to v4.12.2 and Enjoyr DGen patches and everything works just fine!

In my case 'HappyOSD' is part of a software used to display on-screen various indications of laptop functions (brightness level, volume level, battery level, etc.) when the corresponding touch buttons or FN keys are pressed. Looks like it was installed by Alienware from the initial build. It is still wired than it started to misbehave all of a sudden!
By deactivating the service the FN keys still function, but the nice on-screen sliders are lost ... well I can live without it!

Thank you all for your suggestions! I hope this will help.