[mikkowl]

Hello mikkowl,

many thanks for your work on this fine programm. But i have a little problem and hope you can help me.

I am using the Saitek Yoke, 2 Saitek quadrants, an Saitek pcdash and at least the Saitek pedals.

I used the joystickidentfier and these tools figured out:


Pedals are #2
Quarandt is #3

the quadrant for the throttles, typed all into the ini-file, but i the game always and only the pedals

were found, and i can throttle up the engines with the pedals like in a car. :???:


Every attempt to change the ini-file has no effect on it. What did i wrong?

I hope you can help, me

Saruman

You mean that using pedals as throttle is not realistic?! I am just joking.

You don't need to edit the .ini file yourself at all. That was in the previous versions. Now, just go into the "SETUP" then "Non-G940" folder and run "CONFIGURE THROTTLE 1.EXE" and "CONFIGURE THROTTLE 2.EXE" and follow the instructions. The program will write it into the .ini file automatically. You can do this for up to 4 throttles and the 2 toe brakes, if your rudder pedals have them.

And if you don't have the SETUP folder, go to the first post in this topic and download version 3.2. Let me know how it works out.

[Logan/we the few]

Your the man!...3.2 works great. This is a nice mod and a must have for us multi engine flyers until 410 comes out with the support for it.
Thanks for all your hard work on this.

[walter_solito]

Hi mate!!!

As I wrote before this is a great mod and an epic revolution in IL2 HID management!!!

I have a little trouble in correctly configuring the program!!

I installed version 3.2 directly without any previous version!

My usb device configuration is:

HID1 Saitek Pedals
HID2 Saitek pro flight joke sistem (with the satndard throttle quadrant)
HID3 Saitek pro flight throttle quadrant

This is how I installed your mods after extract it in a temp folder:

1) I put the mod folder into the Il2 main root: C\IL2\Multi-Throttle v3.2

2) I create a desktop link at the C\IL2\multithrottle v3.2\Multi-Throttle v3.2 for IL-2 file

3) I create a desktop link at the C\IL2\multithrottle v3.2\Multi-Throttle v3.2 for IL-2\SETUP\Non g-940 folder

4) configurate the device:

[control_devices]

THROTTLE_1_AXIS=2joyz
THROTTLE_2_AXIS=3joyx
THROTTLE_3_AXIS=no
THROTTLE_4_AXIS=no
WHEEL_BRAKE_LEFT_AXIS=1joyx
WHEEL_BRAKE_RIGHT_AXIS=1joyy


[controller_options]

SENSITIVITY_SAME_AXIS=0
; Filter for the last moved throttle, in case it moves itself slightly when not touched. In percent %.

SENSITIVITY_DIFFERENT_AXIS=0
; Filter for the rest of the throttles, in case they move themselves in-game slightly when not touched. In percent %.

INVERT_THROTTLE_AXIS_1=no
INVERT_THROTTLE_AXIS_2=no
INVERT_THROTTLE_AXIS_3=no
INVERT_THROTTLE_AXIS_4=no
INVERT_BOTH_WHEEL_BRAKE_AXIS=no
ENABLE_TOE_BRAKES=yes

[seperate_engine_buttons]

TOGGLE_ENGINE_1_KEY=no
TOGGLE_ENGINE_2_KEY=no
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

5) add at the conf.ini

[DeviceLink]
port=3333

6) Runned IL-2

7) Runned Multi-Throttle v3.2 for IL-2.exe clicking on ok because I have made the setup and IL2 is running

8) the blak windows appear and tell me:

privato-31c16cf [192.168.0.3] 3333 (?) open

9) start a QMB with the A20

mine controls configuration for Hotas are those:

http://s614.photobucket.com/albums/tt22 ... -41-01.jpg

when I'm in the cockpit if:

-I move the setted throttle the engine 1 or 2 are regular in control;
-If I move the pitch control this isn't regular because I can change only the right engine pitch and the left engine go in the same position of the right only moving one throttle so I haven't control of pitch left engine
-If I move the flap slider control they work regular
-I don't understand how configurate the feather propeller

