Jump to content

Engine Response to throttle input?


lobo

Recommended Posts

Is the current engine response to throttle input accurate? or is this an area that is still a WIP?

 

It seems to to take (large) fist fulls of of power to get a response from the engines. I'm finding this particularly challenging when on approach.

 

Thanks

Lobo's DCS A-10C Normal Checklist & Quick Reference Handbook current version 8D available here:

http://www.digitalcombatsimulator.com/en/files/172905/

Link to comment
Share on other sites

I'd say almost the opposite, they feel very sensitive. I find it difficult to maintain a speed without constantly moving the throttle tiny steps. I tried AAR for the first time today and it's the same, constantly moving the throttle to maintain desired speed. The tiniest increments I can do gives me big(5-10+ knots) changes in speed.

Link to comment
Share on other sites

I'd say almost the opposite, they feel very sensitive. I find it difficult to maintain a speed without constantly moving the throttle tiny steps. I tried AAR for the first time today and it's the same, constantly moving the throttle to maintain desired speed. The tiniest increments I can do gives me big(5-10+ knots) changes in speed.

 

You find the throttle response on approach to be very sensitive? In the Hornet? :pilotfly:

Lobo's DCS A-10C Normal Checklist & Quick Reference Handbook current version 8D available here:

http://www.digitalcombatsimulator.com/en/files/172905/

Link to comment
Share on other sites

You find the throttle response on approach to be very sensitive? In the Hornet? :pilotfly:

 

Obviously you won't see an instantaneous response, it might take a second but the change in thrust is definitely large relative to throttle movement.

 

How big changes to throttle would you say you need to see a difference in engine performance?

 

Let's say I'm flying approach and I'm at 150 knots and falling slightly. If I make slight increase in throttle then the speed will slowly start increasing instead and after a while I will have to decrease it to maintain 150 knots. I'm definitely not adding quarter throttle or anything like that, I just push it enough that I feel the slightest movement. But this could of course differ between HOTAS. I have an X52, what do you use?

Link to comment
Share on other sites

In another thread about the real life Hornet guy who is making vids I read this:

 

"As of the 3rd vid he has only commented once on the flight model but one observation he has that is shared by many including myself if the throttle response is slow/weak/ iirc. While doing pattern work he had to push the throttle really high and into burner just to achieve another 10 knots or so.

To early to call it a FM issue or something that needs tweaking but I am looking forward to when he turns his attention to the fidelity of the aircraft."

 

This ^ is what I am noticing also.

 

I'm using the Warthog Throttle/Stick.

 

Problem could be the drag as currently modeled...

 

https://forums.eagle.ru/showthread.php?t=213353


Edited by lobo**

Lobo's DCS A-10C Normal Checklist & Quick Reference Handbook current version 8D available here:

http://www.digitalcombatsimulator.com/en/files/172905/

Link to comment
Share on other sites

I am not a real jet pilot, but I play one on my PC. With that disclaimer I agree that the throttle seems sensitive enough. Apparent "sluggishness" is likely due to the inertia of the 16 ton mass of the aircraft. Response not dissimilar from VRS F/A-18E. Watch airspeed. You will see it changing before the E bracket starts moving. I find that many hours of practice are required to attain the muscle memory and anticipation needed to prevent constant throttle over-correction. I am still learning, but improving in that area. Acquiring that muscle-memory can be hampered by too frequent adjustment of the throttle thrust curve, so I recommend minimizing that action. Set it and forget it.

 

 

 

In a related matter, I HIGHLY recommend viewing Jar113's third Youtube video on Case 1 recoveries. His explanation of trimming to on-AOA finally turned on the light-bulb for me. You will learn that in proper recovery technique the stick is used ONLY to control bank angle and use ONLY the left hand to control pitch. Call the ball.

 

 

 

https://www.youtube.com/watch?v=Xso1mMo_1Mg

Link to comment
Share on other sites

To me, it feels a bit slow to spool-up. Kind of reminds me of the old turbojet engine behavior.

