I'll try that when I get home.  I did try all of the other override options though.

For the second time today I have been stumped by FSUIPC messing with the 777. Remove the joystick calibration for the throttle axes (click "reset" on each of them - you can first click "profile specific" to just change it for the 777), and it works like a charm even though the axes still are recognised through FSUIPC. The other FSUIPC thingy I had earlier today was that I had to reset cowl flaps (!) calibration to make most of my 777's buttons work, as they were unclickable (including the battery switch). So this time, remove calibration on throttle axes (but keep it through FSUIPC) and you should be good to go.

Had the same issue (CH Products throttle) using the FSUIPC twin jet setup, same as the NGX and FSX controls disabled.. Went into the 777 FMC/Simulation menu and changed to "Show thrust lever position" to YES and works fine now. Perhaps a coincidence.

 

Anyone else get this process to work?

Finally just had to turn on the default FSX throttle quad and set it up for the 777.  Works fine now.  Just hope is doesn't mess up other planes.

I had to re activate my FSX controls for instance to get my rudder to hold position and for my ailerons to work at all. I also had to reset my brakes function in FSUIPC. Other than that, nothing else changed in FSUIPC.

 

 

Ed Zachery!

Interesting. It sounds like you had the same issue I'm having. I have no rudder or ailerons. Throttle and elevators work fine. I have everything mapped (but not calibrated) through FSUIPC. The rudder actually twitches for some reason on the flight controls page when I move the rudder axis on my Thrustmaster Warthog throttle quadrant. Hmm

 

When you say that you had to reactivate your FSX controls, do you mean you had to put a check in "Enable Controllers"?

Hi.

 

I had exactly the same issue with my throttles (Hotas Warthog here).

 

Reading the Introduction PDF I saw that many of the issues with FSUIPC can be solved by deleting the FSUIPC.INI file and letting the program regenerate it again.

 

This did the trick for me. Problem solved.

 

 

BR,

GHNilson

This is very strange. I have the Saitek Pro Flight System and rudder pedals as well. I remember having issues with the NGX in particular with breaking. I was then told via the forums to use FSUIPC instead of FSX. I did so and never looked back. I'm even using the same configuration with the 777 and all works fine.

 

The only issue I can see is that spoilers aren't arming using the red zone button on the throttle quadrant. I have to use shift+/. I'll have a look into this later.

 

The strange thing is that some are having issues with FSUIPC and others are not.

 

Also, do we know why the introduction manual advises against calibrating controls with FSUIPC? I'll have to go and read it again to see if it's explained as it was really late at night when I first read the manual, so I can't remember.

 

Also, are they only advising not to calibrate using FSUIPC or is the advice not to use FSUIPC as input?

 

Rynardt

 

Sent from my GT-I9300 using Tapatalk 2

 

 

Hi.

 

I had exactly the same issue with my throttles (Hotas Warthog here).

 

Reading the Introduction PDF I saw that many of the issues with FSUIPC can be solved by deleting the FSUIPC.INI file and letting the program regenerate it again.

 

This did the trick for me. Problem solved.

 

 

BR,

GHNilson

I remember reading that. I was hoping to avoid having to delete the ini because I don't want to have to reconfigure all of the axis and button assignments in FSUIPC. Deleting the file deletes all of that, right?

I remember reading that. I was hoping to avoid having to delete the ini because I don't want to have to reconfigure all of the axis and button assignments in FSUIPC. Deleting the file deletes all of that, right?

 

 

That is correct. You could backup your file before you delete it. Then start configuring it step-by-step in order to check where the error is at.

I also have problems with my Saitek control after installing 777.

After trying to correct the problem without success , I deleted FSUIPC.ini.

The assigning of throttles, ailerons and elevator axis via FSUIPC and other (brakes, rudder and etc) via FSX contols did the job.

I rechecked it on 737 and also everything fine.

Same Problem here. Deleting the FSUIPC.ini and send the Throttle Axis direct to the FSX do not Fix the Problem. :mad:

Same Problem here. Deleting the FSUIPC.ini and send the Throttle Axis direct to the FSX do not Fix the Problem. :mad:

I'm at work at the moment (bah!) and still need to give this a whirl, but my understanding is that we just need to let the FSUIPC.ini rebuild , and then we can reassign the axes and throttles through FSUIPC again. In other words, I don't think it needs to go through FSX. It sounds like the rebuilding is required because the ini gets corrupted somehow.

 

By the way, my throttles are working fine through FSUIPC.

 

 

but my understanding is that we just need to let the FSUIPC.ini rebuild , and then we can reassign the axes and throttles through FSUIPC again.

I did that. The first thing that I configuered via the FSUIPC was the Throttle Axis. But it don't work.

 

 

Interesting. It sounds like you had the same issue I'm having

 

Yes exactly the same thing.  

 

 

 

When you say that you had to reactivate your FSX controls, do you mean you had to put a check in "Enable Controllers"?

 

Bang on friend.  Then it works like a charm.  I haven't gone back in to the NGX or any other aircraft but I think everything is fine.  I think enabling controllers again bypasses FSUIPC though.  Not sure.  Whatever not a huge deal.  

I think enabling controllers again bypasses FSUIPC though. Not sure. Whatever not a huge deal.

Yes, I believe it does. Perhaps I'll try it anyway. Having the HOTAS Warthog kind of complicates things though. Fingers crossed.