I hope to have give you all the data you need for help me!!!

I'll wait for your reply mate!!!

cheers

walter

[mikkowl]

Saluti Walter

Your English is a bit difficult to understand. But I will try to help

THROTTLE_1_AXIS=2joyz
THROTTLE_2_AXIS=3joyx

Do you understand how to assign your throttles and wheel brakes? The "non-g940" folder. Throttle 1 and throttle 2, etc.

I ask because: your mikkonfig.ini file shows that your throttle 1 and throttle 2 are not on the same control device. You set Throttle 1 to the Saitek Yoke (axis Z) and Throttle 2 is the Saitek Quadrant (Axis X, the left, first, lever). Is this really how you wanted?

mine controls configuration for Hotas are those:

http://s614.photobucket.com/albums/tt22 ... -41-01.jpg

You must clear (empty, unassign) the POWER and the BRAKE. Because we use multi-throttle and DeviceLink instead of the HOTAS of IL-2 to control brakes and power. If they are not cleared, then the wrong engine can move (and more evil things).

Also, you must make sure that your throttle 1, 2 and wheel brakes are not assigned to anything in IL-2 HOTAS either. If they are, then one axis can do several things at the same time. For example it can control throttle + flaps at the same time Not good.

-If I move the pitch control this isn't regular because I can change only the right engine pitch and the left engine go in the same position of the right only moving one throttle so I haven't control of pitch left engine

Multi-throttle does not have support for individual prop. pitch axis. So this is how crazy the Il-2 prop pitch works. It is meant to work that (bad) way. In IL-2, if we change something on engine 1, then select engine 2, then engine 2 will copy the settings from engine 1. It is like this always: select another engine, and it will copy the old engine settings. Multi-throttle can avoid it only with the throttle settings.

-I don't understand how configurate the feather propeller

You have to edit the mikkonfig.ini file.

TOGGLE_ENGINE_1_KEY=no
TOGGLE_ENGINE_2_KEY=no
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

Change "no" for the feather prop 1 and 2 into a button on a controller, or a keyboard key. To assign one of your controller buttons, you write for example:

3joy1

3 means "device 3" (the saitek quadrant for you). "joy" means it is a controller device. "1" means button 1. On the saitek quadrant (which I also have), button 1 and 2 is the left switch. 3 and 4 is the middle switch. 5 and 6 is the right switch.

Maybe an easier way for you is this:

1. instead of "joy" bla bla, you can try writing "^1" and "^2", like this:

FEATHER_PROP_1_KEY=^1
FEATHER_PROP_2_KEY=^2

This means "CTRL 1" and "CTRL 2" on your keyboard.

2. Then, you can just assign (with the saitek profiler) CTRL 1 and 2 to any button of the Yoke or the Quadrant. You can use any other keys, does not have to be 1 and 2. Instead of "^" (Control) you can use "!" (Alt) or "+" (shift).

Warning: you will not be able to use the keys for anything else when running multi-throttle. For example, if you just write "1", you will not be able to use "1" for anything else. Not even for typing.

I hope this helps

[cerkaire]

Hello Mikk
I have one problem with my configuration.

I use R1 for my prop-pitch and it was disable when I use Multi-throttle. :-?

Help me please

Ps: R2 is for my flaps and it work...

[walter_solito]

Dear Mikkowl!

Thanks for the reply!!!

I apoogize for my complicate language!

Now I have understand what I must do for make your mod to work: delete the HOTAS control on IL2 and assign controls to the feather for each propeller.

What I haven't yet undestand is:

- If I delete the control on IL2 other than the throttle I can have the propeller pitch control too or not?

cheers

walter

[cerkaire]

Sorry, I don't understand, it reappear...... :o
All works

[mikkowl]

Dear Mikkowl!
Thanks for the reply!!! I apoogize for my complicate language!

