Engine Response to throttle input? - Page 9 - ED Forums


Thread Tools Display Modes
Old 08-07-2018, 12:22 AM   #81
Join Date: Mar 2016
Posts: 194

This was my post in another thread I also found several other GE sources that showed less then 4 seconds idle to mil.

I was just looking at some documents and several of them have said under 4 seconds from IDLE to initial A/B light on the F404. I know A/B light time is random as engine has to go through the process etc. I have tried to time it in the sim and even if only count time after I push throttle full forward its 5.5-6.5 seconds from idle to 100% I wonder if this is why some feel the drag is to high or very easy to get behind the power curve. This is measuring it after I already pushed throttles up so thats letting engines get up about 75% before I even hit timer lol. If I time from when I start moving throttle it takes about 6.5 or little over like theres a bit of lag for the command to hit FADEC or we. I am only timing to 100% on display not A/B light etc.

Is the throttle response to slow? I know the turbines spool from Low RPM slower then High RPM but even on the Wiki it says the F404 was known to respond fast for carrier ops. Says around 4 seconds for idle to lighting A/B. This is what several documents show online aswell.

In the GE document it says on average 3.25 seconds from idle to full thrust. The F404 in game doesn't spool idle to full thrust in 5 seconds let alone 3.25.

Several Official Sources.
Rig: 5960X @ 4.5GHZ 32GB 3000Mhz DDR4 Titan XP Dell 3415W 21:9 Thrustmaster Warthog

Last edited by HawkDCS; 08-07-2018 at 12:25 AM.
HawkDCS is offline   Reply With Quote
Old 08-07-2018, 02:17 AM   #82
bbrz's Avatar
Join Date: May 2016
Location: Europe
Posts: 485

Looking at the airplane acceleration table Druid provided, the Hornet needs only 4sec to accelerate by 60kts.
Considering that the engine acceleration alone takes already 3sec in the DCS Hornet, the too slow RPM/thrust build up might be an indication of a too low basic airframe drag.
This in turn might explain the too high gear and/or flap drag in an attempt to offset the too low basic drag.
bbrz is offline   Reply With Quote
Old 10-08-2018, 10:21 PM   #83
Kingsnake's Avatar
Join Date: Feb 2009
Location: US
Posts: 298
Thumbs up Thank you! :-)

Originally Posted by Panthir View Post
The only way to fix this "deadband" is to go to Throttle Axis tune and set SATURATION Y to 83% for both Throttles. It works for Warthog and other Throttles as well.
Thank you so much! I gave refueling a try today and was having trouble due to the lag in response. I either was at too much power or not enough and kept playing that back and forth game. I found your post, changed to the 83 Saturation and wow did that make all the difference. I went back up with these setting's and fully topped off on the first try. Even my landing at Khasab afterward was much easier staying on speed. Awesome tip! Thanks again!

CH Settings for the F/A-18C:

Pitch 4 Curve
Roll 2 Curve
Rudder 5 Curve
Thrust 83 X & Y Saturation
Left & Right Brakes 2 Deadzone Inverted

Windows 10 1809 64-bit, AMD FX-6300 OC 4.00 GHz, EVGA GTX 1050 Ti SC 1.83 GHz 4GB (416.34 Drivers), 16GB DDR3 RAM
CH Fighterstick Pro, CH Pro Throttle, CH Pro Pedals, TrackIR 4 (5.4 Software), SRS
[ DCS World: (Open Beta) ]
Nevada, Persian Gulf, DCS A-10C Warthog, DCS Black Shark 2, Lock On Flaming Cliffs 3, DCS: Combined Arms, DCS: Hawk T.1A, DCS: M-2000C, DCS: AJS-37 Viggen, DCS: AV-8B Harrier II Night Attack, DCS: F/A-18C Hornet
Kingsnake is offline   Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 11:15 AM. vBulletin Skin by ForumMonkeys. Powered by vBulletin®.
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.