HSI CRS and HDG Bug not advancing w/5deg Setting

[dawgboy]

I’m using the VKB STECS Mini+ for HSI key mappings, and I have the TM WH stick’s pinky switch enabled for “Pinky Switch (DX Shift)”. On the STECS, I’ve mapped the HSI CRS and HDG Bug knobs to use the DX keybinds for 1deg unshifted, and 5deg shifted. They work properly in the Launcher “KeyMapping” tab and in 3D VR worlds. However, in the 3D VR world, the shifted 5deg functions don’t work…I get only 1deg of HDSI movement across the 4 buttons.

In the falcon.cfg file, the PinkyShiftMagnitude is 256. This is what is in the non-edit section of my user.cfg file (1792), which I have no idea if it is correct or not. I also don’t know if the ButtonsPerDevice is correct at 128, or not.

// LAUNCHER OVERRIDES BEGIN HERE - DO NOT EDIT OR ADD BELOW THIS LINE
set g_nButtonsPerDevice 128 // SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 1792 // SETUP OVERRIDE
set g_nNumOfPOVs 2 // SETUP OVERRIDE
set g_nPOV1DeviceID 4 // SETUP OVERRIDE
set g_nPOV1ID 0 // SETUP OVERRIDE
set g_nPOV2DeviceID 14 // SETUP OVERRIDE
set g_nPOV2ID 0 // SETUP OVERRIDE

Here are the lines out of the auto.key file, which is the latest modified KEY file:
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======== 4.07 MAIN INSTRUMENT ========”
SimHsiHeadingInc 116 0 0x28 0 0 0 1 “MAIN: HSI HDG Knob - Increase (5°)”
SimHsiHeadingDec 116 0 0x27 0 0 0 1 “MAIN: HSI HDG Knob - Decrease (5°)”
SimHsiHdgIncBy1 116 0 0x28 1 0 0 1 “MAIN: HSI HDG Knob - Increase (1°)”
SimHsiHdgDecBy1 116 0 0x27 1 0 0 1 “MAIN: HSI HDG Knob - Decrease (1°)”
SimHsiCourseInc 116 0 0x28 2 0 0 1 “MAIN: HSI CRS Knob - Increase (5°)”
SimHsiCourseDec 116 0 0x27 2 0 0 1 “MAIN: HSI CRS Knob - Decrease (5°)”
SimHsiCrsIncBy1 116 0 0x28 4 0 0 1 “MAIN: HSI CRS Knob - Increase (1°)”
SimHsiCrsDecBy1 116 0 0x27 4 0 0 1 “MAIN: HSI CRS Knob - Decrease (1°)”

Am I missing something simple or? Any ideas/clues, pls?

UPDATE: BMS 4.37.6. I used to understand the KEY files and their operations. After A/L was introduced, not so much.

Thanks in advance.

[airtex2019]

@dawgboy what is your g_nKnobAccelerationDelta

Search the forum for that, to learn more about how that mechanism works

[dawgboy]

@airtex2019 said in Pinky Shift Not Working:

@dawgboy what is your g_nKnobAccelerationDelta

Search the forum for that, to learn more about how that mechanism works

I referenced two different posts:
Bug Report

and this one on the forum

I added this line to falcon BMS.cfg file:
set g_nKnobAccelerationDelta 300

No joy…both the 1 deg and 5 deg still only advance 1 deg per button push. I have not modified my encoder, as the BMS Forum item suggested.

UPDATED: It’s working…I was not pressing the buttons fast enough in rapid succession to kick in the rapid movement. Thanks for your help.

[Big_one]

@dawgboy
I had the same problem.

set g_nKnobAccelerationDelta 250// msec delay between subsequent keypresses, to rotate knobs 5° instead of 1°

Did the trick for me, you have to enter this in Falcon BMS User.cfg ABOVE the line:
// LAUNCHER OVERRIDES BEGIN HERE - DO NOT EDIT OR ADD BELOW THIS LINE

[dawgboy]

@Big_one and @airtex2019

It’s working…I was not pressing the button fast enough to kick in the rapid advance. Thanks for your help.

[oakdesign]

@dawgboy which is what the value of

set g_nKnobAccelerationDelta

is made for to be adjusted to your likings in order to set what is your preferred time delta to reconginze BMS a 1° push or 5° push

UPDATE: BMS 4.37.6. I used to understand the KEY files and their operations. After A/L was introduced, not so much.

BTW the keyfiles and their operations have not changed regardless if you use Launcher, the Launcher in terms of keyfile just takes the task of writing them, the content of the keyfile and how the callbacks are in there is still the same

[dawgboy]

@oakdesign said in HSI CRS and HDG Bug not advancing w/5deg Setting:

Thanks for the insight.

BTW the keyfiles and their operations have not changed regardless if you use Launcher, the Launcher in terms of keyfile just takes the task of writing them, the content of the keyfile and how the callbacks are in there is still the same

Well, maybe it’s imaginary, but now I feel “like a hog lookin’ at a wristwatch”…i.e., clueless.