Now I have understand what I must do for make your mod to work: delete the HOTAS control on IL2 and assign controls to the feather for each propeller.

What I haven't yet undestand is: If I delete the control on IL2 other than the throttle I can have the propeller pitch control too or not?

To make it clear: you clear the following in the IL-2 HOTAS section: POWER and BRAKES. You also clear the controller axis you use for Multi-Throttle in the IL-2 HOTAS section, so they are only used in Multi-throttle, not in IL-2 HOTAS.

To use prop pitch, you assign it like normal in IL-2 HOTAS section. You can use it, it works. The strange behaviour is: It only affects prop pitch of the engines you last moved. For example: You move engine 1 to 50% power, then engine 2 to 50% power. Then, if you move prop pitch, it will only change engine 2 prop pitch. The reason: It was the last one to be moved (so it is the last one selected). To make prop pitch also affect engine 1, it is simple: just move engine 1 throttle a little bit.

Cordiali saluti dalla Svezia. Tra l'altro, ho avuto un gatto amato quando ero un bambino di 21 anni.

[walter_solito]

[quote="walter_solito"]Dear Mikkowl!
Thanks for the reply!!! I apoogize for my complicate language!

Now I have understand what I must do for make your mod to work: delete the HOTAS control on IL2 and assign controls to the feather for each propeller.

What I haven't yet undestand is: If I delete the control on IL2 other than the throttle I can have the propeller pitch control too or not?

To make it clear: you clear the following in the IL-2 HOTAS section: POWER and BRAKES. You also clear the controller axis you use for Multi-Throttle in the IL-2 HOTAS section, so they are only used in Multi-throttle, not in IL-2 HOTAS.

To use prop pitch, you assign it like normal in IL-2 HOTAS section. You can use it, it works. The strange behaviour is: It only affects prop pitch of the engines you last moved. For example: You move engine 1 to 50% power, then engine 2 to 50% power. Then, if you move prop pitch, it will only change engine 2 prop pitch. The reason: It was the last one to be moved (so it is the last one selected). To make prop pitch also affect engine 1, it is simple: just move engine 1 throttle a little bit.

Cordiali saluti dalla Svezia. Tra l'altro, ho avuto un gatto amato quando ero un bambino di 21 anni.

[mikkowl]

Now I understand how the prop pitch work!!
I had it working but I haven't undestand it before your reply!!!

Fuel mix, radiator and magneto work the same way. Be careful. If you set fuel mix or magneto to 0% on one engine, then you do anything on the other (like move the throttle, or just select the engine) it will set fuel mix / magneto to 0 on that engine too, and it will stop.

This is why it is so difficult to have individual prop pitch, fuel mix etc in multi-throttle. I tried but it did not work properly.

[mikkowl]

I've managed to read the responses from DeviceLink with my program now (complicaaaated). I've also managed to control the G940 led lights using info from IL-2. All this I'm going to put out in the next version (possibly labeled 4.0).

What can be read is mostly relevant to G940 users, as it can be used to control the 8 throttle button background lighting. But they can be useful for others too, completely safe to use online as it's not a mod.

If anyone can think of any good use relating to these things available, then post it. Who knows, maybe it's a brilliant idea.

The following systems are allowed to be read (which is relevant to any utility like this one) in multiplayer.

