So, I was doing a regional flight in my JS4100 (Elmira/Corning Regl to Washington Dulles Intl) and I take off from Elmira, land in Washington, and stop for about 30 minutes. I get back to my computer, fly back to Elmira, land, park at a gate, and start my plane up about 30 minutes later.

 

This is where the problem comes in. I begin to taxi to runway 6 for takeoff, but I notice my plane is veering to the left. I check that my trims are centered and then check my Condition Levers, which are at the taxi position. Thats when I notice it's my throttles. Throttle 1 will go all the way forward and all the way into reverse, but throttle 2 can't go forward past beta range (idle), and ONLY go into reverse. Whats even weirder is that this has happened before, but again... both incidents happened right after the return leg of a flight. Any suggestions on what the problem is?

 

My regards,

Nathan3219

BTW, I assigned my throttle quadrant to FSX via FSUPIC, so I am wondering if that could have an impact on this problem I have?

I had a similar thing happen in a C182 with the rudders. I, also, was using FSUIPC. As I was coming down, I realized that I was in a 'slip', one wing low, tracking somewhat sideways down the runway. I did a little troubleshooting but not enough...mostly just recalibrating in FSUIPC. Somehow I got it cleared up...or it cleared up on its own....not sure.

 

Anyway, what I would do is turn logging on in FSUIPC and see what commands it is sending for each throttle. If they're significantly different then FSUIPC is the problem and I'd report it to them. If they're the same then it's something in FSX.

Glad someone else flies into IAD in the simulator. On VATSIM, it seems everyone is LAX, JFK, ORD and ATL (maybe some LGA and EWR).

 

As for the issue, it seems that it's a calibration issue. If you hadn't used FSUIPC, there are times where a throttle lever will get stuck on a single engine. Since you're using FSUIPC, you may want to disable FSUIPC axis processing, test it, and see how it works with it off.

Nathan,

 

Perhaps only one engine was out of its Start Lock.

Nathan,

 

Perhaps only one engine was out of its Start Lock.

That would make sense on the engine problem I was having, but both engines were out of the start lock.

 

 

Thanks for the helpful replies Greg and scandinavian13! I've run out of time to mess around with FSUPIC, but tomorrow I'll try both of your advice.

Well, it looks like a problem within either the JS4100 or FSX (most likely FSX,) so I'm just going to restart or shut off FSX when this happens, because it only happens when I do excessive hours of flying (excessive hours as in dangerous to my health, lol.)

 

Anyways, thanks for the help guys. Much appreciated for the responses.

 

My regards,

Nathan3219

So, it looks like FSUIPC is sending the properly calibrated instructions? I wonder what happens if you save your flight and then Load it right where you are? Then, if you do have to restart it, you could at least start from right where you left off by loading it (after you turn your antiskid on and set your Vr speed...J41 forgets those on restart).

I wanted to add something here about saving flights and reloading them later (my suggestion from above). I had a situation recently where I'd saved a flight and was using it to test an aircraft. At some point I put in a crosswind to try some landings and I found that the rudder was EXTREMELY weak. I tried reloading the flight, changing aircraft, recalibrating...nothing worked. I then loaded another flight plan and the rudder was fine. Then I went back to the saved flight...again, the rudder was weak! Somehow, the rudder sensitivity was saved with the flight (I double checked my control settings...rechecked calibration...everything was right and simple.) So, it seems that FSX was saving something. I ended up blasting the saved flight and recreating it.

 

So, bottom line, if you do save a flight because you're having a weird problem it's still possible that the problem will still be there if you reload.