Released: Multi-Throttle Support for IL-2

[335th_GRSwaty]

Thank you!
I hope its useful!

[TheGrunch]

Originally Posted by 335th_GRSwaty

Thank you!
I hope you its useful!

Well, I've got a spare broken CD drive.

[Stanger]

ok I am pretty stupid, and need the Multi Throttle for dummies setup.

I saw where you add to config ini the device link. What else you do. Drag what file where. Push this exe. I have gone thru all of the readmes and I am missing this. Or which readme has the instructions to put what file where?

Thanks, and I do appreciate your hard work and patience.

Opps found the cure. First I had to open the port on router and second I start your program after I start IL2.

Thanks I got it now.

[Stanger]

Also I found out you do not have to map keys. All I did was make sure my controller id was right in config. I have no power throttle mapped in Il2 and I just start the engines as normal with in game settings and seperate engine starts up. Then my throttle will work seperate for each engine.

So I have no keys mapped in Il2 for power settings and it still works.

Thanks

[MikkOwl]

Originally Posted by Stanger

ok I am pretty stupid, and need the Multi Throttle for dummies setup.

I saw where you add to config ini the device link. What else you do. Drag what file where. Push this exe. I have gone thru all of the readmes and I am missing this. Or which readme has the instructions to put what file where?

Thanks, and I do appreciate your hard work and patience.

Opps found the cure. First I had to open the port on router and second I start your program after I start IL2.

Thanks I got it now.

In this case, you were definitely not stupid and managed to figure it out by yourself, and the fault was mine to begin with.

There is a (now) confirmed issue in how this works - if starting the throttle software first, then starting IL-2, it does not work. One must start IL-2 first, then when at the runway (presumably) alt-tab out and start the throttle software.

I will fix this issue tonight, by making the throttle software not do anything until the user clicks a hotkey, such as "ALT G", then it will launch and set up itself in the background and make things work.

[MikkOwl]

Originally Posted by Stanger

Also I found out you do not have to map keys. All I did was make sure my controller id was right in config. I have no power throttle mapped in Il2 and I just start the engines as normal with in game settings and seperate engine starts up. Then my throttle will work seperate for each engine.

So I have no keys mapped in Il2 for power settings and it still works.

Thanks

I should have explained better in the instructions for this version 3.0:

The method of using keyboard key emulation to control the engines is now gone. It is replaced with using the joystick axis directly, through a special communications link called "Device Link" supplied with IL-2. It allows programs to send instructions to IL-2 from outside IL-2, telling IL-2 what to do. In my case, I made it scan your throttle devices and then convert the information to the right format, and then (if many conditions are filled, which is very complicated to explain) send it as an update into IL-2 to change to the right engine (also through device link) and to move the power setting to a certain position.

Everything works in this way now, EXCEPT fuel mixture, if you use that, and that is only because fuel mixture cannot be changed through device link.

This is the great thing. Nearly no set up needed by the users, and much, much higher accuracy in-game, just as good as the in game throttle (If bound in game), down to every single %. You all get your keyboard keys back The only thing one must at least set up oneself, is to specify what throttle devices to assign in the mikkonfig.ini.

[Stanger]

Thanks for the quick reply. But for me as soon as I was in il2 main screen I tabbed out then start your program. Went and started a mission and it worked. So the tabbing out to desktop can be done before you start mission.

Thanks again for this great mod and your hard work.

[Ghost33]

Hey MikkOwl, I love your programing work here and I use it all the time now with my G940. I only have one suggestion or wish , Do you think that it would be possible to have a hotkey that can "arm/disarm" the toe breaks for flying? Sometimes my G940 pedals are so sensitive that the toe breaks pick up the littlest movement and send my rudder all wonky when in flight.

Other than the fact that I have to be ever cautious with my toes now, this little program is wonderful. Awesome job

[MikkOwl]

Change Log version 3.1 (current)

- Fixed an issue where software would not be accepted by IL-2 if software was started before IL-2. Now one can launch it at any time. After starting IL-2 and having entered the cockpit, one now presses to "Alt G" activate the software (a comand prompt will appear over IL-2's screen - use the mouse to click on the IL-2 window and it will resume). "ALT E" exits the software. Users updating from Version 3.0 can simply copy their old mikkonfig.ini over to the new version.
- Tidied up the files and directories. Now only the launcher, the mikkonfig.ini file and the instructions are in the main directory.

See first post in topic for details and download link.

[MikkOwl]

Originally Posted by Ghost33

Hey MikkOwl, I love your programing work here and I use it all the time now with my G940. I only have one suggestion or wish , Do you think that it would be possible to have a hotkey that can "arm/disarm" the toe breaks for flying? Sometimes my G940 pedals are so sensitive that the toe breaks pick up the littlest movement and send my rudder all wonky when in flight.

Other than the fact that I have to be ever cautious with my toes now, this little program is wonderful. Awesome job

I'll try to think of something Either a key, that can be the same as the gear up and down for example, to disable the rudder aspect of toe braking (just applying the brakes in the air does nothing, after all), or an adjustable deadzone if one inadvertedly keeps pressing the pedals.

I have never managed to accidently press them for myself though, the pedals already have a deadzone on them of maybe 3-5 cm before anything registers. In my case I sit at such an angle that my heels are mainly the ones doing the pushing of the pedals, and it requires a concious effort to 'flex' my feet forward to tip them forward. If you could in any way adjust the pedals to be further away from your feet, or angled a bit away from your feet, you may get the same results.