Allow us to disable the staging delay

[Temeter]

If you don't know what this is about: After staging there is a small delay until you can stage the next time. This was introduced in a patch over 2 years ago. Idea is to help avoid accidental staging.

 

And frankly, this 'feature' is infuriating at times, while having very little real benefit for anyone without major motorical problems with his or her hands - I know it certainly never helped me in the last 2 years of play, while killing a few crafts that could've been at least partly recovered. Whenever a craft, launch or operation fails, it's often time critical to stage as fast as possible, and sometimes also just because you messed up the staging or build a complex craft relying on fast staging. In more common flight, it's sometimes just plain annoying.

I don't even get who this is supposed to help. Who accidently presses a button, even moreso one as large as space, 2 times in a row? I managed to tip this post, over 1400 letters, without getting double letters a single time. The easy to make mistake with staging is accidental staging, but that's pretty much unavoidable as long as the the function has to be 100% ready at all times - and even then, it just doesn't really matter in the long run, the game plays fine. Then punishing successive staging is highly inconsequent.

 

If you don't want to remove this option (and this is not the first time this is brought up), can we please at least get an option to disable it?

Edited October 19, 2016 by Temeter

[Stargate525]

40 minutes ago, Temeter said:

I managed to tip this post, over 1400 letters, without getting double letters a single time.

You did manage to miss a pair of them, though.

One of the side-effects of lag is that keystrokes sometimes don't register, or take a moment to do so. I know personally when I'm having key input lag, the spacebar is the one that suffers the most. having the delay allows a bit of a breather-room for someone who assumed that the first didn't register, pressed again, only to discover the first one hadn't fired yet.

[Allocthonous]

Could be a good option. While they're at it, an arm-then-stage option using two separate keys would be nice. I've had to revert a few flights because I accidentally staged out a fully fueled section prematurely.

[Wjolcz]

I don't mind the delay actually. I guess the intention was to delay the decoupler-engine exhaust contact. I remember blowing up the upper bits of the previous stage many times in the past.

For the rest I just use action groups.

[Temeter]

7 hours ago, Stargate525 said:

You did manage to miss a pair of them, though.

One of the side-effects of lag is that keystrokes sometimes don't register, or take a moment to do so. I know personally when I'm having key input lag, the spacebar is the one that suffers the most. having the delay allows a bit of a breather-room for someone who assumed that the first didn't register, pressed again, only to discover the first one hadn't fired yet.

I've played a lot with lag, had some ~1400 part crafts. Can't remember a single time the space button didn't register.

And it got actually worse with the delay: Imagine you got a lot of lag and you need to stage two times successively. Then you are loveed by the safety, because it's really hard to tell when it works and when not.

Hence there should be an option.

[Padishar]

There is an option but it is hidden away in Physics.cfg for some reason rather than being in settings.cfg:

stagingCooldownTimer = 0.5625 // The time in seconds after staging during which one cannot stage again.

Edit: incidentally, I'd recommend not setting this lower than 0.05 or so (and definitely not lower than 0.02) to reduce the chances of something weird happening if the game processes some aspect of the staging event over more than one physics tick and two of them overlap (or even, with a value lower than 0.02, it would be possible to trigger two staging events on consecutive rendered frames with no physics ticks between them).

Edited October 19, 2016 by Padishar