[SOLVED] Callbacks Increase/Decrase by 5 won't work
-
I’ve a problem with ALL callbacks that invoke “5er” steps -> they all just increase/decrease by 1.
I’m talking about:
HSI Heading
HSI Course
Altimeter PressureThere are different callbacks for Increase/Decrease by 5 and by 1. However all of the 5er callbacks behave like the 1s.
I’ve read through the keyfile manual and all other documentation, but I could not find anything that would help me.
Any ideas?
-
From BMS Manual, pg 247:
g_nKnobAccelerationDelta
When set to 0 it will make the “By1” and default “By5” callbacks
work without acceleration, i.e. By1 =1 and By5=5. Default = 60
milliseconds in which the next input has to occur. If
g_nKnobAccelerationDelta is not 0 it will not change the “By1”
callbacks at all. Instead the “Normal” callbacks will behave as
“By1” if used once and accelerated to “By5” if used in rapid
succession. Basically if you move the controls slowly you get
By1 increment, if you move them faster you get By5
increments. Use SimHsiCourseInc, SimHsiCourseInc,
SimHsiCourseDec, SimHsiHeadingInc, SimHsiHeadingDec
SimAltPressInc, SimAltPressDec, SimHsiCourseDec,
SimHsiHeadingInc, SimHsiHeadingDec, SimAltPressInc
SimAltPressDec “normal’ callbacks for acceleration to work, not
the By1 callbacks. -
I believe:
1. g_nKnobAccelerationDelta is to be in the falcon bms.cfg file found in your …user\config folder.
2. the syntax is “set g_nKnobAccelerationDelta = x” where ‘x’ is the deadline in milliseconds that you must meet between callbacks before you get the by 5 bump.Also, I am not 100% sure the manual is correct on this topic just from what others have told me. IIRC and as I understood it, I was told that it doesn’t matter what callback you use the behavior is the same depending on your falcon_bms.cfg g_KnobAccelerationDelta is set. I actually don’t know what is true because I just wrote a voice macro and assign heading and course by voice (using VAC). I’ll be testing this in the coming months though as I am building a button box and I want to see if accelerating the rotary encoders By5 feels good or not.
I suspect all of this is a tip of the hat to pitbuilders and that acceleration depending on the callback interval is generally preferable. In this way, as a pitbuilder, you only have to deal with one call backback per electro-mechanical switch. Otherwise, you might try to solve the issue by having two knobs to increase/decrease course and that’s obviously less than optimal.
-
From my blog page:
For the Altimeter and HSI functions to work, the falcon bms.cfg file must be edited and this entry added at the first space at the top:
set g_nKnobAccelerationDelta 300Works in my Helios profile.
-
Thank you guys!
After setting g_nKnobAccelerationDelta to 0 the buttons work as expected.
I’ve read through the keyfile manual twice and also looked in the standard manual but I just did not expect to find anything in this section of the manual…
Thank you!
-
Thank you guys!
After setting g_nKnobAccelerationDelta to 0 the buttons work as expected.
I’ve read through the keyfile manual twice and also looked in the standard manual but I just did not expect to find anything in this section of the manual…
Thank you!
So, you are using the By5 callback and that works on the first keystroke?
-
So, you are using the By5 callback and that works on the first keystroke?
There are two sets of callbacks, one for a 1-increment and another for a 5-increment. Obviously, one press of the appropriate key binding will give the appropriate result, whether 1-increment or 5-increment.
-
There are two sets of callbacks, one for a 1-increment and another for a 5-increment. Obviously, one press of the appropriate key binding will give the appropriate result, whether 1-increment or 5-increment.
Actually, I don’t think that is right assuming all default settings.
If I have this in my head right: you have two different callbacks SimHsiHeadingInc (I’ll call this By5) and SimHsiHeadingBy1 for example.
By5 is mapped by default to 0x28 0 which is the [‘] key.
By1 is mapped by default to 0x28 1 which is the [Shift] + [’] keys.As I recall by default there is no g_nKnobAccelerationDelta entry in the falcon_bms.cfg file and I was experiencing the same exact thing as was the OP (at least to my understanding of what was happening to him). If I pressed the [‘] key or the [Shift] + [’] keys the HSI ticked up only by 1 either way.
Just to check my memory, I just now tested the configuration above in an ITO F16 pit and the result is the same. 1 degree of change regardless of the By1 or By5 callback. I went ahead and added set g_nKnobAccelerationDelta 0 and only now is it moving By5 on the first and every keypress of [‘] and By1 on every keypress of [Shift]+[’].
-
Like I said….
For the Altimeter and HSI functions to work, the falcon bms.cfg file must be edited and this entry added at the first space at the top:
set g_nKnobAccelerationDelta 300I don’t quite remember where I got the 300 from but this was from my 4.32 profile so I just kept it.
Also, I think “by default” is misleading… it depends which .key file you’re using. The Full .key file has it as 0x28 but the Pitbuilder .key file has it as 0xD2.
-
Reviving this thread as I’m all of a sudden experiencing issues in 4.34 with this.
Situation 1: vanilla 4.34 with “full” keyfile.
- Mouse scroll in 3D over pressure knob of altimeter: works
Situation 2: same as above + added SimAltPressInc & SimAltPressDec to my SYM rocker switches of my TM MFD’s
- Pressing rockers on MFDs in 2D controls UI: correct lines show up as being pressed
- Mouse scroll in 3D over pressure knob of altimeter: works
- Pressing both rocker switches on MFDs in 3D: works
Situation 3: Programm encoder via Pokeys to trigger the key combos of the inc/dec.
- Pressing rockers on MFDs in 2D controls UI: correct lines show up as being pressed
- Rotating encoder both ways in 2D controls UI: correct lines show up as being pressed
- Mouse scroll in 3D over pressure knob of altimeter: does nothing, but I hear the ‘clicking’ sound in the pit
- Pressing both rocker switches on MFDs in 3D: does nothing
- Rotating encoders in 3D: does nothing, but I hear the ‘clicking’ sound in the pit
Situation 4: same as above but added set SimAltPressInc 0 in falcon bms.cfg
- All actions as done in situation 3 result in same behavior
Situation 5: same as above but changed g_nKnobAccelerationDelta to 300
- Same issue
Situation 6 etc: tried with callbacks to SimAltPressInc/Dec as SimAltPressIncBy1/DecBy1 in situation without g_nKnobAccelerationDelta, set to 0 & set to 300.
- Same issue all over again
Anyone knows what I did wrong. I don’t understand what could have triggered it based on all the scenario’s I’ve tried by now.