Slow Key Recognition [1.5.1.46722]

[JLX]

When assigning HOTAS buttons, often (but not always) the depressed button will not register and I must hold the button down before it is recognized. It appears to be just when configuring my keys as they seem to work fine while flying.

 

This delayed behaviour (which was present for me in 1.2.6 and earlier) went away in the first 1.5.0 builds and all my joystick keys registered instantly when setting up my binds. However, it's back now with 1.5.1

 

I'm wondering if it might be related to a problem (and others like it) mentioned in this thread. Here's a excerpt:

 

EDIT3: FFS, I found the problem.

It's the good old depress bug DCSW has always had, where the cockpit triggers have a big chance of not firing if you don't keep pressed the button for a few moments.

Since it was manual release I was just pressing the pickle button on the HOTAS for an instant, while it seems to register fine if I keep it pressed for half a second or so.

 

I realize this is a bit obscure but it may help narrowing it down if it's related to changes introduced in 1.5.1

 

Edit: I'm running DCS vanilla with no mods.

Edited November 9, 2015 by JLX

[m2b1]

Sometimes when I run a quick mission, respond no more keys ?!

[too-cool]

When assigning HOTAS buttons, often (but not always) the depressed button will not register and I must hold the button down before it is recognized. It appears to be just when configuring my keys as they seem to work fine while flying.

 

This delayed behaviour (which was present for me in 1.2.6 and earlier) went away in the first 1.5.0 builds and all my joystick keys registered instantly when setting up my binds. However, it's back now with 1.5.1

 

I'm wondering if it might be related to a problem (and others like it) mentioned in this thread. Here's a excerpt:

EDIT3: FFS, I found the problem.

It's the good old depress bug DCSW has always had, where the cockpit triggers have a big chance of not firing if you don't keep pressed the button for a few moments.

Since it was manual release I was just pressing the pickle button on the HOTAS for an instant, while it seems to register fine if I keep it pressed for half a second or so.

I realize this is a bit obscure but it may help narrowing it down if it's related to changes introduced in 1.5.1

 

Edit: I'm running DCS vanilla with no mods.

I'm having the same problem in both 1.5 and 2.0, seems it takes for ever to fire rockets or drop bombs. TC

[Grand]

Same problem here, though it seem I have it more often while assigning keys than in the pit itself, fortunately.

[Feuerfalke]

Same problem here.

 

X-Keys-Keyboards are no longer recognized.

Even if I artificially slow them down.

 

Keyboard input of the same commands still works.

 

 

CH gear still works, too, but sometimes DCS doesn't respond as it did. :(

[Chief1942]

And I thought I was having keyboard issues. I hadn't noticed the issue with previous iterations (1.2.16 or 1.5.1) , just when I started inputting my key binds in 2.0. Will stand by and see if ED gets it corrected.

[Bobby]

:joystick:

 

+1

 

Hotas Cougar

[Feuerfalke]

Bug still present.

[Feuerfalke]

1.5.2.48162 same result.

 

Input from all 3 X-Keys-devices are not recognized.

1 in software, 2 in hardware-mode.

I can even set keys to being pressed as long as I hold the key.

DCS doesn't recognize the input. :(

 

They work perfectly in other games.

[Chief1942]

Yes, still there for me as well. Works fine in 1.2 but it's a crap shoot whether or not you get a response from key presses in either the updated 1.5 or 2.0. Something changed.

[Dachs]

Just wanted to join the choir, I have the same problem, both in 1.5.2 and 2.0

[Feuerfalke]

Tried to update driver and narrow down the cause.

To no effect.

 

Works perfect in 1.2 with all settings and drivers.

No joy in 1.5 and 2.0 - literally...

[esb77]

I had this happen to me when trying to configure controls for the Su-25T on a thrustmaster X flight hotas. It took long and/or repeated presses to register keybinds.

 

 

Also had an issue where none of the F key view commands worked, even when rebound several times.