Vipergear ICP and rotary axis for QNH
I hace a Vipergear ICP. And I want to map the BRT rotary switch to control altimeter setting. Unfortunately the axis is to sensitive. So for each “notch” on the actual rotary, the altimeter setting jumps by 5. Any idea how to set the axis to be increment with 1 pr physical “notch”?
I tried the ingame saturation with no effect.
I have mapped to a rotary on my CM2 throttle like this:
It is not obvious why you should map to the 5 degree increments but that works, together with this setting in the config:
set g_nKnobAccelerationDelta 250
The setting will allow BMS to figure out if you are slowly dialing the rotary or spinning it fast. The former will then give you 1 degree increments.
Note that 250 may not work for you. It is dependent on the hardware firing rate, so try lower or higher values to see what works.
I will give it a go. thanks
I’m not quite sure I’m doing this right.
I added the line
set g_nKnobAccelerationDelta 250
at the end of my
// Config.exe Settings //
I did not chance anything in my keys.
Unfortunately it didn’t have ANY effect what so ever.
So I’m guessing I’m doing something wrong. Could you walk me through it?
The docs describe this setting in the Technical manual, p. 3-27. They suggest setting it to zero for 1-degree increments always (when bound to the 1-degree setting). That may workfor QNH. But I use rotaries for CRS as well, so I need to be able to spin faster. Hence my choice of 250.
If you are using the Alternative Launcher, you could show the Mapping screen for those bindings like mine above. Just take a screenshot and paste it in here.
Also, are you mapping the rotary to the 5 degree increments/decrements binding only?
In the BMS UI, under Setup-Controllers, this is what I see when I turn my rotary one notch:
And same for decrement. You might check that you are seeing the same thing
I think this might the reason it doesn’t work.
Mine is an axis, and as far as I understand what yours is, is a DX key to emulate a button press.
Or am I mistaken?
My rotary isn’t registrering when I try to map it to the Increase/decrease function
This post is deleted!
@BOCOWA No, you are right, my rotary fires off a DX-keypress for each notch.
That is probably what causes your issue. Can you somehow “convert” the rotation into DX-keypresses (axis-to-button) through software ?
On the other hand, it should work with using analog control. Reading through the pages in the user manual around 3-47, there is some warning about only use one physical axis per in-game axis, so you could check if you by any chance have a conflict of axis.
Thanks anyway. I’ll browse the manual, and leave this post open, And see what turns up.
I’m guessing there is a way to change this.
I ran into this same issue when I made my own HSI knobs with a pair of rotary encoders. Ended up adding custom coding to my hardware to detect the rotary spin speed and adjust output accordingly - slow movement is 1 degree per detent, faster is 18 per, faster still is 30 per detent.
Since you may not be able to alter the coding or firmware of your device, you may be able to achieve similar results with some third party tools, but it may require a fair bit of tinkering to get it to work. I’d suggest checking out AutoHotKey and perhaps vJoy and Universal Joystick Remapper (UJR) as well.
You may be able to bind the axis to such utility programs which themselves could apply a custom script and output to a second virtual joystick bound in BMS. This really goes off the deep end fast, and don’t quote me on whether this will net a solution, but this is where I would start looking myself.
Seems a bit advanced. But I’ll poor me a big coup of coffee and give it a go.
Unfortunately this IMMIDIATELY started fucking with my BMS. so this is not an option for me. I’ll just use the keybinds for now.
I was thinking that if your BRT control on the ICP is an axis, it will in some sense take on values between 0 and 100 and back. When it reaches 100, you can only go backwards. While the QNH dial is a rotary that can be rotated infinitely many times in both directions. Maybe those two constructs are just incompatible
Right now I have placed it on the backburner. It is not worth screwing with all my other settings to control QNH on my rotary