Page MenuHomeFeedback Tracker

Quick Bar not responsive to keystrokes
Closed, ResolvedPublic


items in the quick bar take 1 to 3 presses of the corresponding slot
IE: 1,2,3,4,5 ...


Legacy ID
Steps To Reproduce
  • put items in the quick bar slot (slot 1 : gun, slot 2: axe)
  • empty hands of items
  • use quick slot item to select or change items (#1:gun, #2:axe)
  • notice if there is any sluggish or delay action corresponding to equipping items.

Event Timeline

exogravis set Category to Controls.
exogravis set Reproducibility to Always.
exogravis set Severity to None.
exogravis set Resolution to Duplicate.
exogravis set Legacy ID to 2291693805.May 8 2016, 2:14 PM
Bohemia added a subscriber: Bohemia.May 8 2016, 2:14 PM

double press for equipping is normal....

i noticed that as well. it's frustrating at times.

Coonsaa added a subscriber: Coonsaa.May 8 2016, 2:14 PM

Same here, super annoying having to hit the button three times when a zed is chasing you.

Have this issue also with the Vault key

Yep getting the same nonsense. Sometimes I have to click twice, sometimes three. Sometimes the character will holster the weapon again, if you click twice. Real annoying.

Gecrap added a subscriber: Gecrap.May 8 2016, 2:14 PM

Yep, can confirm. Seems to happen most on busy servers, clicking the 1 key multiple times to get my rifle out only to have it immediately holster again if It registered more than 1 key stroke.

This is still occurring in the new .46 experimental build. Had to press '1' 8 times to get it to change weapons. The server was somewhat full at the time but other actions such as eating and drinking were much more responsive. Please look into this!

This is worse in the current experimental build than the current stable build, the reason is probably related to the amount of rubberbanding we are also seeing.

Still occurring in new .47 experimental. :/

Akaris added a subscriber: Akaris.May 8 2016, 2:14 PM

Same issue in 0.48 stable build.

Hello exogravis,

Thank you for sending us your feedback regarding this issue. Unfortunately, this problem is a known issue that has previously been reported.

Closing as duplicate of #363.