Quote:
Originally Posted by LesniHU
1. it is possible to do anything, but its very hard to do something useful, realistic and working correctly for all planes in game. Changes to stop exploiting the engines are in the pipeline (but nothing directly related to everheat time). BTW inline engines have water and oil temperature threshold too and both are used to determine overheat.
2. possible, not planned now. We can add them in the future if there will be demand for it. I believe that for example feather prop would have bigger priority  .
3. one axis for all engines. |
Appreciate the answer.
1. I understand the reasoning. Too big of a task to accomplish to change the modeling with limited resources. But inline engines having water temperature involved?! Are you 100% certain about this? I performed several tests with the Bf-110 G-2 and every single time - overheat message at 125 degree oil-out temperature, and 'engine normal' at 124 degrees. It seemed only that water temperature affected how fast the oil can heat up or cool down - but not the overheat mechanic itself.
2. Oh yeah, feather prop. I forgot.. I have that stuff in that Multi-throttle program I made so I didn't even think about it. I agree that would be more important if one does not use third party apps like mine.
3. One radiator for all, understood. If it has a devicelink interface (maybe it will not) then I could possibly make it work with separate radiator for each engine. But while I want it, I don't have enough controllers to control all this stuff.. I would have to plan to get another quadrant
Crap. SoW will almost force that
Quote:
Originally Posted by Avimimus
Regarding the radiator: Is there any chance that we'll get a "radiator open" and "radiator closed" keyboard commands with the next patch?
The problem with the current setup is that only a few airplanes have an animated radiator lever or engine that is visible from the cockpit.
This poses a problem for people who want to fly with the HUD log off (in the conf.ini) and "no external views". The current command is a toggle and it is impossible to tell whether the radiator is open or closed prior to pressing it.
Having two separate keyboard commands would solve this problem.
|
I have the same concerns you do in general - eliminating that crappy helmet mounted display (the so called 'hudlog') and still be able to know what my controls are set to. If they don't do that radiator thing, I think I can make it work with my multi-throttle program. I already have, in fact, but it is controlled by a controller axis, not buttons. We'll see what I can come up with if need be.