Keyboard suddenly stops working

[ambision]

 

Mainly in the Apache module, where this issue is most affected,  the keyboard stops working after about 3 minutes of playing. I run it vanilla, after cleaning and repairing. I'ts become completely unplayable. Every module has this behavior.  No xbox controller is connected. 

At first I thought a modifier was at fault, so I deleted the throttle switch assignment and reverted to default. No joy.

Then, I thought the the "show ruler" button on the F10 map was the culprit - no it wasn't.

this seems to be happening after about 2-4 minutes in the game. Best I was able to reproduce was to start cold (everything works fine), then make the craft go alive. by the time it starts up, all keyboard commands are not working. But TrackIR and ALT+TAB commands do work. Only way to exit DCS is by killing it from task manager. In the Apache, it always happens after about 2 minutes in. other modules are a bit more stable, and it happens randomly. 

I'm at a loss here.DxDiag.txt

what do I do and how can I report this?

August 2022, Windows 11, DCS 2.7.17.29140

dcs.log

Edited August 27, 2022 by ambision

[Sn8ke]

I am having the same issue, presented itself just after latest OB update. Keyboard/USB are perfectly fine. Just stops working in game after about 3-4 minutes...seeing many posts about this on reddit and elsewhere. I deleted saved games/config/input/a-10cII/keyboard.diff as well as ran a full repair, problem still occuring. . Windows 11 Pro, latest OB. 

Edited August 31, 2022 by Sn8ke

[silverdevil]

On 8/27/2022 at 11:45 AM, ambision said:

 

Mainly in the Apache module, where this issue is most affected,  the keyboard stops working after about 3 minutes of playing. I run it vanilla, after cleaning and repairing. I'ts become completely unplayable. Every module has this behavior.  No xbox controller is connected. 

At first I thought a modifier was at fault, so I deleted the throttle switch assignment and reverted to default. No joy.

Then, I thought the the "show ruler" button on the F10 map was the culprit - no it wasn't.

this seems to be happening after about 2-4 minutes in the game. Best I was able to reproduce was to start cold (everything works fine), then make the craft go alive. by the time it starts up, all keyboard commands are not working. But TrackIR and ALT+TAB commands do work. Only way to exit DCS is by killing it from task manager. In the Apache, it always happens after about 2 minutes in. other modules are a bit more stable, and it happens randomly. 

I'm at a loss here.DxDiag.txt

what do I do and how can I report this?

August 2022, Windows 11, DCS 2.7.17.29140

dcs.log 331.85 kB · 2 downloads

 

2022-08-27 20:09:59.291 INFO    INPUT: Device [Keyboard] created.
2022-08-27 20:09:59.327 INFO    INPUT: Device [T-Pendular-Rudder {11359850-2CD6-11ea-8005-444553540000}] created.
2022-08-27 20:09:59.327 INFO    INPUT: Joystick created[T-Pendular-Rudder {11359850-2CD6-11ea-8005-444553540000}], ForceFeedBack: no
2022-08-27 20:09:59.336 INFO    INPUT: Device [Throttle - HOTAS Warthog {11363490-2CD6-11ea-8006-444553540000}] created.
2022-08-27 20:09:59.336 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {11363490-2CD6-11ea-8006-444553540000}], ForceFeedBack: no
2022-08-27 20:09:59.349 INFO    INPUT: Device [Saitek Pro Flight X-55 Rhino Throttle {11468840-2CD6-11ea-800C-444553540000}] created.
2022-08-27 20:09:59.349 INFO    INPUT: Joystick created[Saitek Pro Flight X-55 Rhino Throttle {11468840-2CD6-11ea-800C-444553540000}], ForceFeedBack: no
2022-08-27 20:09:59.349 INFO    INPUT: Device [Joystick - HOTAS Warthog {1146AF50-2CD6-11ea-8011-444553540000}] created.
2022-08-27 20:09:59.349 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {1146AF50-2CD6-11ea-8011-444553540000}], ForceFeedBack: no
2022-08-27 20:09:59.361 INFO    INPUT: Device [Mouse] created.
2022-08-27 20:09:59.396 INFO    INPUT: Device [TrackIR] created.

