Problem calibrating Throttle Quadrant in FSUIPC

[simx]

Hello Pete

I have a problem with calibrating in fsuipc I thought I would share with you. When I press rescan and move the lever the in/out values goes directly from 0 to 16383, which basically means there is nothing between idle and full thrust. So I wonder if you know anything about this and how it may be solved, havent found any similar questions online but I cant be the first one having this problem? I use the left lever for throttle and the other two for flaps and spoilers. When I have moved the lever all the way up and then back, the assigned lever in fsx (e.g the thrust lever) wont go back, but stays there, which can be a problematic during taxi and landing. The saitek pro flight system is brand new and works properly så it has to be something between fsx and fsuipc that dont want to co-operate. I have also tried disabling controls in fsx, without success. 
Best Regards 

Simon

[Pete Dowson]

I have a problem with calibrating in fsuipc I thought I would share with you. When I press rescan and move the lever the in/out values goes directly from 0 to 16383, which basically means there is nothing between idle and full thrust. So I wonder if you know anything about this and how it may be solved, havent found any similar questions online but I cant be the first one having this problem? I use the left lever for throttle and the other two for flaps and spoilers. When I have moved the lever all the way up and then back, the assigned lever in fsx (e.g the thrust lever) wont go back, but stays there, which can be a problematic during taxi and landing. The saitek pro flight system is brand new and works properly så it has to be something between fsx and fsuipc that dont want to co-operate. I have also tried disabling controls in fsx, without success. 

 

Actually it is a commonly reported problem specifically with the Saitek quadrant, and is caused by a bad setting in the Registry which defines some axes as "digital" (meaning "on or off").

 

I would have though Saitek would have fixed their install package by now. I don't recall the specific details, but you'll certainly find the answers somewhere over in the Saitek support forum.

 

Pete

[simx]

Actually it is a commonly reported problem specifically with the Saitek quadrant, and is caused by a bad setting in the Registry which defines some axes as "digital" (meaning "on or off").

 

I would have though Saitek would have fixed their install package by now. I don't recall the specific details, but you'll certainly find the answers somewhere over in the Saitek support forum.

 

Pete

Okay thank you, I will see what they can come up with. 

 

Simon