Alienware Area 51 R5 - Intel i9 7980XE (4.7 GHz), 32GB Dual Channel HyperX DDR4 XMP, Dual NVIDIA GeForce GTX 1080 Ti Graphics 11GB GDDR5X SLI, 4.5 TB combo of SSDs/HDDs, Alienware 1500 Watt Multi-GPU Power Supply, Alienware 25” 240Hz Gaming Monitor, Alienware Pro Gaming Keyboard, TM HOTAS, TM Cougar F-16C MFDs, Saitek Pro Flight Rudder Pedals, TrackIR5, Win10 Pro x64

Link to comment
Share on other sites

Obviously you won't see an instantaneous response, it might take a second but the change in thrust is definitely large relative to throttle movement.

 

How big changes to throttle would you say you need to see a difference in engine performance?

 

Let's say I'm flying approach and I'm at 150 knots and falling slightly. If I make slight increase in throttle then the speed will slowly start increasing instead and after a while I will have to decrease it to maintain 150 knots. I'm definitely not adding quarter throttle or anything like that, I just push it enough that I feel the slightest movement. But this could of course differ between HOTAS. I have an X52, what do you use?

 

It may well need a little tweaking here and there perhaps..

 

This is flying on the backside, so the aircraft will seek this on speed AOA. You should be more concerned with lift and descent rates with power, not speed, I don't even look at the speeds when on speed.

 

The power setting on the throttle should be 50% to 90% always to keep the engines spooled up.


Edited by David OC

i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro

Chuck's DCS Tutorial Library

Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link

Link to comment
Share on other sites

I keep constant back pressure on my stick so I am always close to stalling (high end of bracket), reducing power will quickly loose altitude, so there's no delay reaction or over correction.

 

also helps when i'm high on final. pull up on stick and power down to drop altitude, followed by power up to keep from falling straight down.

Ryzen 1700 @ 3.8GHz / 32GB( 4x8 ) @ 3.2GHz / 1TB ADATA NVMe System Drive / 232GB NVMe Samsung 960 / ASUS dual RTX 2080ti / Reverb / Rift CV1 / T-16000M FCS flight pack

 

A10C/M2000C/F5E/SA342/Mi8/UH1H/KA50/AJS-37/FA-18C/AV-8B/F-14/Mig29/CA/SU-27

Link to comment
Share on other sites

This is also highly dependent on what throttle hardware you're using. Throttles with lots of throw, such as the TM Warthog, will require more movement for an equivalent engine adjustment compared to a shorter throw throttle, such as the T16000M. I just switched to the Warthog HOTAS and I can tell you that getting used to the throttle movement per equivalent response is not easy, especially during sensitive stages like carrier recoveries.

Link to comment
Share on other sites

Its not throw, (at least on the TM Warthog), as the difference between gaining and losing altitude whilst on speed AOA is about 2cm of travel on my throttle.

 

 

It's engine response for me at least. The hornet engines as currently modelled make the A-10 seem quick to respond. I'm constantly wallowing during final approach and over-compensating. I'll get used to it....Then have to re-learn when patched.

 

 

All part of the beta fun! It was the same during A-10 beta. It's only frustrating when we don't know whether its WAD and a "training issue" or its a WIP feature and we'd just better live with it for now.

[sIGPIC][/sIGPIC]

i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals

Link to comment
Share on other sites

The engine response is delayed deliberately, it doesn't instantly reach the inputted commands, like the delay in anything with an input and output, it's based on the design on the mechanism. The specific time of that delay is something OP noticed because they flew something that had an engine with a faster response. That's been coded very specifically as it's extra work to model and engine spooling up to speed. It's no accident, ED did it this way for a reason and based on some data (that I don't have or want to look for). So the fact it's been modelled deliberately means that logically speaking someone had some data to suggest that this is how it works, as opposed to how the driver wants it to feel.

The rest of the debate is down to engine manufacturing specs and real pilot data, so for now, you can assume it's nothing more or less than modelled as accurately as ED can.

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Link to comment
Share on other sites

We don't see acceleration on the screen

 

Due to the inertia of the rotating masses, it will inevitably take a little bit of time for the turbine to spool up to the new rev rate after a throttle input and deliver the desired thrust resulting in acceleration. That spool-up time is probably not the issue and I expect that acceleration builds up very quickly. And the RL pilot doesn't need to look at any screen or gage he or she feels the acceleration in the body.

