July 22, 20241 yr I recently updated to the latest version (4.30 b12) and I am now having difficulties with a setup that I've had forever. I have the throttle and the reverser on the same axis, having defined the ranges of the axes separately, so that the input ranges don't overlap. This has worked flawlessly across almost all of my aircraft (in MSFS), but now seems to be having difficulties. It seems that the Axis assignment that is higher up in the order of Assigned Axes takes priority and only that input gets sent to the simulator, regardless of the range that the controller is in. In the example below, the reverser ranges get transmitted to the simulator, but the regular throttle range doesn't appear to get transmitted, presumably because the 0 value of the reverser is being transmitted at the same time and takes precedence in AAO? Again, this is a setup that used to work fine, but now doesn't seem to and I haven't changed anything in my set up. If I assign the reversers to the non-default control layer, then the throttles work, but as soon as I put both sets of controls on the same layer, the throttles don't work.
July 22, 20241 yr Commercial Member This is strange. That was a bug that has been reported for an early build of the 4.40, but not this version. I suggest that you send me an email to the support address with your proof of purchase. I will then provide my current development build of the 4.40 where this has been fixed. The address is on the last page of the manual. LORBY-SI
Create an account or sign in to comment