Sometimes when I load the J41 I can only move one throttle at a time.  If I push the left handle forward (either with the mouse or with my yoke then the right won't go forward.  If I push the right handle forward, the left won't go forward.  FSUIPC says all is well.  None of my other aircraft are having any problem.  Anybody else have this problem and find a solution?

 

Thanks.

Never mind.  Seems that LINDA causes the problem when I run it's Cold & Dark script.

Gregg, just saw your post, I use Saitek throttles and FSUIPC and always apply the LUA C/D script before starting a new flight, but I have never experienced what you describe.

 

Are you sure all FSX mappings are cleared?

 

 

Are you sure all FSX mappings are cleared?

 

Yep.  Double checked.  My yoke is a CH and I have separate throttles for L and R.  All works well unless I run the script.

Sigh.  I stand corrected.  The problem happens when ANY cold and dark setup is run...either by LINDA or the FSUIPC FO.  Nuts.

have you tried pressing F1 ? that should put them in the correct position pre start.

 

 

try running your throttles with just fsx settings . I have saitek and no probs here.

Ah well. I had it in my head to give FSUIPC another try this morning but it doesn't seem so fun if you can't go through the whole thing.  I'll just save it to a new airport from the tutorial script and fly it by myself.  Thanks for trying.

Hi Gregg, 

 

sometimes after having opened and closed doors and cargo doors (Shift E 1 etc.) I experience the same issue with one throttle stuck. But simply pressing E and then '1' and '2' quickly afterwards  couples both throttle levers, ie. both react in parallel again on my Saitek. 

 

(Spooling up the respective engine is also stuck because of this in the 737NGX and LevelD'67 because of this just below N1 40%.) 

 

Does it work? 

Edited April 21, 201313 yr by 19AB67

 

sometimes after having opened and closed doors and cargo doors (Shift E 1 etc.) I experience the same issue with one throttle stuck. But simply pressing E and then '1' and '2' quickly afterwards fixes to couple both throttle levers, ie. both react in parallel again on my Saitek. 
 
(Spooling up the respective engine is also stuck because of this in the 737NGX and LevelD'67 because of this just below N1 40%.) 
 
Does it work? 

 

Double nuts...it isn't doing it today.  I don't like instability.  Grrrrrrr...  But I'll try this next time it happens.

 

 

pressing E and then '1' and '2'

 

You know, the quick sequence E, then '1', then '2'. 

With E then 1 or 2 you can decouple one throttle after an engine failure. 

You know, the quick sequence E, then '1', then '2'. 

With E then 1 or 2 you can decouple one throttle after an engine failure. 

 

I'll give it a try.  It's odd, though, right?  If I put the right lever forward the left won't go until I pull the right one back and vice-versa.  

 

EDIT:  I got it to do the weird thing again.  The E1, E2 thing didn't help. Thanks for trying.

Not E1, then E2, but E-1-2

Not E1, then E2, but E-1-2

 

Still no luck.  Also tried to map both engines to a single throttle control...nope.

 

EDIT:  I reset back to dual throttle.  I pressed F1 in the hope that it would get the throttles to where they needed to be for the start.  The engines started and, so far at least, everything is fine.  Let's see if it stays that way.

Do both move if you use the F keys ?

yes they both move to start position with F1

 

whoever is using fs2crew can download a very good user friendly flow checklist here in Avsim that will have you in the correct config at all stages of flight. I have it but dont know how I obtained it but I can attach it to email if anyone needs it just PM me

 

 

Do both move if you use the F keys ?

 

I only have F1 and F4 mapped to the throttle (I unmapped almost everything else on my keyboard).  F4 doesn't work any different than my throttle...it moves them up just a little past idle where they get 'stuck' (exactly the same as if I push both throttles on the quad forward).  F1 does seem to put them at idle, though, which, when the problem occurs, is difficult to achieve with the quad.