ButtonD Press Delay is ignored

Moderator: AdminGroup

jukelo
Posts: 68
Joined: Fri Aug 18, 2023 0:25
Has thanked: 1 time
Been thanked: 8 times

ButtonD Press Delay is ignored

Postby jukelo » Thu Jan 16, 2025 17:21

Issue: When holding a ButtonD button (and not pressing the Master button), the Press Delay option is ignored. Instead, the ButtonD's virtual button will only fire after ~150ms have elapsed.

Firmware: 2.18.F, 2.18.D, 2.18.5, 2.15.1
Software: v0.93.18

Steps:
On default config EVO SCE,
  • Set up Physical 10 as Button D. Master = Physical 9, Press Delay = 10ms.
  • In the Test tab, press the first trigger stage, without going to the second stage:
    • Logical 1 fires after a delay much longer than 10ms

Screenshot 2025-01-16 150525.png


Setting up a 2AND boolean firing virtual 121 as soon as the ButtonD Physical button is pressed and turning off when the ButtonD virtual button fires allows one to measure (roughly) the Press Delay duration (plus or minus the overhead from executing the boolean):
Screenshot 2025-01-16 150629.png

Screenshot 2025-01-16 150732.png


Virtual 151 here appears to be pressed for approximatively 150ms between activation of Physical 10 and activation of Virtual 10, which is the max Press Duration.

When testing with 2.15.0 (which does not have a Press Delay option), the Boolean registers a press duration for Virtual 121 between 16 and 32ms.
Screenshot 2025-01-16 151658.png

User avatar
Alex Oz
Posts: 1228
Joined: Mon May 12, 2008 9:10
Location: Минск
Has thanked: 22 times
Been thanked: 131 times

Re: ButtonD Press Delay is ignored

Postby Alex Oz » Thu Jan 16, 2025 23:59

there are acceptable delay ranges for this function:
https://www.njoy32.vkb-sim.pro/home/inp ... ns/buttons

Code: Select all

Delay parameters:

Press - delay in turning on the 1st button when pressing the trigger. The delay allows you to "skip" the button press when pressing quickly. Recommended values ​​- 20-40 mS

Release - delay in turning on the Master Button button after releasing the 2nd button. Allows you to "skip" pressing the 1st button when fully releasing the trigger. Recommended values ​​- 60-100 mS
Крайние прошивки и софт / Latest firmware & software
https://www.njoy32.vkb-sim.pro/home
http://alex-oz.strana.de

Icer_CRO
Posts: 4
Joined: Sat Dec 11, 2021 13:13

Re: ButtonD Press Delay is ignored

Postby Icer_CRO » Sun Feb 02, 2025 18:02

Sorry for resurrecting this old question, but I can't get any delay options with VKB Config 0.93.17 (Have the GF Ult TW XT2 v2.115)

Has this been dropped completely? The manual states the various delay options, as does this post...
Attachments
VKB_ButtonD.png

jukelo
Posts: 68
Joined: Fri Aug 18, 2023 0:25
Has thanked: 1 time
Been thanked: 8 times

Re: ButtonD Press Delay is ignored

Postby jukelo » Tue Feb 04, 2025 14:15

The delay options for ButtonD were introduced in firmware v2.15.0

jukelo
Posts: 68
Joined: Fri Aug 18, 2023 0:25
Has thanked: 1 time
Been thanked: 8 times

Re: ButtonD Press Delay is ignored

Postby jukelo » Wed Feb 19, 2025 15:36

Alex Oz wrote:there are acceptable delay ranges for this function:
https://www.njoy32.vkb-sim.pro/home/inp ... ns/buttons

Code: Select all

Delay parameters:

Press - delay in turning on the 1st button when pressing the trigger. The delay allows you to "skip" the button press when pressing quickly. Recommended values ​​- 20-40 mS

Release - delay in turning on the Master Button button after releasing the 2nd button. Allows you to "skip" pressing the 1st button when fully releasing the trigger. Recommended values ​​- 60-100 mS


The problem is that the Press delay setting entered by the user is ignored and is instead forced to be ~150ms regardless. A Press Delay value of 20-40ms will suppress the first stage's virtual for 150ms, just like a Press Delay of 80ms (or 0ms) will.
This makes it impossible to ignore the 'skip' behaviour or adjust its delay.

Holding the first stage of the trigger (not pressing the second stage) I use Virtual 121 in this setup to measure the delay between the press of physical 10 and the activation of virtual 10, giving me an (approximate) measurement of the actual Press Delay value.
ButtonD_40ms_Phys.png
ButtonD_40ms_Bool.png


Virtual 121 should be released after ~40ms of being pressed, instead I get 145ms:
ButtonD_40ms_Result.png


Adjusting ButtonD Press Delay to 110ms, I get 155ms on the Virtual 121 press duration instead of ~110ms.
ButtonD_110ms_Phys.png
ButtonD_110ms_Result.png


By comparison and to validate the measurement method using Virtual 121, here is a reproduction of the ButtonD behaviour using booleans which respects the 'Press Delay' value (set by adjusting the duration of the Boolean 1 pulse length). Physical 10, the trigger first stage, is set to 'NoF', Virtual 10 is left to default Logical 1.
BoolD_setup.png


With a Boolean 1 pulse length of 40ms, I measure (using virtual 121) a press duration of ~48ms, good enough:
BoolD_40ms_Bool.png

BoolD_40ms_Result.png


With a Boolean1 pulse length of 110ms, I get a press duration of 112ms, a close match again:
BoolD_110ms_Bool.png

BoolD_110ms_Result.png


Return to “Technical Support”

Who is online

Users browsing this forum: Bing [Bot] and 9 guests