I regret having to join the group of users having problems with FSUIPC and the Airbus X Extended. But here I am. I've already taken this issue up with Aerosoft tech support, and have been told rather firmly that it's not something they're able or willing to address. So I'll take it up here.
The issue is this: I've followed the instructions on their forums for setting up controls under FSUIPC. All of the controls work properly with one exception - the throttle axes are inverted. When I try to un-invert them using the Aerosoft Airbus configuration tool (by de-selecting "invert axes"), the throttle problem is cured - but all of the other axes are inverted as well (e.g. a full left aileron command deflects the ailerons to the left, and so on).
Under any other circumstances, I'd go into FSUIPC and check the "reverse" box in the calibration pages for the two throttles. But Aerosoft's FADEC module is unable to read FSUIPC calibration - if I try, the axes become unreadable altogether. I've asked them whether there's a way to address a single axis (or in this case a pair of axes) inside their module. Their reply is that the problem is with FSUIPC, not with their software, and they're not going to take any action to address my issue.
My FSUIPC setup works with all my other aircraft, and with a suite of control devices including a PFC yoke and throttle quadrant, a Thurstmaster Warthog HOTAS (I was trying to use its joystick as an Airbus sidestick), Saitek pedals (soon to be replaced with PFC) and a custom set of helicopter controls.
I do recall one similar issue with a different Aerosoft product - the 4X Katana. In that case, the prop lever was inverted, and I was unable to set it up to use the prop governor. But in that case, I was able to use the Katana's configuration routine to define the axes as a normal one without the governor, and that allowed me to use it, but without the governor function.
I've also found that A2A's configuration utility can't read FSUIPC inputs, but most of those can be replicated within FSUIPC, so it's not an issue.
This is the first time I've run across an aircraft with a critical control that won't respond to FSUIPC calibrations.
I'm open to anything you can suggest about my setup.
For the record: I'm running FSX with Acceleration on a W7 PC, i7-3770K overclocked to 4.8 gHz on a custom water cooling loop, 16 megs of DDR3 2400 RAM, and a GTX 680 card, also water-cooled. I'd be glad to provide further specs as needed.
Thanks in advance for your help.