I would also like to fly this with my xbox 360 controller like I do with every other plane, including PMDG 777/737. Is it possible with the airbus? Always having throttle issues. Is there a way for us casual simmers to fly this using a gamepad?

Jim Are you sing FSUIPC? And are you using the Throttle Axis within FSUIPC and not the sim's Control?

 

If so I can give you my settings.

 

This is what I had to do

 

1) Remove the throttle axis from the Sim control

 

2) Maintain the two setup in ASinput.ini

 

3) in Fsuipc, Assign both the throttle to axis "Axist Throttle 1" and Axis Throttle 2"

 

4). This is very important.. in FSUIPC, the tab "joystick calibration" ( I am not home until this weekend). where you move the lever and see the number go up and down, that should be "UNSELECTED". This is non intutive. For all other aircrafts I have to "select" but for this AS Airbus I had to unselect.

 

IF this is confusing.. this weekend I can post screenshot of you still need it

I found this image in google search..this is not my setup.. I wanted to explain Item 4.

 

 

In Throttle 1 and Throttle2 you need to click on "Reset" and make it look like Thorttle 3/

Thank you so much Manny! I have been sat in the 'cockpit' of this aircraft for nearly 3 hours trying every solution I could find on the forums everywhere, not just here, and pressing RESET twice fixed the problem. Wish I'd found your solution first!

I gave up on Aerosoft and Airbus X Zero tech support from them or the Aerosoft forum in trying to address this issue. I guess since I have the 1st Airbux X release they do not want to support the product.

I gave up on Aerosoft and Airbus X Zero tech support from them or the Aerosoft forum in trying to address this issue. I guess since I have the 1st Airbux X release they do not want to support the product.

They have said so explicitly. They do not support the earlier Airbus models.

 

DJ

They have been unable to get this addressed from Day 1, I was part of the beta testers on the Joystick fix and even they could not get it figured out even during testing. It is a total lack of willing ness to work with customers to come up with a proper fix, I know I am not the only person who continued to have issues several folks who were on the joystick fix had and still have the same issues. About 6 months later I was finally able to get it to map, and then when I pixked up a new PC in March 2015 again ZERO help, and Zero support.

 

Also just for the record I have the same issue with the updated Airbus A320/321 when I won a free copy from a contest same issues same result from Aerosoft.

Just installed new machine myself. Got everything working great, all PMDG aircraft and RealAir (sad news there) worked 'out of the box' with my

dusty but (after cleaning/lubing) trusty CH yoke and saitek rudder/throttle setup.

After blitzing through a ton of OrbX airports with the 737/777 decided I would install my Airbus X for a change of scenery (bad pun sorry)

note 1: The J41 PMDG works but I dont trust the A/P in Steam edition.

note 2:The MD-11 cockpit and textures look ...well UGH in 4k resolution.

note 3: I have EU airports so the Airbus seemed a good fit..

 

Noticed A.X no longer supported. Saw new product, $20 upgrade price approx. Decided to give it a go.

December 27th decided to spend an afternoon learning and flying the bus around some airports.

 

12 noon. Started it up. 2pm had finally got the cockpit views working like every other add-on, cycling and NOT resetting. Heavy deletions in aircraft.cfg files were needed.

2:15pm after snack resumed with excitement. Flicked thru windshield/overhead/radios and pedestal with ease.

lets FSCUIPC these babies!

Flaps/Spoiler (CH yoke map) work YAY!

Throttles going backwards and doing all kinds of crazy *^&&.

Fast forward nearly 4 hours (but imagine those slow hours actually grinding by in frustration trying to get a very simple thing to happen)

6pm its DARK now in my cockpit, I just thanked Manny for getting a simple hardware axis working.

im hungry, I didnt leave the ramp, start an engine or program a CDU (FDU?)

On the bright side I managed to load the passengers and fuel! They will have to sleep in the plane though tonight Im done.

 

Its 1235 pm now. Am going to spend this afternoon seeing if I can complete a flight. 

 

Homer Simpson, of simple mind, once said "bed goes up, bed goes down, bed goes up, bed goes down."

How hard can it be really to get to the stage of "throttle goes up, throttle goes down, throttle goes up, throttle goes down"?

EVERY OTHER AIRCRAFT manages it ok!

I have had zero issues with the 1.31 version of the 'bus. Install aircraft, read tutorial, fly tutorial, fly as required. The controls work properly, the views shift properly, and the thing works as designed.

 

DJ

Having all sorts of issues getting my Jetmax 737 TQ to work, cannot believe a product would be this hard to get the throttles to configure. PMDG, Level-D, Project Airbus, Quality Wings, Wilco, ect... Never an issue.

I have had zero issues with the 1.31 version of the 'bus. Install aircraft, read tutorial, fly tutorial, fly as required. The controls work properly, the views shift properly, and the thing works as designed.

 

DJ

Read tutorial (I am OCD regarding manuals, I like to read and understand before even loading sim).

Printed out checklists.

Fly tutorial...well there are numbers missing from left of page. e.g a rather important part:

166 goes straight to 170

at end of 166 it reads if TOGA mode locked in how to disengage, then cryptically mentions "If AP mode was selected, then it will need to be reselected after climb back to normal "

(I paraphrased there)

Absolutely nowhere in the tutorial does it mention engaging AP1 during ascent in the first place, my first attempt led the bus flying off in a straight line so I reloaded and ignored the tutorial and just

followed the complete checklist instead. AP1 select ON is clearly on that checklist. 

I am using Aerosoft A318/319 Vol 6 step by step English. Is that the correct version?

Are there any other vital steps missing from the 'step by step' (such as lower landing gear, AP off on approach) that I should be aware of?

Like I said, the checklist itself seems perfect so far so will just follow that. Sorry for nitpicking!

 

Oh regarding the views shifting correctly, they sure do, my problem was that they reset each time so if I set up a custom pan/tilt/zoom they were wiped each time.

Turning views OFF corrected that for me, is it possible to leave them turned on AND not have them reset to the defaults? 

To be fair I will conclude the rest of my tutorial experience here. After my last comment on the tutorial/checklists I went back to the flight and completed everything without hitch, from climb/cruise/descent/approach/landing

and shut down. Pressing the relevant yoke button (mapped to disconnect AP in all other tubes) set me up for landing which I will need to practice as the throttles work different from the Boeings, but I got down safely.

Did not use tutorial flight plans but a completely different one from ENNO to ESSA with my own flight plan using OrbX airports and scenery. I always do tutorials this way as I find it helps me learn and understand better rather than just type in the numbers and press the buttons Im told to.

I like the co-pilot, set to me making changes myself (he calls out and I press the buttons - best way to learn). The auto-checklists are a wonderful addition. I feel this place will fill in a void in my hanger, next to the 737/777/J41s that I can fly by memory myself. I can see this being the last plane I fly before bed when I'm too tired to be button mashing on overheads!

To sum up, what Aerosoft have delivered here is a marvelous creation of inter-working systems. I think the tutorial (English version) could do with a revision, particularly regarding adherence to the checklists.

The throttle setup, subject of this thread, was a nightmare for me and I'm sure for others too. it took me some 6 hours in two sessions to get to the stage where I could actually plan a flight.

6 hours to find the info, 5 mins to implement it. Thanks again Manny!