Question on Paid FSUIPC

[bobsk8]

I just got the paid version of FSuipc yesterday and have a question.  II tried for hours to program the axis settings in P3D on my Majestic Q400, and each time I had a problem. I watched the tutorial videos and read a couple of manuals, that included disabling the joystick assignments in P3D, but still had erratic results  when finished. The only  reason I wanted to do this axis editing  was to use the slope function on the joystick to tone down the responsiveness for the elevator and ailerons in the center region. I finally discovered, that if I left the control settings for each axis assigned as normal in P3D, and just calibrated the Joystick using FSuipc, including setting the slope for those 2 joystick functions, it seems to work properly when flying the aircraft. My question is, is this an acceptable way to use FSuipc to get the outcome that I am trying to achieve? 

[Pete Dowson]

I just got the paid version of FSuipc yesterday and have a question.  II tried for hours to program the axis settings in P3D on my Majestic Q400, and each time I had a problem. I watched the tutorial videos and read a couple of manuals, that included disabling the joystick assignments in P3D, but still had erratic results  when finished. The only  reason I wanted to do this axis editing  was to use the slope function on the joystick to tone down the responsiveness for the elevator and ailerons in the center region. I finally discovered, that if I left the control settings for each axis assigned as normal in P3D, and just calibrated the Joystick using FSuipc, including setting the slope for those 2 joystick functions, it seems to work properly when flying the aircraft. My question is, is this an acceptable way to use FSuipc to get the outcome that I am trying to achieve? 

 

I don't actually publish a "tutorial", only the User guide and the reference Advanced Users guides.

 

FSUIPC's calibration facilities can be used no matter where you assign the axes, FS or FSUIPC. The facilities for assigning in FSUIPC were added later, a long time after the calibration, for the main purpose of allowing different assignments for different aircraft -- eg stick for Airbus or military, Cyclic etc for Helo, and yoke for other airliners and GA.

 

If you had erratic behaviour when assigning in FSUIPC compared to assigning in FS there MUST have been some sort of conflict. Probably you didn't actually disable the controllers in P3D -- merely unassigning the individual assignments is not usually sufficient, and can get wiped out on the next reload.

 

There are some aircraft which don't like assigning in FSUIPC to anything other than the normal FS controls ("axis .... set"), mainly because they need to see these controls. So assigning "direct" in FSUIPC (generally the most efficient way) doesn't work with those. However, usually, if that is the case, calibrating in FSUIPC doesn't work either as such aircraft are effectively bypassing whatever FSUIPC is doing. If you can calibrate okay in FSUIPC with your aircraft then the problem with assignment would definitely be some conflicting assignment.

 

Pete

[bobsk8]

Thanks.... BTW I think there is some different programming on the Majestic Q400 that is not typical in FSX and P3D, for instance the throttle when set to full, only goes to a green line in the engine control which is around 70%. When I changed the axis in FSUIPC I got some overspeed of the engine and an indication on the engine panel of 130% throttle, and when I  went back to assigning the throttle in P3D, the overspeed instantly went away. Apparently that is at least one function that is controlled by the aircraft.