squid

No problem Pete, I will report to Wilco, but experiance has shown over the years that their aftersales support leaves a lot to be desired. In anycase Im just glad its working now and thanks again.

Peter, Apologies for not responding earlier, I have been away from my PC, and did not have the chance to implement your suggestions. I now have the issue fixed, and I thank you for your help and assistance. However for me the solution was slightly different (from my understanding of the instructions at least) and I post them here in order to help anyone struggling. I followed your suggestions (as I actually did in the previous post on the subject ;) ) but to no avail. Frustrated I even tried removing FSUIPC to see if that made a difference. To my surprise it did not. Even when mapped entirely through FSX I could not get a throttle response from the Wilco Airbus. So as you see for whatever reason, simply unasigning the controls from FSUIPC had no effect. However as you rightly pointed out the issue was not with FSUIPC but rather the Wilco Airbus. I played around further and found that by setting a control axis from the TQ to each individual engine I could get a response using the FSX contols menu.. That discovered I reinstalled FSUIPC and assigned the Throttle axis I wanted to use (just one control) via the Axis assignments followed by your suggested settings. It works perfectly. Why for whatever reason the Wilco Airbus ignores single throttle inputs assigned to mutiple throttles on my setup , I have no Idea. I trawled everywhere for any conflicts, nothing, perhaps just a peculiartiy with my system. In anycase for me it was the issue that had stumped me, despite trying out all your reccomendations in this post and prior. Thanks again for helping me get there, and like I say its just a heads up to others who may experiance the same problem

Thanks for the quick reply Peter. Sorry for not being specific. This version is 4.60a and I am running FSX. My throttle works with every other single aircraft I own (PMDG, Level D, Default, you name it). The issue with the Wilco Airbus as I understand it, is that it only recognises throttle input direct through FSX, and is designed to ignore any input from FSUIPC. I am struggling to make this so. I have the throttle axis assigned via FSX, but even though I have tried unasigning it in FSUIPC i still get no response. They keyboard will move the throttle just not the hardware. In addition I have tried using a MS Sidewinder Joystick as well, again, works fine with all other addons, but not the Airbus. Is there a setting I have missed (or what do I need to check to make sure that FSUIPC is not processing the throttle axis. I understand that this is an issue with a 3rd party aircraft, but I ask for advice here as apparently the fix is to make sure FSUIPC is not intercepting the input. Thanks Again.

I do hope someone can help. I have the latest registered version of FSUIPC and recently have gotten Wilcos Airbus Vol 2. No matter what I do I cannot get my SAITEK throttles to work with it. I have try setting an Ignore axis in FSUICP but it seems to to save the settings. Even when it is still checked in aircraft specific I can still see the throttle putting an imput via the joystick calibration page. Can anyone provide an idiots guide to getting the throttle axis working with this addon? Many Thanks