Bog9y Posted February 24, 2023 Posted February 24, 2023 Hi guys, the last few times I flew the Hog I had a random engine failure, not had that ever happen before. Today the failure happened 5 mins after take off , I was low level and had the throttles at full since take off. I guess it could be a birdstrike? The A-10 does not have a max time limit for max thrust, does it?
razo+r Posted February 24, 2023 Posted February 24, 2023 Do you have birds enabled in the options? Are random failures enabled in the mission? Are perhaps random failures forced enabled even if you don't have it enabled in the mission itself (check mission.lua for that)
Bog9y Posted February 24, 2023 Author Posted February 24, 2023 41 minutes ago, razo+r said: Do you have birds enabled in the options? Are random failures enabled in the mission? Are perhaps random failures forced enabled even if you don't have it enabled in the mission itself (check mission.lua for that) Yes, birds are enabled. Random failures not enabled, i think, I'd need to double check but I think they're off by default.
razo+r Posted February 24, 2023 Posted February 24, 2023 Then there's a chance that the engine failure was related to your bird setting.
ASAP Posted February 24, 2023 Posted February 24, 2023 (edited) 3 hours ago, Bog9y said: The A-10 does not have a max time limit for max thrust, does it? The only timer is the fuel totalizer. was the engine failure preceded by anything? Master caution, low oil pressure, high ITT, etc… do you have the fire handle mapped to anything? Accidentally hitting that will kill an engine. Edited February 24, 2023 by ASAP 1
Bog9y Posted February 25, 2023 Author Posted February 25, 2023 (edited) 15 hours ago, ASAP said: The only timer is the fuel totalizer. was the engine failure preceded by anything? Master caution, low oil pressure, high ITT, etc… do you have the fire handle mapped to anything? Accidentally hitting that will kill an engine. The master caution came on, gen dropped offline and it seemed like a flameout. Good point about about the fire handle, I don't think it got triggered but I do have a full Harrier pit setup so perhaps one of the inputs there may have triggered it. I'll have a look Edited February 25, 2023 by Bog9y
ASAP Posted February 25, 2023 Posted February 25, 2023 1 hour ago, Bog9y said: The master caution came on, gen dropped offline and it seemed like a flameout. Good point about about the fire handle, I don't think it got triggered but I do have a full Harrier pit setup so perhaps one of the inputs there may have triggered it. I'll have a look I’m not sure how DCS does birdstrikes but that’s not what I’d expect from one. I would think you would get some other bad stuff along with it, possible fire indications, high ITT, rapid rpm drop, rpm freezing. In general a bunch of bad indications, not just the engine flaming out and winding down peacefully. That is what I’d expect from fuel starvation, like pulling the fire handle or something like if you left the boost pumps off and did some aggressive negative Gs (although they suction feed just fine unless you do some real hiyaka maneuvers). I’d start with checking engine, fire handle and fuel/air control bindings to make sure it’s not your controls. 1
dporter22 Posted March 13, 2023 Posted March 13, 2023 It happens to me also at various times for no reason. No warnings, no abnormal indications, plenty of fuel, no birds, random failures not selected, etc.
razo+r Posted March 13, 2023 Posted March 13, 2023 11 minutes ago, dporter22 said: It happens to me also at various times for no reason. No warnings, no abnormal indications, plenty of fuel, no birds, random failures not selected, etc. Random failures can sometimes still be enabled even if you have turned it off in your and the mission setting. To figure that one out you would have to open the mission.lua of the mission and manually check it.
dporter22 Posted March 13, 2023 Posted March 13, 2023 Then what's the purpose of unchecking the random failures option if it doesn't actually work?
razo+r Posted March 13, 2023 Posted March 13, 2023 4 hours ago, dporter22 said: Then what's the purpose of unchecking the random failures option if it doesn't actually work? It does but there are rare cases where it doesnt happen. And so far I only have seen this 3 times in 2 years or something like that. So, it is rare, but worth to check. 1
Jackjack171 Posted March 24, 2023 Posted March 24, 2023 Just had the same thing happen to me over Guam. Just a regular FAM flight as I had not flown the A-10CII for some time. DO it or Don't, but don't cry about it. Real men don't cry!
Teshune Posted March 29, 2023 Posted March 29, 2023 (edited) Yeah well... Apparently, it happens when you pull back the throttle to iddle : It seems to shut down the engines for some reason... I realize it does not match the initial post's conditions but that's how it felt the first time it happend to me... Edited March 29, 2023 by Teshune
dporter22 Posted March 29, 2023 Posted March 29, 2023 Yes, it does seem to happen when pulling the throttles back. Obviously that should not result in engine shutdown.
Falconeer Posted April 2, 2023 Posted April 2, 2023 On 3/29/2023 at 2:52 PM, dporter22 said: Yes, it does seem to happen when pulling the throttles back. Obviously that should not result in engine shutdown. In the Warthog throttle, there is a detent in the idle setting. If i pull against the detent, the engines go to idle. If i pull them beyond the detent, the engines shut down (cut off setting) which is how it works. I can imagine that for joysticks without a detent, this would be an annoying issue, as pulling the throttle levers back to idle, results in shutting down the engine Planes: Choppers: Maps: Flaming Cliffs 3 Black Shark 2 Syria A-10C Tank killer 2 Black Shark 3 Persian Gulf F/A18C Hornet AH-64 Apache Mariana's F-16C Viper Afghanistan F-15E Strike Eagle Kola Peninsula Mirage 2000C AJS-37 Viggen JF-17 Thunder F-14 Tomcat F-4E Phantom
Yurgon Posted April 2, 2023 Posted April 2, 2023 (edited) 5 hours ago, Falconeer said: I can imagine that for joysticks without a detent, this would be an annoying issue, as pulling the throttle levers back to idle, results in shutting down the engine The TM Warthog is special in that the throttle OFF position is realized as a button that DCS can react to. When the button is ON and the throttle axis is sufficiently low near the IDLE stop, DCS will interpret this as the pilot shutting down the engine. And vice versa, when the button is switched from ON to OFF, DCS will interpret this as moving the corresponding throttle from OFF to IDLE. However, any other throttle out there that does not have this very specific behavior is not going to prompt DCS to shut down the engine at or near the throttle axis IDLE position. Unless players have accidentally mapped the throttle's engine OFF keybind to an input device or the keyboard, there's no way DCS is going to set an engine to OFF just because a player moves the throttle to idle. (With controller specific software like what Virpil offers for their devices, the TM Warthog style behavior can be emulated; it's possible to limit the axis range and to also define a part of the axis range to just activate a DirectX button. If I'm not mistaken, that's also what TM does in the Warthog internally, they just don't expose this behavior to their TARGET software). Plus, when the engine actually get set to OFF, this is very easy to confirm visually in the DCS pit. As is so often the case, without a track (preferably a very short one) this is going to be extremely hard to debug, so anyone saying "it happened to me, too" isn't really helping. If you guys have a hunch what kind of situation prompted the behavior, try to replicate it and if you succeed, make sure to save the track and send it to us. Edited April 2, 2023 by Yurgon
Lee1 Posted April 10, 2023 Posted April 10, 2023 Birdstrike. Used to happen quite often in the A10 until I disabled birds. No more random engine fires and failures.
Recommended Posts