Page MenuHomeFeedback Tracker

Commanding UI is too slow
Closed, ResolvedPublic

Description

This has carried over from ARMA 2.

This may not be a major issue for most people, but if you, like me, know every radio command by heart, then it is.

Basically, if you're fast at issuing commands, the current UI is a bottleneck for you.

You have to wait a little between commands.

Eg. If I want my units to stand up and relax, I would press (Note that the key to the left of digit 1 is ½ for me, which selects all units):

½,7,6,½,7,4

This is
ALL, Stand up
ALL, At ease

However, the UI does not respond to presses within like 200-300 ms from the last one.

So, after pressing ½,7,6 for stand up, you have to wait. If you don't, it will ignore ½ and 7 of your next command, and only registers the 4. Thus, you end up with no units selected in the Mount menu.

Having to wait 300+ ms between commands, drastically slows down commanding.

Details

Legacy ID
2905515428
Severity
Major
Resolution
Suspended
Reproducibility
Have Not Tried
Category
Ingame UI
Additional Information

Event Timeline

MulleDK19 edited Steps To Reproduce. (Show Details)Mar 9 2013, 4:19 AM
MulleDK19 edited Additional Information. (Show Details)
MulleDK19 set Category to Ingame UI.
MulleDK19 set Reproducibility to Have Not Tried.
MulleDK19 set Severity to Major.
MulleDK19 set Resolution to Suspended.
MulleDK19 set Legacy ID to 2905515428.May 7 2016, 11:53 AM

Just tested in latest dev build - using the command UI seems instantaneous, therefore closing as fixed.

If this issue is still reproducable for you, please create a new ticket for it.

Re-opening as requested.

However, I still cannot reproduce this bug. Even placing my fingers over the number keys and hitting them as fast as possible, all commands are executed.

Then you're not doing it fast enough. Check out the video.
The keyboard overlay at the top is input registered by software.

Nope, I type pretty fast.

Though I noticed that the framerate in that video looks pretty low, which might be a factor. What kind of FPS do you get in-game?

EDIT: Okay, watching with sound explains a lot - you slowed it down. :)

Still, even hammering on the keys almost simultaneously I can't reproduce this issue. The only thing I can think of is that you might be a victim of the input lag some people seem to be experiencing, and this may be a symptom. Do you experience any mouse lag or similar issues?

The FPS does not matter. This issue has existed since the first iteration of ARMA.

The framerate in the video is 30fps. At the time of recording the game was running 102fps.

I've even tried slowing down the game (NOT setAccTime. I wrote an external program to slow timing functions), and the commanding UI does NOT process key presses right after issuing a command.

Nine commands in 1.5 seconds? This isn't StarCraft, dude.
Typing §72§77 as quick as I can they do what I tell them to. Doing it quicker or a longer string of commands I mess up more often than not. So the only issue I can tell is human error though your video convincing enough otherwise.

Fank added a subscriber: Fank.May 7 2016, 11:53 AM
Fank added a comment.May 13 2014, 11:36 PM

@MulleDK19 could you try it with the current version?

I don't seem to be able to reproduce this. I've also tried voice recognition software called Articulate which is designed specifically for Arma 3 and that issues the keypresses in as little as 10ms between presses with no issues.

when I do it fast, the command lags, but no matter how fast I press, the commands always execute.
Even if I press "~, 5, 5" (you guy's § and ½ is my ~) extremely fast, in game I will still call "SITREP," even if it takes about 1/2 second for the menu to progress from each step to the next.
*presspresspress*
*all units selected*
*step through first stage*
(½ second)
*selects SITREP*
(½ second)
"SITREP"

(on an unrelated note, what countries are you guys from? Just wondering what kinds of keyboards have ½ and § as their key to the left of 1. I have ` and ~)

Fank added a comment.May 14 2014, 5:57 PM

Issue closed as obsolete, it was an Alpha issue. If you encounter this problem again, please create another ticket. Thank you.