Kanttorin Metal Throttle and trimming WWI planes

[hsthhsth]

Brief description:
Trimming the S.E.5a

 

Detailed description, conditions:
The S.E.5a so far is the only WWI plane that has an elevator trim wheel.
The response to the keyboard keys (RCTRL + cursor UP/DOWN) works good. The trim wheel is very responsive.

 

But not to the Kanttorin Metal Throttle console I use. 
On this console I have a digital rotary encoder axis (buttons 99/100 & 107/108) that I have mapped with Joystick Gremlin.

I can see that it tries to move the wheel in the S.E.5a but somehow can't do it.

 

The same axis works perfectly in any WWII plane like the IL-2 or Spitfire but does not work for the S.E.5a.

 

Additional assets (videos, screenshots, logs):
NA

 

Your PC config data (OS, drivers, specific software):
Windows 10
Joystick Gremlin 13.3

[-DED-Rapidus]

@hsthhsth, a digital rotary encoder axis do not work in il2.

[hsthhsth]

@DED-Rapidus,

 

The axis is coded in Joystick Gremlin that acts as an intermediate. JG submits the key commands associated with the axis to IL-2.

And, as stated before, it works like this in IL-2 for all WWII planes and always has.

It's only the S.E.5a that doesn't work.

[Charon]

If you're already using JG, you might try my JG plugin to map the encoder to an axis. You'll likely need to edit the appropriate file in the inputs folder to bind it in-game.

[hsthhsth]

@Charon,

 

thank you for your assistance. Can you explain what difference your plugin will make? What will be difference between the S.E.5a and all other planes? Because I have no problem with the same axis & JG combination on all other planes?

[Charon]

I'm away from my gaming computer at the moment, and I don't fly the SE.5 (or any of the WWI planes) normally. So I don't know why that one specifically would be a problem. I can check this weekend.

 

Encoders tend to cause problems in Il-2 because they send a sequence of rapid button presses. But when you bind a pair of buttons to an axis, the game expects you to hold those buttons to change the value. The plugin above works by translating each button press, no matter how long it's held, into a specific, configurable step along a virtual axis. The game then only sees the axis.

 

OTOH, if it works for you in other planes, maybe it's not worth messing with this.