4.35.2 Throttle doesn't move at ramp start
-
Hi all, After update at U2, I’ve noticed that, at ramp start with the plane “dark and cold”, the throttle doesn’t move at all, making inpossible the engine start procedure. It happens with different F16’s versions at different scenario, either in TE or CMP. If I start the simulation with engine running or in flight, everithing goes ok, as usual. Does anybody experienced this issue ? Any Idea ?
Thanks in advance -
Has been this way since 4.34 with the new startup procedure. It will move once you hit the indent.
-
hit [alt+I] to move the throttle out of the ‘cutoff’ position, then see if it moves
(but then hit [alt+I] again to return it to cutoff, before proceeding)
-
Quasi-stellar, Airtex2019, thank you for your quick answer. Well, the fact is that I’ve flown every version of BMS, made thousend of ramp starts, and since last U2 update, everything had had the same routine. That’s why this issue surprised me a lot. I’ve never experienced something similar before…Anyway, I use the first part of throttle course, as ident (setted from the setup page), now I’ll try to unlock the ident manually, at ramp, as you both suggested. Thanks for help.
-
Cool – sorry it’s hard to tell newb from veteran sometimes. (I am far more newb than you… I just post more lol)
I think you’re right, that if you have physical throttle idle-detent configured, you shouldn’t need to hit the callback? Haven’t heard of any changes to this, but anything’s possible.
-
If you use physical analog detent U2 has overwritten the value in falcon bms.cfg you have to reenable it
from changelog and installation post of 4.35.2
CONFIG FILE: U2 does replace your existing config file
so either set manually in User/Config/falcon bms.cfg
set g_bUseAnalogIdleCutoff 1
or through configuration editor
reassure idle detent line is set in setup
Gesendet von meinem SM-G930F mit Tapatalk
-
You were right mate ;). The problem was the idle detent (alt+i as you said). Actually, what I understand is that U2 does reset config.cfg as in the first install, were I use the “idle cutoff” checked, 'cause I’ve got a physical ident onto my TQS. Thanks again, I’ve appreciated.
-
oakdesign, thank you for your help. I’ve gone throught config editor to set my personal configuration, included the idle cutoff. The cut off / idle position in setup page, has remained the same as before. Basically, not paid attention either the changelog and config file notice, it’s my fault. Lesson for the future.
-
Yes, a lot of people have been bit by the unexpected cfg file reset.
Nice catch Oak …
Does the 2D setup UI render the red idle-cutoff bar, and accept modifications, even when g_bUseAnalogIdleCutoff == 0? That’s definitely confusing…