We simmers however are handicapped as we neither feel nor see the acceleration. We only see the speed changing as a function of acceleration and TIME. I did a bit of calculation, using a mass of 17,000 kg and a thrust of 10 kN. If we disregard drag, this would result in acceleration = 5.88 m/s2, which results in a speed increase of 11.4 kt after 1 s. Now in reality there is drag, and it increases with the square of speed. So in reality the speed will increase by significantly less than 11.4 kt when you are already at a high speed; but it should be close at final approach speed around 140 kt. Unfortunately, I could not find any numbers for the drag of the F/A-18.

 

Even 1 second in a tense situation seems like a very long time, and this might be why we feel that the response to throttle input is too sluggish. Unlike the SU-27, the F/A-19C cockpit doesn't indicate acceleration, which would be desirable from a sim point of view but probably too unrealistic.

 

PS: I only know basic physics so I'd be happy to be corrected by an expert.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

If it’s accurate then I’m ok with it. However, my initial impression is that the spool up time in general seems excessive for a fighter. Feels like a turboprop in terms of lag and that just seems odd in a high performance aircraft.

 

This is very alien to most sim pilots and IRL pilots because only the Navy fly this way when landing at the carrier or when always practicing at an airfield. The power feels off to most because your are flying the backside technique at the optimal wing coefficient and not a normal approach. Controlling speed with the stick and rate of descent with the throttle. Curly (Engineer) wrote and provided great links in this post here and more in this one.

 

 

Quote

"It was found in a lot of aircraft configurations that the lift to drag ratio decreases at high lift coefficients. Total drag increases with decreasing airspeed, this is as the region of reverse command or the backside of the drag curve."

 

He also has this thread going about some change he thinks are needed to the FCS.

 

I have a thread consolidating On speed AOA here.

 

 

Also, make sure you are under 33,000 pounds when landing or she becomes a real pig to fly on speed AOA.


Edited by David OC

i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro

Chuck's DCS Tutorial Library

Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link

Link to comment
Share on other sites

Yeah it's not very responsive on my end either. I'll try to tweak it out a little and see if it changes

  • MB: MPG Z790 EDGE WIFI
  • Memory: WD Black SN850X 2TB PCIe Gen4 NVMe M.2
  • CPU: Intel Core i9-14900K Desktop Processor 24 cores (8P+16E) 36M Cache
  • EVGA 1200W Gold PSU
  • MSI RTX 3090
  • TrackIR on Samsung 49 inch Odyssey Widescreen
  • No money in my pocket lol
Link to comment
Share on other sites

In using a warthog throttle and setitng saturation to 85% on the y axis of the throttles has helped increase the response by quite a bit so it's better now. Give that a shot if you have a warthog and see if it makes a difference for you.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Link to comment
Share on other sites

In using a warthog throttle and setitng saturation to 85% on the y axis of the throttles has helped increase the response by quite a bit so it's better now. Give that a shot if you have a warthog and see if it makes a difference for you.

 

 

Yes but surely that means that at 100% throttle fwd movement you are only getting 85% in game? bye bye afterburners?joystick.gif

[sIGPIC][/sIGPIC]

i7 9700k | 32gb DDR4 | Geforce 2080ti | TrackIR 5 | Rift S | HOTAS WARTHOG | CH PRO Pedals

Link to comment
Share on other sites

Yes but surely that means that at 100% throttle fwd movement you are only getting 85% in game? bye bye afterburners?joystick.gif
I don't think it modifies how long your throttle travels but rather the response of the throttle compared to the position it's at.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Link to comment
Share on other sites

In using a warthog throttle and setitng saturation to 85% on the y axis of the throttles has helped increase the response by quite a bit so it's better now. Give that a shot if you have a warthog and see if it makes a difference for you.

 

 

On a Saitek X52 but I'll try it thanks :thumbup:

  • MB: MPG Z790 EDGE WIFI
  • Memory: WD Black SN850X 2TB PCIe Gen4 NVMe M.2
  • CPU: Intel Core i9-14900K Desktop Processor 24 cores (8P+16E) 36M Cache
  • EVGA 1200W Gold PSU
  • MSI RTX 3090
  • TrackIR on Samsung 49 inch Odyssey Widescreen
  • No money in my pocket lol
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...