monkie Posted September 13, 2013 Posted September 13, 2013 Was working with the throttle under 1.2.6 and noticed that as I twist to increase there is no change in engine RPM until the very bit of travel and then it's a full increase. I thought I remember in 1.2.5 that you could get a gradual increase in engine RPM as the grip is twisted. Sager Laptop, i7-6700k 4.00GHz, 16GB RAM, GTX 980M, 1920x1080, TIR 5, Windows 10
b00ce Posted September 13, 2013 Posted September 13, 2013 Works fine for me, you probably have to delete your control profile in your DCS folder. LG 34UC97 34" 3440x1440 monitor | 2x GTX-980 G1 Gaming I7-5820k @ 3.3GHz | 16GB Corsair Vengeance DDR4 @ 2133Mhz Samsung 840 EVO 120GB & 1TB SSDs | Seagate 3TB HDD TM Warthog | Saitek Pro Flight Combat Pedals
number3 Posted September 13, 2013 Posted September 13, 2013 Was working with the throttle under 1.2.6 and noticed that as I twist to increase there is no change in engine RPM until the very bit of travel and then it's a full increase. I thought I remember in 1.2.5 that you could get a gradual increase in engine RPM as the grip is twisted. I too have noticed this as well. During the startup, gradually increasing the throttle does nothing until I get to maximum throttle. I have not mapped my throttle to anything, I simply use the mouse scroll to achieve this. Also I have not cleared and re-loaded the default key profiles. Not sure if that is the solution or not. 314-я смешанная авиационная дивизия 314th Mixed Aviation Division: The "Fighting Lemmings"- Forums: http://314thsquadron.enjin.com/ - ED Forum Group: http://forums.eagle.ru/group.php?groupid=119
Nealius Posted September 13, 2013 Posted September 13, 2013 Same thing for me. It takes ~7 keyboard hits to increase from idle to full, and RPM does not increase at all until the 7th and final key stroke. Although I do hear the engine whine a bit louder in the first 6 strokes, the tachometer doesn't start increasing until the 7th.
Donglr Posted September 13, 2013 Posted September 13, 2013 does that necessarily means it's a bug? Maybe that's just how the governor works. Have you tried without it? I think without it it has more of a linear correlation between throttle and RPM
TurboHog Posted September 13, 2013 Posted September 13, 2013 does that necessarily means it's a bug? Maybe that's just how the governor works. Have you tried without it? I think without it it has more of a linear correlation between throttle and RPM It's the new idle stop range that is half-way implemented. The physical part of the collective is working properly (with the lock button that allows throttle to move from idle to stop). However, the engines do not respond accordingly. This is not a bug it's WIP. 'Frett'
monkie Posted September 13, 2013 Author Posted September 13, 2013 thanks for clearing it up Sager Laptop, i7-6700k 4.00GHz, 16GB RAM, GTX 980M, 1920x1080, TIR 5, Windows 10
Recommended Posts