Problems with Slot Two (Wingman)
-
We have observed the following problem which has already reached half the pilots of our squadron.
Each time, the problem only occurred with Number Two.In TE:
The trottle cannot moved.
In 2-D all Settings working fine, in 3-D nothing happend (different HOTAS Systems and Settings).In Campaign:
JFS works fine, but the RPM needles from Engine remain on zero.
Of course, when the problem occurred, the Ground Chief recharged the JFS, but without success.
JFS had not blinked yet.In both cases (TE and Campaign) the problem persists even after re-entering the machine (3-D) and also when
other Pilots try this plane it´s remain dead.Has anyone else ever had this problem?
Greetings
Bumerang -
In 2-D all Settings working fine, in 3-D nothing happend (different HOTAS Systems and Settings).
Throttle cycled max then idle once in 3D?
JFS works fine, but the RPM needles from Engine remain on zero.
BATT switch on MAIN PWR position?
… otherwise, no idea.
Always follow checklist (or refer to it) … if not working, first ask yourself: what did I forget? => Checklists.
-
The problem persists. We have constant problems with Number Two on the first flight.
We’re flying the campaign Mantis at dawn.
Almost every multiplayer flight we have this problem.
The Throttle can only be moved between idle cutoff and idle. It doesn’t move any further forward.
As you can see the movement of the throttle from idle cutoff to idle in the 3-D pit, BMS seems to recognize the throttle axis allready.
The problem occurs with many pilots when they enter Slot 2. It seems to be a bug.
If the problem occurs, it persists. The throttle remains immobile when you re-enter.
When we handle this Jet to KI Pilot, he cannot start either.
KI startup the Jet, but leaving on Ramp.Has anyone else had the same experience?
Greetings Bumerang
-
-
Yes, quite a few times on three different machines. Check out this thread for a more detailed description:
https://www.benchmarksims.org/forum/showthread.php?36892-Help-engine-won-t-start&highlight=wake-up
and yes, in our case it’s always been the #2 wingman slot that’s been affected by this issue.
Uwe