Originally posted by Duckwing6
well most engines i know in RL will pretty much instantly startp again if you switch the ignition off and back on when windmilling ... you'd prolly get some nasty exhaust flames but what the heck... but who in his right mind would switch off an engine in flight unless it's required ?
From Shaw's "Fighter Combat".
"Make no movement gently, but be as violent as possible. Pull back on the stick and apply left rudder at the same time. It might rip the wings out of your plane, but if you're a goner anyway, what's the difference".
When it comes to survival you do whatever can save your life. I think that I read about soviet pilots switched engines off during spain war, but could not find it in my books. I am sure it happened during war, though was not any common practice.
Now to this thread and its questions:
My vote is for a more realistic engine behaviour as a whole, but not as a top priority, and many things shall be taken into consideration before any change.
Really, aks yourself, how often you meet such behaviour (engine switching off in combat) in AH, and how much you think it affects your AH expirience. Also, good question is how much time it will take to model a correct engine behaviour in case of switch off, for each engine and each situation (how hot was engine, how long it stayed off, what was plane speed etc.). Then think how many other things which are not implemented yet requires work, or more gamey now (for examply bailing, it is extrememly unrealistic, try to bail at 400 mph in a real fight), and ask yourself if you really want it to be fixed right now and right here.
I do not even say that in AH you can switch engine off by accident by pressing one button instead of other. Are you sure your solution in this case is better than the problem itself? We have such examples in AH, when fix was a bigger pain, than problem itself. For examply UDP/TCP switch. I saw not a single invisible plane, but UDP switch kickes me out of AH every 5th sortie.