CoBlue Posted August 8, 2016 Posted August 8, 2016 Engine is not flaming out during negative G's. (1.5.4.55584 Update 3) I can fly long time in negative G, without any flameout. Anyone else seeing this? i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
Art-J Posted August 8, 2016 Posted August 8, 2016 Nope, flaming out here allright, both with simplified engine management option turned on and off. Tested in instant free flight mission, and some random custom one. Any particular throttle position where this happens for You? i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
CoBlue Posted August 8, 2016 Author Posted August 8, 2016 No particular throttle position. Flying with simplified engine management allays off, tried to recycle from off/on. Looked trough all options. No flameout in MP. Must be something wrong on my end, very strange indeed. i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
Art-J Posted August 8, 2016 Posted August 8, 2016 Well, I tested in SP only, as I don't do MP. There might as well be some bug related to online playing. Check SP first and see how it goes. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
grunf Posted August 8, 2016 Posted August 8, 2016 I've just checked on some random server, the engine flamed out as expected. Which server were you on? Can you try a different one? I don't think it's the case of server enforcing simplified engine management, because even with it turned on the engine will flame out.
CoBlue Posted August 8, 2016 Author Posted August 8, 2016 Both single & MP(F-5 vs Mig-21 server). I can do -2G all day long without flaming out. i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
grunf Posted August 8, 2016 Posted August 8, 2016 Both single & MP(F-5 vs Mig-21 server). I can do -2G all day long without flaming out. Strange. Have you tried repair?
Ramsay Posted August 9, 2016 Posted August 9, 2016 Engine is not flaming out during negative G's. (1.5.4.55584 Update 3) I can fly long time in negative G, without any flameout. Anyone else seeing this? Might be best if you post a track, as I'm not seeing your issue. Temperature +20, no wind, cloud base 300m Clean aircraft, 83% fuel, most tests at mil (100%) or stage 1 AB @ 2000m inverted - engine cut out after ~5 sec pushing the nose down for short periods - engine stayed lit @ 5000m inverted - engine cut out after ~5 sec pushing the nose down for short periods - engine occasionally cut out i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
CoBlue Posted August 9, 2016 Author Posted August 9, 2016 Here's a track. Haven't done repair yet, I'll try it later. i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
Art-J Posted August 9, 2016 Posted August 9, 2016 Start higher or roll on Your back and do inverted loop, 'cause You run out of altitude too fast ;). According to the manual, without afterburner the engine should sustain negative Gs for at least 15 seconds, with 1st AB - at least 5 seconds, with 2nd AB - at least 3 seconds. In the track You weren't pulling neg Gs long enough for our test purposes. On the other hand, when I did simply inverted flight with no AB, the thing flamed out certainly faster than 15 seconds... so the simulation might be a bit off, but in opposite direction to Your observation :D ? i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Golo Posted August 9, 2016 Posted August 9, 2016 Yea, what Art-J said, longest you were in negatives I counted 7s, the aircraft can handle that. Critical amount of Gs are 0, you can stay there only for a two seconds or so.
Art-J Posted August 9, 2016 Posted August 9, 2016 OK, after another attempt I partially take back what I said, 15 seconds of inverted flight with properly negative G and N1 of ~95% and th engine flamed out. I guess the time around 0 G affects the final result, as Golo noted above. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
CoBlue Posted August 9, 2016 Author Posted August 9, 2016 Alright thanx for all your inputs :thumbup: I didn't know that 0G was so critical, thought that 21 didn't like negative G's at all. So it's all good now :) i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
portman Posted August 10, 2016 Posted August 10, 2016 During one of my last flights, the engine flamed out two times in a row. The first time I was able to relight, but the second time I didn't make it, though all parameters were OK. Did anyone experience the same? As far as I remember, in the past I was able to relight the engine as often as I wanted to. Mancher zum Meister sich erklärt, dem nie das Handwerk ward gelehrt!
Art-J Posted August 12, 2016 Posted August 12, 2016 During one of my last flights, the engine flamed out two times in a row. The first time I was able to relight, but the second time I didn't make it, though all parameters were OK. Did anyone experience the same? As far as I remember, in the past I was able to relight the engine as often as I wanted to. My experience is different. When I was flaming out on regular basis during various silly dynamic climb attempts, I could relight only once or twice. I guess, apart from limited air supply in the system, it depends on how the flameout happened, though I never investigated the issue closer. The engine damage and limitations have been reworked multiple times lately, so we've got to re-learn some aspects of its operation anyway. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Nerd1000 Posted August 12, 2016 Posted August 12, 2016 During one of my last flights, the engine flamed out two times in a row. The first time I was able to relight, but the second time I didn't make it, though all parameters were OK. Did anyone experience the same? As far as I remember, in the past I was able to relight the engine as often as I wanted to. According to the manual the engine relight system depends on an auxiliary oxygen supply that only lasts a couple of uses. Oxygen is consumed so long as the mid-air relight switch is on, so if it takes too long the first time you're likely to be unable to re-start the engine again.
portman Posted August 12, 2016 Posted August 12, 2016 Thanks you two :) Mancher zum Meister sich erklärt, dem nie das Handwerk ward gelehrt!
Recommended Posts