Page MenuHomeFeedback Tracker

Keyboard becomes unresponsive in Arma 3 and Windows!!!
Closed, ResolvedPublic

Description

During the first infantry showcase as you get to the first cluster of rocks, the game stops responding to keyboard commands.

Unable to alt+tab, unable to ctrl+alt+delete. After team killing the AI and subsequent failure of the mission I was able to close the game with the mouse.

Once back in windows the keyboard was still unresponsive. Unable to toggle caps lock or type within windows.

after a reset functionality is restored.

Details

Legacy ID
3628559134
Severity
Block
Resolution
Fixed
Reproducibility
Always
Category
Controls
Steps To Reproduce
  1. Load Arma 3 alpha from Steam.
  2. Load Infantry Showcase
  3. Begin the mission and walk around the first bend where the rock is and first contact with enemy is made.
  4. approx 30 seconds after reaching the bend in the valley the keyboard becomes unresponsive.
Additional Information

Mouse: Logitech G5 laser mouse
Keyboard: Microsoft SideWinder X4
Controller: Razer Onza Tournament Edition gamepad

Event Timeline

Muppet edited Steps To Reproduce. (Show Details)Mar 6 2013, 4:54 AM
Muppet edited Additional Information. (Show Details)
Muppet set Category to Controls.
Muppet set Reproducibility to Always.
Muppet set Severity to Block.
Muppet set Resolution to Fixed.
Muppet set Legacy ID to 3628559134.May 7 2016, 10:46 AM
Muppet added a subscriber: Muppet.
Muppet added a comment.Mar 6 2013, 5:37 AM

The Xbox controller also dies, only the mouse remains functional.

This also happened on the helicopter showcase. Roughly 60 seconds in during take off in the chopper the keyboard and xbox controller becomes unresponsive which also persists into windows once the game is closed.

Muppet added a comment.Mar 6 2013, 9:10 AM

I have a few application error here that occur at the time of the problem but the game does not actually crash.

EventData

   arma3.exe 
   0.5.102.571 
   512deb6a 
   arma3.exe 
   0.5.102.571 
   512deb6a 
   c0000005 
   00808a83 
   f94 
   01ce1a3e1f760c39 
   D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
   D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
   5d86c846-8631-11e2-be6d-902b343d289d

EventData

arma3.exe 
0.5.102.571 
512deb6a 
ntdll.dll 
6.2.9200.16420 
505aaa82 
c0000005 
00061b06 
f94 
01ce1a3e1f760c39 
D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
C:\Windows\SYSTEM32\ntdll.dll 
5de2733c-8631-11e2-be6d-902b343d289d

EventData

   arma3.exe 
   0.5.102.571 
   512deb6a 
   arma3.exe 
   0.5.102.571 
   512deb6a 
   c0000005 
   00808a83 
   4c 
   01ce1a3e4fef06ef 
   D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
   D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
   8db323fe-8631-11e2-be6d-902b343d289d

EventData

arma3.exe 
0.5.102.571 
512deb6a 
arma3.exe 
0.5.102.571 
512deb6a 
c0000005 
00808a83 
7a8 
01ce1a3ed075db70 
D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
D:\Games\Steam\steamapps\common\Arma 3\arma3.exe 
0e337fd3-8632-11e2-be6d-902b343d289d

Please add debug.log from C:\Users\<Name>\AppData\Local\Arma 3 Alpha\
Thank you

recently I bought a few SSD's, due to this I re-imaged my machine. Even though I used the same drivers and version of Windows 8 I am now unable to replicate the issue at all on my new install.

I have been able to play through all 4 missions and some MP. Having said that, I have not yet plugged in my razer xbox controller since re-imaging. I'll do some more testing see if there is any conflict.

I have a sidewinder X4 too,

My keyboard work but i can't use macro key :(

This issue turned out to be a problem between Windows 8 xHCI Usb 3.0 drivers and the Intel Z77 platform.

Some usb device combinations (for me; razer onza xbox 360 controller and logitech usb microphone) cause a conflict in the driver and it fails to rout the device to the ECHI controller (Usb 2.0) or the xhci controller (usb 3.0).

Resulting in the effected devices to become disabled. Going in the bios and setting xHCI routing to enabled from either Auto or Smart Auto seems to have restored stability so far...

http://www.intel.com/support/chipsets/usb3/sb/CS-033962.htm

Seems to have been fixed by user.