Released: Multi-Throttle Support for IL-2

[MikkOwl]

Whatever it was (or wasn't) it appears to be gone and un-replicatable so who the heck knows.

That it moves in 1 and 2% increments up and down seems to be something about the math that IL-2 uses to read controls. One needs devices with massive amounts of resolution (if one changes sensitivity one can see that it moves in 1% consistently, on devices with already high resolution, but not otherwise). I suppose that the different numbers you see on the way back could be either the strange IL-2 math or that the reversal bug fix is slightly too much or too little, so you might be able to get it completely consistant with some of that tweaking.

When tuning the amounts originally myself when seeing if it could be done or not, I used the AutoHotKey (the programming language I made this stuff in) debug features where I could see the exact indicated positions of the axes, and then I would check how much one 'normal' step was, compared to how much the fix was 'off', then adjusting over and over until they matched almost exactly. But each throttle was a bit different, and other throttles can be too. Unfortunately for you there's no way to see the numbers straight, all you have to go on is the in game %, which could be unreliable.

Either way, changing that value by some fraction cannot be responsible. Even if set to crazy amounts it would not influence the other throttle in any way.

[Ghost33]

Thanks for the response and help provided. That is what I have been doing. Load up IL2 turn on your program and test, close your program, change the .ini and reload your program and test again. As far as I can tell 2% or the occasional 3% jump is the best I can get and quite frankly good enough for me and much better than stock IL2. Haven't had that odd Left Right throttle bug anymore either.

When you said you used AHK's Debug did you mean that JoyID identifier you provided with Joy1-4? I fired it up to look closer and I do get a full range of every number 0-100.

Ghost33

[MikkOwl]

I did not mean those, the JoyID thing does not even show decimals. It's just debug screens one can access if running the uncompiled "AutoHotKey" code with AutoHotKey installed, and it shows all the variables, their values etc. With that I could see that my left throttle would move 0.723 (out of 0-100) when moving forward as little as possible. When tuning the reversal bug amount I could see if, when reversing, it also moved 0.723 (it did not usually, it could be way off until I dialed it in closer and closer. But when pretty close, it might move 0,6 or 0,9 instead and there'd be no real percievable difference in IL-2. The amount in the .ini file is that amount x2 by the way, since it bugs in both directions).

And yep, full range in 1% increments with the JoyID program, and the accuracy is even higher than that (around 0.7 increments as mentioned above). In IL-2 it goes from 0% to 120% (122 steps) but the throttle has more steps than that available (about 140-150) yet IL-2 does not seem to read it properly, and similar with other more accurate devices so, who knows why. Something IL-2 related.

[Sokol1]

MikkOwl,

Is possible a version with "separated_engine_buttons" that support toggle switch, say: switch up, engine ON, switch down engine OFF.

[seperate_engine_buttons]
TOGGLE_ENGINE_1_KEY=1joy23
TOGGLE_ENGINE_2_KEY=1joy24
TOGGLE_ENGINE_3_KEY=no
TOGGLE_ENGINE_4_KEY=no
FEATHER_PROP_1_KEY=no
FEATHER_PROP_2_KEY=no
FEATHER_PROP_3_KEY=no
FEATHER_PROP_4_KEY=no

Cause:





Sokol1

[MikkOwl]

Originally Posted by Sokol1

MikkOwl,

Is possible a version with "separated_engine_buttons" that support toggle switch, say: switch up, engine ON, switch down engine OFF.

[seperate_engine_buttons]
TOGGLE_ENGINE_1_KEY=1joy23
TOGGLE_ENGINE_2_KEY=1joy24
TOGGLE_ENGINE_3_KEY=no
TOGGLE_ENGINE_4_KEY=no
FEATHER_PROP_1_KEY=no
FEATHER_PROP_2_KEY=no
FEATHER_PROP_3_KEY=no
FEATHER_PROP_4_KEY=no

Cause:





Sokol1

It is absolutely possible, in fact that is what I wrote for myself and used for a while (before releasing version 3.1). I will put this into version 3.3.

By the way, very nice switches you have there. I always wanted metal proper switches like that.

The engine on/off as seperate buttons work like this (up/down, choose yourself):

Switch up = Engine Start: selects the engine and presses 'toggle engine' function.

Switch down = Engine Stop: selects the engine and moves magnetos all the way to "off" and then up to "1+2" again. This shuts off the engine no matter what it is doing.

Note: when people use buttons, if it was only like this, the 'Engine Start' button would also turn off an engine that is running. To prevent this, the engine start button can only be pressed once - if the engine then does not start (engine restart in air etc), one must press the "Engine Stop" once, and then try the "Engine Start" again. This is not a problem for people like Sokol with two state switches, as it is not possible to press the switch twice - it moves between two states only - to press a switch again the switch must be moved to the 'off'.

This also means the program must be told if we spawn in the air (engine already on) or on the ground (engine off). Unless someone thinks of a better solution to avoid the 'engine start' shutting the engine off if pressed when engine is already running...

Hmm. Maybe I will leave it simple and allow the 'engine start' to also shut the engine off if pressed again. Switch people have no problems with this, and not many people without switches would want 3 buttons for each engine anyway to justify implementing a 'air/ground' extra button and the extra programming and documentation.