fixed Please fix the afterburner

[Juancio]

When going from max dry thrust to full afterburner the AF sometimes lights, sometimes doesn't and sometimes only one lights, causing uneven engine thrust. Having to yank the throttle lever back and forth in the middle of a dogfight to get the engines to full power is utterly exasperating.

Please have a look at this.

 

Thanks

[fjacobsen]

Have You checked Your controler calibration ?

 

I don´t see this with my CH-Products Throttle Quadrant.

 

FinnJ

[Juancio]

Have You checked Your controler calibration ?

 

I don´t see this with my CH-Products Throttle Quadrant.

 

FinnJ

 

Yep, checked the controller already, everything is fine. I even tried using the keyboard to control engine power and the issue still persists. I noticed this only happens with the F5E, not with the rest of the modules.

[SkateZilla]

make sure you dont have a cross linked axis (ie left throttle axis linked to another controllers axis).

[Eddie]

Are we sure it's not intended behaviour? Afterburner ignition failures are far from uncommon, and engines without digital control units can't resolve the issue automatically.

 

I mainly see them at when advancing into reheat from below mil power and at low airspeed and/or high altitude, doesn't seem unreasonable to me.

[ThorBrasil]

When going from max dry thrust to full afterburner the AF sometimes lights, sometimes doesn't and sometimes only one lights, causing uneven engine thrust. Having to yank the throttle lever back and forth in the middle of a dogfight to get the engines to full power is utterly exasperating.

Please have a look at this.

 

Thanks

 

it is true. This happened with me. 6 times flying.

[Juancio]

make sure you dont have a cross linked axis (ie left throttle axis linked to another controllers axis).

 

Already checked that, remapped everything. Problem persists.

 

This issue was reported before.

 

http://forums.eagle.ru/showthread.php?t=170821

[SkateZilla]

Devs asked for a track file of the problem and one was provided,

 

will see if I can re-produce tonight after work.

[Kelevra9987]

I don't know but I fly the Tiger now since release and didn't had a single AB Failure. It ignited every single time on both engines. I had a flameout once after a inverted loop but that was it.

[acdelta57]

I think I've had one AB failure, and I was excited because I was like wow they modeled this too!

[Juancio]

I think I've had one AB failure, and I was excited because I was like wow they modeled this too!

 

Please don't hijack the thread. It's not an AB failure what I was reporting, it's a throttle response problem. I can make the AB work if I yank the lever around a little bit, but that's not how it's supposed to work.

 

Thanks

[Juancio]

Don't see any hijacking here at all. Furthermore your first post said that AB fails to light. Now you are saying it's not an AB failure.......

 

However, when does this happen? Tried every combination of speed, AoA and G-load and didn't manage to experience a single AB fault.

 

Sorry, maybe I didn't make myself clear. What I'm experiencing it's not an AB system failure per se. The problem is related to the throttle response from full dry thrust to full afterburner. When I apply the necessary power needed to light the AB (from max dry thrust) during normal flight conditions (pulling no Gs, level flight, whatever), it doesn't go into full AB, but it sticks to max dry thrust (sorry for being redundant).

AB lights if I decrease power and proceed to reapply it fully, so as you can see, this is not a "AB system failure" but something else. It happens while flying the F5E only.

[Svend_Dellepude]

I see. Have you tried changing the throttle curve/deadzone?

 

^^^This!

I had this too, but after adjusting my MIL setting a little aft, the problem went away.

On a sidenote; it seems like the F-5 doesn't pick up input if they happen too fast.

[Juancio]

I see. Have you tried changing the throttle curve/deadzone?

 

I did try this but it didn't solve the problem. After some testing I noticed the throttle levers in the cockpit move when given joystick imput but the AB fails to light, even when those levers are at the MAX position, so this doesn't seem to be a curve setting problem. AB lights if I reapply power a couple of times. Something seems to be out of sync.

 

Thanks

[Antimon]

Op didn't post control specs but I have noticed the same and I suspect this has to do with the TM Warthog throttle. Had trouble assigning the throttle axis in game due to physical dual linkage in the first place and DCS seems to recognize both throttles as the same axis and sometimes as seperate. So if it's not intented behavior it's more likely a hardware related issue...

[escaner]

Devs asked for a track file of the problem and one was provided,

 

will see if I can re-produce tonight after work.

 

 

Did they reply about this problem?

It is a bug?

Is this WAI? If WAI, how are we supposed to systematically get a good burner light?

[BadHabit]

Are we sure it's not intended behaviour? Afterburner ignition failures are far from uncommon, and engines without digital control units can't resolve the issue automatically.

 

I mainly see them at when advancing into reheat from below mil power and at low airspeed and/or high altitude, doesn't seem unreasonable to me.

 

This the answer everybody is ignoring. Treat the throttle gently. It's only a good habit :thumbup:

[Nightwolf]

I'm pretty sure it's not a bug. I've experienced this, and if you look at your fuel flow gauges, the flow will go to AB levels, but the nozzle size will bump and then stay low. As far as I can tell it's the engines not lighting the afterburner, but the plane has no way to know this, so it continues to pour fuel into the engine. Like BadHabit said, slower throttle movements, and lots of rapid changes from mil to AB will cause your burners to not light. Be gentle!

[escaner]

Being gentle on the throttle does not ensure proper lighting. I have suffered this both pulling G, at high AoA and at 1G on the runway going from stabilized MIL to minimum AB just after releasing brakes for takeoff.

 

I also think that it is not a bug per se and so I stated it in other thread long ago (https://forums.eagle.ru/showthread.php?t=172526). Anyway, Skatezilla said that the developers were contacted 16 months ago, and every time that I suffer this problem, I remember his post. Therefore I am interested in knowing the official response. Further speculation adds nothing that was not already said in this and other similar threads.

[Eldur]

I've been flying the Tiger II today and also noticed that habit. Nozzles stay at ~20%, FF goes up to ~ low AB level. This all happened *especially* when being gentle on the throttle (like sitting in a Me-262, remember those Jumo 004 engines catching fire in a well known WWII sim when advancing the throttle too fast below 6k RPM?). When I just firewalled them levers through the MIL-AB "detent" from ~100%+ RPM, they ignited practically every time...

 

This the answer everybody is ignoring. Treat the throttle gently. It's only a good habit

 

I'm pretty sure it's not a bug. I've experienced this, and if you look at your fuel flow gauges, the flow will go to AB levels, but the nozzle size will bump and then stay low. As far as I can tell it's the engines not lighting the afterburner, but the plane has no way to know this, so it continues to pour fuel into the engine. Like BadHabit said, slower throttle movements, and lots of rapid changes from mil to AB will cause your burners to not light. Be gentle!

 

... but well, that was just one flight. I also remember that this already occured when the F-5E has been released and I thought it was a bug, but I had patience to wait for a fix. Looks like it's a feature, but there doesn't seem to be a 100% safe way how to do it reliably. IIRC it's no good idea to slam the throttle forward from lower regimes though.

[dolfo]

...s no good idea to slam the throttle forward from lower regimes though.

 

I think it is more of an AOA than a throttle burst thing.

[escaner]

And then, out of thin air, almost seven years later it appears in the changelog as fixed...

[Flappie]

Yes, it's now fixed.