Released: Multi-Throttle Support for IL-2

[MikkOwl]

Originally Posted by Qpassa

I have done a video. It looks like a crap but well I wanted to record how it works
Thanks againt for your work MikkOwl

I used this config

Haha, awesome video Qpassa. I'm sure the sight of the G940 having dual throttles working will get the blood going for people who love having more than one engine. I'm happy you got it working. Did you try the toe brakes? The individual engine buttons?

Originally Posted by Stanger

Is my setup wrong? When I push right toe brake carefully without rudder the rudder moves fully right. Maybe the toe brake is inputting both axis?

Did you read the instructions? The Toe brakes will manipulate the rudder if pressed, because IL-2 determines which wheel NOT to brake by the position of the rudder. This doesn't affect anything on the ground (unless you are taking off and try to use wheel brakes for some reason) - just don't use toe brakes when in the air

[TheGrunch]

Originally Posted by MikkOwl

just don't use toe brakes when in the air

Could I suggest disabling the toe brakes while the gear is up.

[MikkOwl]

Originally Posted by TheGrunch

Could I suggest disabling the toe brakes while the gear is up.

That would be perfect - but there's no way of knowing when the gears are up or not Can make assumptions, but then the user would have to tell the program if we are starting in the air (gear already up) or on the ground.

I'm deaing with some people who downloaded and tried my program, launching the wrong files without checking any instructions, and then their computer acts strange and they blame me. Moreover, they also suggest that I'm trying to install malware/viruses/etc and that they are on to me. Ooookay there...

EDIT: Either way, I'm going to try and work out something for the toe pedal issues if anyone seems to have 'stutter' in their real world feet and having an angle that doesn't make the heels the pressure point. Maybe merge it with the tail-wheel lock function, because as far as I know, the tail wheel is ALWAYS unlocked even when starting in the air. But then one would pretty much need a reset button for this as well.

Maybe something else. I don't know what. I could scan the throttle axis and make it only manipulate the rudder if the throttles are at a certain setting, but I don't think that would work well either due to people using throttles in all kinds of ways when taking off, landing, and turning on the runway.

I could put in a 'deadzone' for the wheel brakes users can set up themselves maybe. That way they have to press them a bit more when using them, but less chance of inadvertent activation otherwise. I've personally never managed to accidentally press the toe brakes far enough (they have a noticable deadzone of travel before engaging to begin with).

[JG301_HaJa]

Well, there are idiots everywhere who doesn't feel the need to read a manual and thus wreaking havoc on things

[MikkOwl]

I abandoned yet another chance to fly on my favourite server to respond to people having problems, and to release the 3.2 version with the G940 reversal bug fixes. I'm rewriting the documentation and going to change other things to try to make it more 'fool proof'. I think while the documentation is very detailed and informative, it is probably too much for some people to even bother start reading.

[kimosabi]

Fool proof suits me perfect.

Thanks for all the time you spend on this, MikkOwl.

[Sokol1]

For us that use MikkOwl multi-throttle and MODs, and dont desire disable HUD to not show boring "selected/unselected engines" messages, go to folder:

\IL-2 Sturmovik-1946\Files\i18n

Open the file (with notepad):

hud_log_ru.properties

And erase these messages in right side:

"Engine: Engine1 Selected" etc.

Leave the entries in left side (EngineSelect1...)

EngineSelect1 Engine: Engine 1 Selected
EngineSelect1OFF Engine: Engine 1 Unselected
EngineSelect2 Engine: Engine 2 Selected
EngineSelect2OFF Engine: Engine 2 Unselected
EngineSelect3 Engine: Engine 3 Selected
EngineSelect3OFF Engine: Engine 3 Unselected
EngineSelect4 Engine: Engine 4 Selected
EngineSelect4OFF Engine: Engine 4 Unselected
EngineSelect5 Engine: Engine 5 Selected
EngineSelect5OFF Engine: Engine 5 Unselected
EngineSelect6 Engine: Engine 6 Selected
EngineSelect6OFF Engine: Engine 6 Unselected
EngineSelect7 Engine: Engine 7 Selected
EngineSelect7OFF Engine: Engine 7 Unselected
EngineSelect8 Engine: Engine 8 Selected
EngineSelect8OFF Engine: Engine 8 Unselected
EngineToggleAll Engine: Selection Toggled
EngineToggleLeft Engine: Left Engine(s) Selection Toggled
EngineToggleRight Engine: Right Engine(s) Selection Toggled

Now you see only % of power, ie 83%...

Sokol1

[MikkOwl]

Originally Posted by kimosabi

Fool proof suits me perfect.

Thanks for all the time you spend on this, MikkOwl.

It is becoming very tedious work now that I'm already finished with features but try to get 'user friendliness' into it, making sure people can use it. I developed a tool that scans EVERY axis on EVERY controller and detects if the user is moving them, then also figured out how to make the tool write the correct device and axis ID to the mikkonfig.ini.

I have so many extra G940 extra features only now though. Reversal bug fix, reversal bug fix AMOUNT for each throttle (and more axises too), option to use the two trims on the throttle as trims through my program as elevator/rudder trim, so that I can then process the axis data and remove the reversal bug, another option to set the range of movement of the trims in-game (they are way too sensitive if left at 100% range, impossible to trim perfectly to fly hands off).

Originally Posted by Sokol1

For us that use MikkOwl multi-throttle and MODs, and dont desire disable HUD to not show boring "selected/unselected engines" messages, go to folder:

\IL-2 Sturmovik-1946\Files\i18n

Open the file (with notepad):

hud_log_ru.properties

And erase these messages in right side:

"Engine: Engine1 Selected" etc.

Leave the entries in left side (EngineSelect1...)



Now you see only % of power, ie 83%...

Sokol1

Sokol, that is GREAT stuff. For the same reason and more, I fly without hudlog except when testing for development reasons. Maybe with tweaks like this I can get rid of everything unecessary and just leave some basic things.