No more IncBy5 or DecBy5 callbacks?
-
Hi Ertiyu!
yeah same .key lines as mine, what seems to be missing are those *By5 callback, e.g. we have now SimHsiHeadingInc instead of SimHsiHdgIncBy5, and SimHsiHeadingInc just behave like SimHsiHdgIncBy1Try “set g_nKnobAccelerationDelta 0” then SimHsiHeadingInc etc. should give you by 5.
See Technical Manual 13-163 for more info.
-
Try “set g_nKnobAccelerationDelta 0” then SimHsiHeadingInc etc. should give you by 5.
See Technical Manual 13-163 for more info.
not working, still by 1 steps, that’s why I introduced set g_nKnobAccelerationDelta in the bms config file in the first place, as a tentative to workaround the default bindings for 5 degree steps not working as expected.
-
-
I also did put
set g_nKnobAccelerationDelta to 0 as suggested, and with and without it I get the same +1 behavior for those callbacks, really strange…gonna look at it again tomorrow, not sure what to look at though, weird. -
The alternative launcher, which creates the keyfile upon launch, still has both the +1 and +5 callbacks. So they are still in U2.
I use set g_nKnobAccelerationDelta 250, and I had to do some experiments to figure out the proper value in my case. Depends on hardware latency too
-
I also did put
set g_nKnobAccelerationDelta to 0 as suggested, and with and without it I get the same +1 behavior for those callbacks, really strange…gonna look at it again tomorrow, not sure what to look at though, weird.I use set g_nKnobAccelerationDelta 300 in falcon bms.cfg and e.g.
SimHsiCourseInc 86 -1 -2 0 0X0 0 “MAIN: HSI CRS Knob - Increase (5°)”
SimHsiCourseDec 85 -1 -2 0 0X0 0 “MAIN: HSI CRS Knob - Decrease (5°)”and it works as designed. Means, when I turn the dial slowly it makes steps of ‘1’, if I do it faster it makes steps as ‘5’
4.35 U2
-
Thank you very much for all the feedbacks, then I need a better strategy to hunt down the source of my problem, as it works for you for both the accelerated and normal mode. Will restart my tests from square zero.
-
Ah!
I made a typo in .cfg, I forgot the set in the set g_nKnobAccelerationDelta 0, now default keybindings works as expected in the not accelerated mode, nice!
Still if I remove this set g_nKnobAccelerationDelta 0 from the facon bms.cfg the problem is back, which is the default U2 behavior, so adding this line in U3 might be a good idea.
Also quite surprised that my typo didn’t bring about any error at bms start.Now gonna bind those accelerated dials and play with the tempo value, cool.
-
I struggled with these confusingly named/labeled callbacks too…
I think the default g_nKnobAccelerationDelta is 60 (milliseconds) which is borderline too fast to hit repeated keypresses… unless you’re really trying hard.
60 ms is good for mousewheel-rotary and encoder-knob clicks… but for key presses or dx button presses, I recommend 200 to 300 ms.
-
Re: No more IncBy5 or DecBy5 callbacks?
I wish they were incby10 decby10 instead, by 5 is still too slow for my taste, and even better were made editable.