Ala12Rv-watermanpc Posted June 6, 2018 Posted June 6, 2018 Just wanted to know if its normal that afterburners take so much time to shutdown once you decrease power to MIL...they take like 7 seconds to shutdown which is not common in any other plane...anyone else noticed this?, is this the way it works in the real hornet?... Also, if you drastically reduce from AB to idle for instance the burners shutdown faster but still taking a big time instead of "almost" shutdown instantly. thanks! Take a look at my MODS here
mastersetter Posted June 6, 2018 Posted June 6, 2018 Hmm, thats odd. I don't have that issue with mine, when i reduce to mil it doesn't take 7 seconds for the AB to cut for sure, maybe 2, 3 at the most? I have WH hotas too. Not at my pc so cant be 100% sure but i don't remember noticing any delay. i5-7600K @ 4.8 | 32GB | 1080 | Rift S | TM MFD & WH HOTAS-10mm ext + TFRP
Svend_Dellepude Posted June 6, 2018 Posted June 6, 2018 Play with the curve on your throttle. This happens if your MIL position is too close to the afterburner detent. Else you can just pull your throttles back to mid position, from A/B, and push to MIL again. Cures the problem too. There is something wacky with the throttle axis now so maybe I wouldnt spend too much time making curves and stuff. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
NahkaSukka Posted June 6, 2018 Posted June 6, 2018 https://forums.eagle.ru/showpost.php?p=3507097&postcount=4 I set these values for both engines and modified my TM WH throttle so i can push through to AB and it works perfectly.
Ala12Rv-watermanpc Posted June 7, 2018 Author Posted June 7, 2018 Great help guys, very appreciated!:thumbup: Will try the advices and report, thanks! Take a look at my MODS here
escaner Posted June 7, 2018 Posted June 7, 2018 The animation takes a while to disappear, but the fuel flow reading drops much faster [sIGPIC][/sIGPIC]
Fri13 Posted June 7, 2018 Posted June 7, 2018 I noticed that going from 100% to 60% takes long time. First you pull throttle back and nothing happens, then you pull more and more and nothing happens and then finally at 1/3 of the throttle the RPM goes from 100% to 90% or so and then starts to slow down by the sound. Haven't read the fuel flow as can't read it in the VR but basing to sound and the RPM number and visual needles the engine takes very long time to respond to any throttle down motion. What has leaded to many overshoot situations as for many seconds you are just in full relight and can't get the speed to drop fast enough. And who would even use any curves for throttle, stick or pedals? If curves are required then there is something wrong in the simulation input or the pilot itself. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
chinpok Posted June 7, 2018 Posted June 7, 2018 Probably I'm wrong but isn't it an "analog multi-stage" ab? so when you reduce the throttle first the nozzle position is changing. But maybe I remember it like this because the delay you mention.
Ala12Rv-watermanpc Posted June 7, 2018 Author Posted June 7, 2018 As promised here is my report: Yes, you all were right, it was my custom curve what was bugged with my detent mod in the WH...after editing it AB remain just a couple of seconds after going back to mil power...here are my values: 0 8 16 25 33 44 56 68 79 90 100 Thanks a lot! Take a look at my MODS here
Recommended Posts