Throttle sticks at 90%

[VAF [136] Striker]

I did a search and haven't found any posts describing this problem. Maybe it's been reported before or internally but I haven't found anything. We use the F-5E for training and it would be nice if the throttle worked properly. I would like to know if this is being addressed in the upcoming new releases.

 

The first example is in climbing and diving (skip to about 0:20) showing that the throttle will be fine until you reach 15,000 feet and then will suddenly snap to 90%. My throttles calibrated and set to 102% when they reach the afterburner detente. I have tested this in Nevada and we have a similar behavior but it seems to work properly all the time when starting from the ground.

 

 

The second video shows that the problem exists from startup all the way through taxi and takeoff (skip to about 3:35 where I test the throttle). Also when in the pattern and coming in for a landing the throttle will again stick at 90% making safe landing difficult. If I push the throttle into afterburner and then back to the detente it goes back to 102%.

 

Edited January 3, 2018 by 75th-VFS-Striker

[AcroGimp]

I just had a somewhat similar experience.

 

Flying the BFM NTTR FAM Mission from the Maple Flag campaign, we had just come out of the training area at Student Gap, cruising along at 300 KIAS and Angels 24, suddenly the throttle sticks in IDLE, I move it forward it moves forward, but as soon as I stop moving it goes back to IDLE - I struggle with this for a minute or so and then have an idea. I pause TrackIR (Numpad + in my setup, going to change), I press Numpad + and they move to Max A/B, and now they move to Max A/B instead of IDLE, great, won't crash for lack of thrust now, but how the hell will I land?

 

 

I fly around trying burn fuel down, keeping a lot of G on with boards out to keep speed reasonable while descending into Vegas area, and find that if I constantly exercise the throttle it will stay around idle. I get the kiss off from the IP that mission is completed, now I can try to bring this pig back home.

 

Finally make it in close, well below BINGO fuel, touch down, take my hand of the throttle to deploy the chute, collapse a gear and spin off the runway but stay upright, with both engines still in Max A/B - I go skidding around the grounds of Nellis like a chicken with its' head cutoff until first the left engine, then right engine die from fuel starvation - I just managed to NOT hit any planes in the ramp, and I ended up near the Aggressor ramp.

 

Not sure if it is a campaign issue, a DCS issue, an F-5 issue, a Thrustmaster T16000 HOTAS issue, or a Voice Attack issue - although VA failed to respond to any commands (and keyboard commands were gone) after the initial throttle control failure.

 

I was sweating like I was really there - actually a lot of fun trying to figure out what I could do to secure one engine or something but the keyboard controls were nonresponsive.

 

Ideas?

 

'Gimp

[Sarge55]

Eject, rather than risk destroying millions of dollars of aircraft on the ramps, not to mention the landscaping bill.

 

Oh, you mean the throttle bug. :megalol: Num Pad - didn't work? Odd that Num Pad + did.

 

I would say add your experience to the bug report. Since you had completed the mission fine it wasn't duplicated control settings.