Azeron Software v1.5.5 Bug: "Long Press" incompatible with games

[SoraKagami]

Summary:​

The "Long Press" feature works for general window use. However for games, at least those that I tired, they fail to register the "Single Press" keyboard assignment most of the time when "Long Press" is also enabled for the key.
Affected Games:
* Dead by Daylight
* No Man's Sky
(and probably most Unreal Engine based games)

To Replicate:​

1. Setup a key on a Cyborg Compact with Azeron Software v1.5.5 that uses both "Single Press" and "Long Press" for the same key
2. Play No Man's Sky (or Dead by Daylight, harder to test tho)
3. Make sure two different keybinds are bound to the keys assigned for "Single Press" and "Long Press" (Example "Single Press" set to the escape key, "Long press" set to do something like fire the weapon).
4. Test both "Single Press" and "Long Press"

Expected:​

Both Single and Long press should work

What actually happens:​

Most of the "Single Press" inputs are missed by the game.

Hypothesis:​

Game Engines may be missing the "Single Press" input possibly due to too short a "press" and "release" key input, i.e. press and release occurs within the same "frame" or input checks timeframe & one of the two conditions, or both are missed.

​

Software Info:​

* Windows 10 22H2
* Azeron Cyborg Compact
* Azeron Software v1.5.5
* Affected Games: Dead by Daylight, No Man's Sky (etc.)
* Unaffected Software: Windows Notepad, Textpad, Notepad++

 

[Im this guy]

Summary:​

The "Long Press" feature works for general window use. However for games, at least those that I tired, they fail to register the "Single Press" keyboard assignment most of the time when "Long Press" is also enabled for the key.
Affected Games:
* Dead by Daylight
* No Man's Sky
(and probably most Unreal Engine based games)

To Replicate:​

1. Setup a key on a Cyborg Compact with Azeron Software v1.5.5 that uses both "Single Press" and "Long Press" for the same key
2. Play No Man's Sky (or Dead by Daylight, harder to test tho)
3. Make sure two different keybinds are bound to the keys assigned for "Single Press" and "Long Press" (Example "Single Press" set to the escape key, "Long press" set to do something like fire the weapon).
4. Test both "Single Press" and "Long Press"

Expected:​

Both Single and Long press should work

What actually happens:​

Most of the "Single Press" inputs are missed by the game.

Hypothesis:​

Game Engines may be missing the "Single Press" input possibly due to too short a "press" and "release" key input, i.e. press and release occurs within the same "frame" or input checks timeframe & one of the two conditions, or both are missed.

​

Software Info:​

* Windows 10 22H2
* Azeron Cyborg Compact
* Azeron Software v1.5.5
* Affected Games: Dead by Daylight, No Man's Sky (etc.)
* Unaffected Software: Windows Notepad, Textpad, Notepad++

Discord - Group Chat That’s All Fun & Games

Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.

discord.com

 

[someusername]

Any updates on this?

Having the same issue with Dune Awakening. Single presses dont register in game 90% of the time if the same button has a long press set. Works fine in notepad or some other Windows app. Unrelated to trigger delay.

Windows 11 Pro 24H2
Cyborg Compact
Azeron Software 1.5.5

 

[Im this guy]

Any updates on this?

Having the same issue with Dune Awakening. Single presses dont register in game 90% of the time if the same button has a long press set. Works fine in notepad or some other Windows app. Unrelated to trigger delay.

Windows 11 Pro 24H2
Cyborg Compact
Azeron Software 1.5.5

No updates yet.

 

[Im this guy]

Any updates on this?

Having the same issue with Dune Awakening. Single presses dont register in game 90% of the time if the same button has a long press set. Works fine in notepad or some other Windows app. Unrelated to trigger delay.

Windows 11 Pro 24H2
Cyborg Compact
Azeron Software 1.5.5

Tested it on Dune, no issues here.
Export the log file from settings / troubleshooting and attach here

 

[someusername]

I attached the log file. Used key #16 for input "1". Works fine as long as no long press is set. Then I set input "2" as long press for key #16. Input "1" not working any more. Trigger delay 200ms. Also made a video for this: https://limewire.com/d/sJXAN#O45ubfANDk

My guess is that the input is too short for the game to register. You can barely see it in the video but I'm clicking #16 ("1") multiple times at second 0:25 and the key is flashing very shortly in the azeron software window. You can see this better at 0:47.
Notepad works fine (second 0:40 - 0:46).
Increasing the delay and pressing the button slightly longer still results in very short single key presses send by the software.

 

[Im this guy]

I attached the log file. Used key #16 for input "1". Works fine as long as no long press is set. Then I set input "2" as long press for key #16. Input "1" not working any more. Trigger delay 200ms. Also made a video for this: https://limewire.com/?referrer=pq7i8xx7p2

My guess is that the input is too short for the game to register. You can barely see it in the video but I'm clicking #16 ("1") multiple times at second 0:25 and the key is flashing very shortly in the azeron software window. You can see this better at 0:47.
Notepad works fine.
Increasing the delay and pressing the button slightly longer still results in very short single key presses send by the software.

Set button throttle to 0 and change the mode, see if that changes anything

 

[someusername]

Tried both modes, throttle 0. No Change.

 

[Im this guy]

test with higher throttle, 15 and up

 

[someusername]

Tested both modes up to 50. No change. This doesnt seem to affect the "lenght" of the single press command (when long press is set as well for the same key) at all. What are your settings that work in Dune?

 

[Im this guy]

Tested both modes up to 50. No change. This doesnt seem to affect the "lenght" of the single press command (when long press is set as well for the same key) at all. What are your settings that work in Dune?

Tried various trigger delays and had no issue in Dune.
Not sure why it`s causing issue only for one user, whilst others are not affected

 

[someusername]

Hmm probably some differences in underlying system configs, polling rates, etc. Seems like a complex problem.
I just tested with higher frame rates. Had it locked at 60fps, button presses worked 1/10. With around 180fps, button presses work 9/10 but still not 100%.

 

[Im this guy]

Hmm probably some differences in underlying system configs, polling rates, etc. Seems like a complex problem.
I just tested with higher frame rates. Had it locked at 60fps, button presses worked 1/10. With around 180fps, button presses work 9/10 but still not 100%.

I remember it testing a while back on superglides in Apex.
Had to play around with the settings to get it constant.