• Trim positions. This is useful for G940 owners. I intend to make the G940 buttons be usable as indicators for if a trim is centered or not, just like many real WW2 era aircraft (Try the PE-3 for example to see)). Should be a welcome addition as it is impossible to see or feel that a trim wheel is centered on the G940. And it is realistic too.
  
  Landing Gear. Not a big deal, because all aircraft pretty much have clearly marked gear indicators on the dashboard that work. But hey, why not. This will also come in handy with the toe brakes - if the gears are up, the plane must be airborne and the toe brake rudder manipulation can be completely disabled. In combination with the tail wheel below, the toe brake system will only be manipulating the rudder when the tail is unlocked and the gears are down.
  
  Tail wheel. This one is great, because I hate seeing that 'tail wheel locked/unlocked' on the HUD, and I removed it ages ago. So much more realistic this way.
  
  Arrestor hook. Useful - can get rid of hook helmet mounted display message, and most aircraft don't have any indicator nor sound effect at all regarding the arrestor hook.
  
  Chocks. Not useful. If the plane does not move, it is obvious the chocks must be on.
  
  Flaps position (unknown at this point if it is the position of your axis or the actual flaps. The two can be significantly different so I hope the latter). Could be used for adding that chiming repeating horn in the Bf 110 if flaps are down but gears are not (yes, that's how it works). I know the Bf 109 is like that in the modified versions of IL-2 I use but I don't know about the stock versions. As it's not a mod to do it this way, it is good. I could make flaps that work just like the real Bf 110: two pull switches. Pull one out, and the flaps start moving in that direction until reaching the max position. To have the flaps in a position other than completely up or down, one has to push in the switch a bit, which will make them stop in their tracks. The flap position indicator of the Bf 110 doesn't exist in IL-2's cockpit, but I can make the G940, which has lights, show different colors depending on the position (To understand how this would work, have a go in the Ju 88 and look at your lower left panel while manipulating the flaps. Three lights, same color as G940 leds).
  
  War Emergency Power (WEP). This one is very cool because practically NO planes at all have indicators for WEP (the ones that do are pretty much all american fighters with auto-wep that lights up if throttle is beyond a certain position). I already added nice support for this for the G940 (and could make it useful for non G940 users as well somehow, sound effect maybe): it currently blinks a button on my throttle red for as long as WEP is activated. I love it! It is impossible not to notice and an urgent reminder to turn it the hell off when you don't absolutely need it anymore. Best of all, being able to ditch that ugly, awful, immersion breaking "NAAAAWZ ENGAGED!!!!!!" constantly glowing in the mid right part of the screen.
  
  Magneto position. This one is truly useless for three big reasons: Have to select the engine in question, to even be able to send a query to IL-2 (it works that way) so IL-2 can send back a reply with the status of that engine's Magnetos. This is a big problem because selecting an engine makes it take on every single setting of the previous engine selected, requiring an update of all it's systems to be re-done. Secondly, messing with the magnetos is dangerous because if it is set to none, and then another engine is selected, it will stop that other engine too (as it's magnetos are set to off as well). Thirdly, magnetos serve no useful purpose even if they worked well.
  
  Level Stabilizer. A minor thing, practically useless. Because anyone likely to use level stabilizer is going to heavly be manipulating the bomb sight, which has no proper graphical interface or interaction other than keypresses and a helmet mounted display projection showing the current settings of the bomb sight. To be able to eliminate a single HUD message in this context is akin to a water drop in the ocean.
  
  Supercharger stage. Maybe not entirely useless. I don't fly any aircraft that have superchargers, but the times I have tried (without HUDLOG) it would have been nice to have some kind of sound effect at the very least to tell me what mode it was just put into, and if it can't move into a higher or lower stage than current.
  
  Propeller feathered or not. Nice to have, as there's no indicators for that in terms of graphical switches or markers in cockpits. Only some aircraft let you see the blade angle being a certain way. Unfortunately it is very difficult to check because the engine being checked must actually be selected in the process, bringing the problems mentioned for magnetos mentioned earlier. Sooo.. have to think of something. Glad to be rid of the Helmet Mounted Display message saying "Engine 1: un-feathered" at least. Can display it in color on the G940.
  
  Air Brake. Not the most useful thing around, few aircraft have air brakes, and it is quite obvious if the air brake is engaged even without any sound effects or instruments. Still, why not, for the man with a bad Junkers addiction. Technically I can manipulate trims or even controls when air brake is deployed, if there's something unrealistic going on in how the game treats air brakes in some aircraft.
  
  Gun pod on/off. This one must be 100% useless. Is there any time, ever, that the gun pod toggle is useful for anything? It doesn't even work most of the time.
  
  Wing fold. Useless.
  
  Canopy (open or not). Mostly useless. Although I could play a loud wind noise effect if it is open and the plane is (probably) airborne. Not that people fly around with it open or would want a loud wind noise effect anyway.
  
  Prop. Pitch. Could possibly be used in some way for multi-prop pitch use before the official 4.10 patch, but I doubt it'll be worth trying. Then it would be checking if the plane prop pitch was in the same position as the controller lever for that engine, and forcing another update if not (the biggest problem for dual prop pitch is making them not move around constantly to match the other engine due to the engine selection problem inherent in IL-2).
  
  Throttle. Useless.
  
  Time of day. Useless.
  
  Plane type. Could be relevant to adjusting some functions to if the plane has them or not, but I don't really see how. I don't think it tells what kind of loadout the plane has either, making it even less useful.
  
  Number of engines. Useless.

________

The list is severely lacking. One cannot even check if an engine is even turned on or not or if the aircraft is airborne or standing still! Can't see anything about fuel mixture, radiators, temperatures, fuel drop tank, ammo counters, dropped bombs, low fuel warning. Can't even check if the plane is airborne. Only check if gears are up and assume it must be flying then. For this reason I cannot even make the G940 button lights show if the engine is turned on or off. ♦♦♦♦

[Saruman]

At first sorry mikkowl, today i saw your answer.

I checked it and........ it works hock: :lol: 8) !

Yes, gentlemen it very easy, but 2 points you have to know:

1. copy the ini-file, after its configurated, out of the setup-foulder into the main IL2-game folder,

and 2. start the multi-throttle.exe after il-2 ! That

[mikkowl]

Version 4.0 change-log

Bug fixes:

- Fixed a bug where the brakes would not release fully when having used the toe brakes.
- Fixed a bug where if both toe brakes were pressed completely the brakes would set to zero.

Changes & Tweaks & New stuff:

- Can now close all windows it creates when exiting (ALT-E).
- Can now detect if user is in an aircraft and at the controls. Does not try to send any commands if escaped, not in control of the aircraft's flight controls, bailed out, main menu (being alt-tabbed does not count).
- Toe brakes no longer manipulate the rudder (for differential braking function) if either the tail-wheel is locked or the landing gear is retracted (no more accidents for some of you and landings should be much be more stable).
- Added ability to detecting button presses for setting up individual engine key controls (start & feather prop).
- Added support for trims (in order to make new trim tweaking possible). Assign any axis to any trim.
- Added ability to limit the range of trims for a much smoother, accurate, realistic and relaxed trim experience (all IL-2 aircraft have an enormous trim range in all directions, but our controllers do not = hypersensitive trimming).
- Added feature to off-set the trims to either side (most aircraft only need to trim the rudder/ailerons in one direction, meaning the other 50% is wasted movement range on our controllers and making trimming twitchier).
- Replaced the dozens of individual config executables with a single, graphical user interface setup program (phew.......). The Setup folder is also gone. G940_tweaks.ini merged into mikkonfig.ini and moved to DATA folder.
- Ability to assign any of the G940 trim wheels to any trims in-game instead of just R1 and R2 to Rudder-Elevator. With reversal bug removal extended to these other trims.
- Radiator support is back (the code is revised but no full setup program support - edit the .ini file if you really want to use it).
- Dual Prop. pitch support.
- Support for G940 throttle button LEDs for IL-2! (Am I the man or what? Logitech owes me a paycheck and you G940 users especially owe me a donation ).
- Bonus: As information from devicelink and IL-2 is limited, wrote program functions to 'guesstimate' certain functions in order to provide more realistic LED behaviour.
- Bonus: One of the extra functions is a flap position indicator light, like the one in the Ju-88 A-4.
- Bonus: Like the real world Pe-2 and Pe-3, a LED button can now light up when the rudder trim is centered. (Knowing when the important rudder trim is centered can be difficult, especially on the G940 and even more with the new trim tweak abilities. Especially important for take-off).