Increase /Decrease keys for radiator - Request for 4.11.1 or 4.12

[Syrius]

4.11 has introduced a much welcome (IMO) improvement to engine management, with better modelling of engine overheat that requires more detailed adjustments of rpm, radiator, throttle and mixture. As currently implemented, radiator opening is controlled by a single key binding ("Cowl or Armor Flaps" in the controls screen) that keeps increasing radiator setting by 2 notches up to 'Open' and then cycles over to 'Closed' and so on. Because we now need to adjust radiator more often and more precisely, it would be helpful to have two incremental keys available for radiator status: 'increase' and 'decrease', similar to what is available for prop pitch, mixture and throttle. 'Increase radiator opening', for instance, would add a notch to the current setting and would stop at the open setting without cycling over; 'decrease' would work the other way round and stop at closed setting. This would help operating the radiator more quickly and predictably, without risking that one extra keypress will close the radiator when we want to set it open.

I'm aware that radiator can be assigned to a joystick axis, but I simply don't have any additional axes available after assigning the ones on my HOTAS throttle to trim controls and prop pitch, and I'm guessing this will also happen to most users. Would it be possible to add those incremental key bindings for radiator in 4.11.1 or 4.12?

Thanks Team Daidalos for all your work.
Cheers,
S.

[Snake]

I think, in Hotas controls, you can assign an axis to Radiator so in this way you can obtain values from 0% to 100%.
P.S.
So you know about axis asigning. Sorry for my useless post.

[WTE_Galway]

+1 on this feature.

On many planes the radiator is the only remaining reason to leave the HUD turned on. Everything else can be worked out from cockpit view.

[Mabroc]

Yes, you can use a "wheel" control or slider in a HOTAS setup to get full control of the radiator, it was just recently implemented on the 4.10 patch. Before that I was using the single key method....and yes, is really annoying

[Blackjack]

I myself use an axis , but I understand the need for increase decrease via key , maybe support controls like the prop pitch , so for every 10% step 0-100% AND increase / deacrese keys?

At least that would make the control scheme more consistent


-my humble 2 € cent

[Artist]

I use Autohotkey for all key-mappings and I solved that for myself in the following way:

In IL-2 I mapped the 'r' to the radiator, so pressing 'r' repeatedly will cycle radiator through 0, 2, 4, 6, 8, 0...

In Autohotkey I defined the following two functions:

MapCommand_RadiatorOpen:
    Send r
    return
MapCommand_RadiatorClose:
    Send rrrrr
    return

and map two keys or buttons to them respectively:

Hotkey, %iIdSelfMade1%Joy32, MapCommand_RadiatorOpen, On
Hotkey, %iIdSelfMade1%Joy17, MapCommand_RadiatorClose, On

Now one key/botton will open the radiator by one step and the other will close the radiator by one step.

Not perfect, but useful.

Artist

[Luno13]

Originally Posted by WTE_Galway

+1 on this feature.

On many planes the radiator is the only remaining reason to leave the HUD turned on. Everything else can be worked out from cockpit view.

Don't forget bombsights, radio frequencies, repeater compass settings, German electric fuses, and throttle control etc. for those using the mouse-wheel

(Once again, I go off on the request for a customizable HUD).

[EAF331 Starfire]

Originally Posted by Snake

I think, in Hotas controls, you can assign an axis to Radiator so in this way you can obtain values from 0% to 100%.
P.S.
So you know about axis asigning. Sorry for my useless post.

The main problem is that we only have 8 axis available in DirectX.

The Joystick takes 2.
My throttle are dual, so it takes another 2.
My Pedal takes 1.
My pedal breakes could use 2 if I had axes in surplus.
Pitch takes 1 for each engine (I got dual throttle) =2
So 2 for each radiator would be nice.

I have written a request at Microsofts developer forum but never got an answer *sigh*

[Pfeil]

As far as I know, the DirectX limit is per device. And IL2 already supports multiple(4 IIRC) controllers.

If this is correct, it shouldn't be a problem unless you have single controller with more than 8 axis.

[Artist]

Starfire,

Originally Posted by EAF331 Starfire

The main problem is that we only have 8 axis available in DirectX.

Pfeil is correct:

Originally Posted by Pfeil

As far as I know, the DirectX limit is per device. And IL2 already supports multiple(4 IIRC) controllers.

- 32 Buttons and 8 Axes per device in DirectX
- IL-2 recognizes 4, but only the first 4 devices

For the buttons of further devices use Autohotkey, for the axes use my YaDeLi

Artist