AK_Heli

There have been a bunch of other bugs/instability issues with this installation and I've been trying to discern if this was a user/installation generated fail or if something else was going on. Still not entirely clear on why this is happening. Followed the recommended online tutorial. In the aileron axis left stick is generating a negative integer and right stick is generating a positive integer. I certainly appreciate that negative values are less than positive values (in simple math at least). The tone here is a little aggressive (read the manual! -<+ etc.) I am genuinely just trying to figure this out and not coming at it from a hobby pov. Please show a little more patience for a new user? if the interface isn't intuitive for this particular user then it isn't about assessing blame on the engineer but rather yielding utility out of payware application. The help is appreciated!

Read the user guide and attempted multiple resets. This is aberrant behavior. Let me try to better explain it. When attempting to calibrate the ailerons from left to right. At full left deflection, press set. The SAME value immediately populates into the Min column and Center column and the "set" buttons are now locked out for the center and right column irrespective of displacing the stick and the values no longer populate into either column, hence the ping.Attempted multiple resets. Upgraded to latest version this morning same behavior. Attempted with different controller, same behavior.

Running FSX on steam. Win7SP1. FSUIPC4966c. This is primarily for helicopter simulation and we want to use FSUIPC to better calibrate the cyclic and pedals (ailerons. elevator, and rudder). The y axis calibrates appropriately. The x axis will take the min (or max) initial value and then populate that into center value and lock the "set" buttons with an audible ping so no different values can be stored. Same behavior with pedals. Values register accurately in when assigning the axes in the previous step. Just fails when trying to "set" value in calibration tab. Attempted with a flight link controller set up and verified with a MS sidewinder. Same behavior. this is a little time sensitive for us. Thanks! FSUIPC4.log