![]() |
Increase /Decrease keys for radiator - Request for 4.11.1 or 4.12
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. |
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. |
+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. |
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
|
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 |
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: Code:
MapCommand_RadiatorOpen:Code:
Hotkey, %iIdSelfMade1%Joy32, MapCommand_RadiatorOpen, OnNot perfect, but useful. Artist |
Hi Artist,
I'm using the X52Pro HOTAS, and the Saitek profile software allows quite complex programming of macros for the joystick/HOTAS buttons; I use those macros for other functions, like continuous zoom in/out and others. I also tried to use a macro for the radiator settings long time ago, but there is a particular problem with the radiator control for different planes. A few plane types, like the the late Spitfires, simply don't have manual control of radiator, the radiator is always automatic in these planes, so they are of no concern here. But most aicraft types fall in one of the following two categories: - Planes with automatic radiator setting: the radiator key (I use 'R' as well) cycles through Closed/Auto (default position at start) -> Closed -> 2 -> 4 -> 6 -> 8 -> Open -> Closed/Auto, etc. That makes 7 different positions and then repeat. - Planes with no automatic radiator setting: the radiator key cycles through Closed (default position at start) -> 2 -> 4 -> 6 -> 8 -> Open -> Closed, etc. That makes 6 different positions and then repeat. In other words, Closed/Auto is an additional position that only some planes have. One group of planes have an even number of radiator steps, the other has an odd number of steps. Some aircraft types (for instance Fw190, Yak and possibly others) go from one group to the other as they evolve throughout the years and models. As an example, the macro for 'RadiatorClose' you showed in your post, with 5 key presses of 'R', will work as intended in the FW190-A types (no Auto/Close setting), but won't work well in the FW190-D9 which does have an Auto/Close setting. Same thing happens when going from an early Yak to the Yak3P or when switching from P51 (has auto) to a Zero (no auto) in the next sortie or mission and then to a Bf109 (has auto) in the next. One macro does not rule them all! :) Of course, one could use two different macros for decreasing radiator setting in planes with/without auto radiator, but that would still make things complicated. If it is at all possible (programming-wise) for the developers to add the two incremental keys as explained in the first post, that would be a much simpler solution that would work in all cases. Cheers, S. Quote:
|
Hi Syrius,
Quote:
And "in this mean time" I use different Autohotkey-files for different planes. ;) Cheers, Artist |
I would appreciate this too as I'd love to use the throttle mousewheel on my X-52 for radiator settings.
|
The axis mapping is a great improvement but not everyone has a spare control axis.
The current problem is this ... Very few aircraft have a visual indication of radiator settings. yes, the Hurri does on the floor and in early 109s you can look at the wing and see the radiator opening and closing - but most IL2 aircraft provide no way of telling radiator position from the cockpit just by looking. Hence if you are limited to keyboard controls only for the radiator and turn HUD messages off you have no way from cockpit view to tell the current radiator position once you forget what you last set it to. |
The wish for +/- keys for radiators is acknowlegded. Personally I would find such step just logical in face of the latest radiator changings.
|
Quote:
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* |
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. |
Quote:
|
Quote:
|
Starfire,
Quote:
Quote:
- 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 |
Quote:
Are there penalties in game from flying around with rads open aside from drag, like having water and oil too cold fed into a hot engine? The reverse of overheating? I have no idea. |
Any bell or whistle that adds to realism is always welcome and applauded.
I never use intermediate radiator settings in fighters though. I am either cruising along with the radiator closed trying to save fuel while on patrol to or from a target or the front, or I have it wide open and am fighting or climbing to the altitude I want to cruise at, so the lack of radiator control never was an issue for me. Didn't some famous fighter pilot talk about how his missions were long hours of tedium interrupted by second of terror and adrenaline? It is the same for my engine.... |
Quote:
(Once again, I go off on the request for a customizable HUD). |
Quote:
Over-cooling was a common problem at altitude. Both the p47 and the p38 suffered mechanical failures related to over-cooling. I suspect it was a key factor in the p38 being withdrawn from European operations (the story about lack of cockpit heating giving the pilots cold toes is just silly). The LA5F also had over-cooling issues at one stage. Note that it is quite possible for the same aircraft to suffer overheat problems under climb at sea level and then have over-cooling issues at altitude. However I do not think over-cooling is modeled in game. One issue that actually is modeled in game is the effect on low speed handling of some radiator cowls. A good example in game is the Lagg 3 once again, which wallows about like a pregnant hippo with the rad open at slow speed. |
It may be worth mentioning that sudden reductions in power could cause shock-cooling, and cracks in the cylinders.
Also, one could destroy his engine in a heartbeat if RPMs were set too low while manifold was too high. For this reason some planes had a stopper to prevent the throttle from moving past the RPM lever. |
Quote:
Is it even possible to start a seized/damaged engine in game if it went out ? Was it historically possible that a engine gave out and could be restarted ? (Or turn of because of fire, then on again) In case of fire we have the "ethernal flame" modelling , after dropping speed it will burn 100% again even if turned off, so no point in turning it off and not going 100% power to get to safety and bail out :confused: |
It should not be possible for the engine, or rather the prop, to stop as it does ingame unless something prevents the crankshaft from turning. The prop should windmill, possibly not losing any revs either. If you still had fuel and a spark then the engine should restart if the mixture was near enough correct. Shame overcooling's not modelled, gets my vote TD if to add it. Someone will though have to make some training or info missions, for the benefit of anyone who doesn't know or understand what's going on, i.e. some poor soul who is new to IL2.
|
In twin engine aircraft its impossible to have to separate radiator settings, eg: left engide is damaged and is overheating, so, i select engine1, open full radiator( no mather if by axis or by keys) and right engine is runing ok, so i can let him with radiator closed, but as soon as i select both engines,(to throttle or prop pitch both, the radiator goes the same (in this case they open both, as was my last choice in the comand) It would be great 2 radiator axis, or one maner to keep them different if we want to. Thanks.
|
| All times are GMT. The time now is 11:51 AM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.