2022-08-27 20:10:16.708 DEBUG   LuaGUI: Input:    can't open './Config/Input/UiLayer/keyboard/Keyboard.lua'

2022-08-27 20:10:39.604 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.lua'

2022-08-27 20:10:39.609 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.diff.lua'

the first part is where all your input devices are created. then there are many many iterations of the second lines. what is explorations?

try to rename your CONFIG folder and restart DCS.

[ambision]

I did that, and even reinstalled windows and dcs from scratch. same behavior. It's sad and frustrating

[Hiob]

Just a brain fart:

What kind of keyboard are you using? Anything fancy? Wireless, Macros, Extra functions?

Do you have a basic wired keyboard you can try as exchange?

[ambision]

Thanks for the thought man, yes, I did try another regular keyboard. My main o e is k95 from corsair, with icue software. 

It's a DCS issue I believe 

[Sn8ke]

19 minutes ago, ambision said:

Thanks for the thought man, yes, I did try another regular keyboard. My main o e is k95 from corsair, with icue software. 

It's a DCS issue I believe 

100% a DCS issue. Keyboard functional in all aspects EXCEPT in game in DCS. I was backing everything up for a reinstall, however since you tried with negative results I won't waste my time. 

[Hiob]

Do you have any export scripts in the export folder? (btw…. I don’t want to insist that the keyboard is at fault, but the icue software is a pita nevertheless!)

[silverdevil]

2022-08-27 20:10:16.708 DEBUG   LuaGUI: Input:    can't open './Config/Input/UiLayer/keyboard/Keyboard.lua'

2022-08-27 20:10:39.604 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.lua'

2022-08-27 20:10:39.609 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.diff.lua'

 

what is explorations? never heard of that module. you have about 100 lines showing can't open blah blah keyboard blah blah

[ambision]

I wish I knew.. 

I'm trying to troubleshoot with ED's team right now. They think that's maybe an issue with win11 preview. 

But I already suspected it, and formatted the the stable version. 

Still the same. 

[Sn8ke]

3 hours ago, ambision said:

I wish I knew.. 

I'm trying to troubleshoot with ED's team right now. They think that's maybe an issue with win11 preview. 

But I already suspected it, and formatted the the stable version. 

Still the same. 

I been slightly suspect of Windows 11 Pro Insiders Edition. They've pushed updates which have killed USB devices such as TrackIR, etc. BTW we both have Corsair keyboard (K60 here) and iCue. 

[Sn8ke]

Microsoft just pushed a sizable Windows 11 Insiders Edition update today. Crossing my fingers this gets rid of the problem.

[Sn8ke]

Rolled Windows to previous edition, no results. Keyboard works in DCS, just not in game. All keyboard control bindings halted, however keyboard works in dcs options area and mission editor. Any take from ED on this? I will add in many regards it makes the sim unplayable. Very frustrating. If I didn't mention it, occurred just minutes after installing latest open beta.

[Sn8ke]

17 hours ago, ambision said:

I wish I knew.. 

I'm trying to troubleshoot with ED's team right now. They think that's maybe an issue with win11 preview. 

But I already suspected it, and formatted the the stable version. 

Still the same. 

Update: I just reverted my openbeta back to the previous OB update; 2.7.16.28157, via command prompt method, and the issue is gone. 100% a DCS bug related to latest OB update.

[Flappie]

What are your keyboards, gents? Do you have the same model?

The only DCS keyboard issue I had heard about until now was this one, but it does not seem related:

 

EDIT: it looks like a conflict between Windows 11 Insider and the latest OB update, then.

