Runway shut down
mypc last edited by
I’ve skipped much of Tutorial one (yes, I know,but I’ll come back to it as I learn the f16) and start Tutorial 2 on the Runway. I can set comms to speak to tower and get clearance to takeoff (Tower doesn’t seem to respond to a chocks call, but I don’t think they are engaged anyway). When I move the throttle over idle detente and to A/b….the engines go on…and then out and everything shuts down. Any idea what is going on?
I can’t start any tutorial or engagement that starts which is not in the air now. I think in a campaign I have, but I have learnt that need to learn properly what I’m doing, not start a campaign!
I’m using a warthog and mud/s profile.
Tofu88 last edited by
Sounds like you may have the throttle cutoff mapped at the wrong end?
Go the the controller setting page and check the AB position then throttle cutoff position. From memory I believe it’s right click off the mouse on the throttle slider graph thing.
Frederf last edited by
Perhaps the fuel switch is not in the correct position and the delivery rate is insufficient for AB?
There are no chocks on runway or taxi start. You’d see the red text in the corner of the screen saying Chocks In if they are in. Any mission which starts on the runway should not require an engine start. Before committing to anything but a T-20:00 ramp start place your joystick switches and axes in a position appropriate for ground taxi. If you commit after T-20:00 but before T-taxi or commit later than engine start but with your throttle to off there is no guarantee that anything will work correctly.
I had a look at Mud’s .tmc script and it doesn’t use the cutoff range at all. It just presses L_ALT+‘i’ for you. As such it isn’t as functionally robust as using a script which actually maps the axis output differently when in off position as idle (e.g. mine). So BMS only knows that ALT-i is pressed when the idle button is released or pressed and of course this can cause unexpected behavior.
MapKey(&Throttle, IDLELOFF, CHAIN(D(1000), PULSE+L_ALT+USB[0x0C])); //Idle Detent ** USB I ** MapKey(&Throttle, IDLELON, PULSE+L_ALT+USB[0x0C]); //Idle Detent ** USB I **
SetCustomCurve(&Throttle, THR_LEFT, LIST(0,4, 65,90, 75,90, 100,100)); MapKey (&Throttle, IDLELON, EXEC("TrimDXAxis(DX_THROTTLE_AXIS, 82);")); MapKeyR (&Throttle, IDLELON, EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(0));"));
Long story short this is a case of “doctor it hurts when I do this.” With either script you must set the throttle to idle before committing taxi or takeoff or you will have an engine shutoff immediately (in my script) or when you come off the button (Mud’s script). That is a change of behavior that the user must take responsibility for. On the other hand my script will handle the situation of committing ramp with the throttle not in off position well provided you fix it before engine start. Mud’s script will forever have the two positions mixed up unless you manually fix it by clicking the idle detent or pressing ALT-i.
My recommend is to alter the script such that the axis output reads 4% at minimum axis position (idle) and 0% with the button pressed (off), enable the idle cutoff checkbox in the BMS launcher configurator, and then set the red bar for cutoff with a right click on the SET AB button in options when the axis output is 4%. You have an expensive controller with powerful scripting capability. The programmed axis solution is the most robust method.