https://techcommunity.microsoft.com/t5/windows-insider-program/keyboard-input-issues-in-last-two-windows-insider-builds-updates/m-p/3584577

Edited September 2, 2022 by Flappie

[Flappie]

@Sn8ke By the way, you should update your sig:

Quote

Windows 10 Professional 64

 

What is your exact Windows version number? Just launch "winver" to know.

[Special K]

Am 31.8.2022 um 22:47 schrieb silverdevil:

2022-08-27 20:10:16.708 DEBUG   LuaGUI: Input:    can't open './Config/Input/UiLayer/keyboard/Keyboard.lua'

2022-08-27 20:10:39.604 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.lua'

2022-08-27 20:10:39.609 DEBUG   LuaGUI: Input:    can't open './Config/Input/Explorations/keyboard/Keyboard.diff.lua'

 

what is explorations? never heard of that module. you have about 100 lines showing can't open blah blah keyboard blah blah

These are debug messages and absolutely normal. It scans different directories and in some it just does not find that lua. That is not the issue here, just a mapping that is not there (and not supposed to be there). If you switch to DEBUG logging, you'll see them, too.

[silverdevil]

2 minutes ago, Special K said:

These are debug messages and absolutely normal. It scans different directories and in some it just does not find that lua. That is not the issue here, just a mapping that is not there (and not supposed to be there). If you switch to DEBUG logging, you'll see them, too.

ah thanks for this. how does one enable debug for DCS logs?

[Special K]

vor 7 Stunden schrieb Sn8ke:

Rolled Windows to previous edition, no results. Keyboard works in DCS, just not in game. All keyboard control bindings halted, however keyboard works in dcs options area and mission editor. Any take from ED on this? I will add in many regards it makes the sim unplayable. Very frustrating. If I didn't mention it, occurred just minutes after installing latest open beta.

Did you roll back to a stable Win11 version or did you roll back to the IE before the current IE? I have a report from Microsoft where users claim this issue for other games on the last TWO IEs.

vor 1 Minute schrieb silverdevil:

ah thanks for this. how does one enable debug for DCS logs?

For debug logging either edit or create a file named Saved Games\DCS(.OpenBeta)\Config\autoexec.cfg and insert this as a first line:

log.set_output("dcs", "", log.ALL, log.FULL)

 

[ambision]

I just rolled back DCS with cmd. windows had an update today in the dev channel, so I did it as well. for now, all seems to be working fine. so its an issue where dcs and win 11 ie dont play well

[ambision]

OK, that was not a good idea:

I can't enter MP because my version is out of date. ED needs to address this. or Windows maybe

[ambision]

further updates: same bug persists in old version as well as the latest ob

[silverdevil]

54 minutes ago, ambision said:

OK, that was not a good idea:

I can't enter MP because my version is out of date. ED needs to address this. or Windows maybe

being part of MS Insiders program is flighting (Running and testing those preview builds) and giving feedback (share your insights in the Feedback Hub on the features, changes, and issues you see). running the insider preview is a commitment to help fix the bugs that are discovered. same for DCS beta. it is explicitly known that some of the new stuff does not work quite right and reporting those issues is to make things better. i implore you to take the time to report your issue through the feedback hub. it is impossible for developers of MS and EA cannot consider every contingency. 

[ambision]

Of course. I did it. 

But now I'm formatting to a clean stable 11 install. Because my PC is only a DCS machine, a bug like this renders it to a mere brick. 

And an expensive one at that. So.. 

It's not for me. 

[silverdevil]

1 minute ago, ambision said:

Of course. I did it. 

But now I'm formatting to a clean stable 11 install. Because my PC is only a DCS machine, a bug like this renders it to a mere brick. 

And an expensive one at that. So.. 

It's not for me. 

my box is also primarily for DCS and i do not want to threaten its ability to run DCS. every choice i make with it makes me consider if it will affect DCS. so i get it. good luck and clear skies.