Incorrect. The default 'Z' key does not work in this sim. It will screw up the plane.

 

If you look in the Aircraft.cfg the FSX autopilot is not even activated in this aircraft - it uses a full custom coded LVar based AP.

 

To set the AP with the mouse, it's left click, and to turn off the AP it is a right mouse click.

 

But far better than that - just download the LUA script for the original Airbus X from the Aerosoft website, convert it from Txt to Lua file type, and put it in the Flight Simulator X / Modules folder.

 

Then, in FSUIPC (registered version), you can select the "Lua AS_Airbus_X" command, and assign any and all of the Extended's AP commands to keys or hardware, using the "parameter numbers" in the LUA file. (It's not as complicated as it sounds) :wink:

 

I have the following commands working beautifully on the Extended :-

 

AP ON assigned to 'X' key

 

AP OFF assigned to 'Z' key

 

Heading Knob Decrease assigned to '[' key

 

Heading Knob Increase assigned to ']' key

 

Heading Push (Managed) assigned to 'N' key

 

Heading Pull (Selected) assigned to 'H' key

 

Speed Knob Decrease assigned to '<' key

 

Speed Knob Increase assigned to '>' key

 

Altitude Knob Push (Managed/Climb) assigned to 'V' key

 

Altitude Knob Pull (Selected/Open Climb) assigned to 'U' key

 

etc, etc,

 

Obviously some of the above keys are assigned to FSX default commands so I have deleted these where required, as the above are my preferred keys that I use in most aircraft.

 

Works a treat.

Mmmm..... Is there by chance, an Lua 'for dummies' book anywhere? It's very easy to say "just do...." but I'm a dummy;-)

Have to say I don't have any serious issues with the Extended. Flew quick sortie between EDDV and EDDK yesterday in complete managed mode with the checklists (LOVE that feature!) and it was great. The only issue i have is with TOD calculation. it seems to be a bit inaccurate.

 

I think the VC is also excellent and I particularly appreciate the variety of internal and external views which are offered. Overall, I'd give it 9/10 considering the amazing complexity of the systems.

 

By the way, hand flying it is a dream and so easy! I had to laugh when someone posted a message on the aerosoft forums with the pic of an error with the drawing of a STAR on the ND and he wrote underneath 'wasn't able to land'.... Right!!

By the way, hand flying it is a dream and so easy! I had to laugh when someone posted a message on the aerosoft forums with the pic of an error with the drawing of a STAR on the ND and he wrote underneath 'wasn't able to land'.... Right!!

 

I don't think the poster you mention was referring to hand flying. I recall he was referring to the automation functioning incorrectly in terms of lateral nav.

But far better than that - just download the LUA script for the original Airbus X from the Aerosoft website, convert it from Txt to Lua file type, and put it in the Flight Simulator X / Modules folder.

 

Then, in FSUIPC (registered version), you can select the "Lua AS_Airbus_X" command, and assign any and all of the Extended's AP commands to keys or hardware, using the "parameter numbers" in the LUA file. (It's not as complicated as it sounds) :wink:

 

I have the following commands working beautifully on the Extended :-

 

AP ON assigned to 'X' key

 

AP OFF assigned to 'Z' key

 

Heading Knob Decrease assigned to '[' key

 

Heading Knob Increase assigned to ']' key

 

Heading Push (Managed) assigned to 'N' key

 

Heading Pull (Selected) assigned to 'H' key

 

Speed Knob Decrease assigned to '<' key

 

Speed Knob Increase assigned to '>' key

 

Altitude Knob Push (Managed/Climb) assigned to 'V' key

 

Altitude Knob Pull (Selected/Open Climb) assigned to 'U' key

 

etc, etc,

 

Works a treat.

 

Haven't tried this yet on the Extended (Christmas present from the wife...), but I can confirm that this all works beautifully in the original bus.

 

Even better for me, is that I configure (through FSUIPC ) the joystick trigger button to disconnect the AP when it's pressed and then the A/Thr when it's released, hence, both get disconnected with a single trigger press.

 

Regards

 

Gary

On the key stuff. There's a brand new LINDA profile available for you guys. LINDA is free, the profile is free, you just need a registered FSUIPC. http://forum.avsim.n...ule-version-20/

I agree that the VC quality has to be improved. The Airbus X looked better on my system.

 

Plus, the performance could be much better. I'm down to 10% AI. LOL

 

....well this is your view but I don't agree... i find the new VC MUCH better than the previous one which was too dark, too dirty.. the new one has a better reflection of ambiant light offering a much more real contrast between different part (MCP...)

Is anyone using EZDOK and FXAA with the new Airbus Extended? I'm getting a brief white flash with FXAA on when I switch camera views in EZDOK, which is no big deal, but I'm curious if someone else is experiencing the same. I usually only engage FXAA between sunset and sunrise anyways, so I can just switch it off.

 

Another thing I've noticed is when switching camera views with EZDOK using either joystick or keyboard shortcuts, I have to hit the button/key twice to get it to switch views.

 

All in all, I love this plane and Mathjis and team have done a fabulous job. I recently flew in first class in row 1 on an Airbus A321 between Detroit and Philadelphia and was wondering if the new Airbus Extended would have the same high pitched engine whine on takeoff and climbout? The answer is YES, it's spot on and I love it :smile:

 

I don't think the poster you mention was referring to hand flying. I recall he was referring to the automation functioning incorrectly in terms of lateral nav.

 

Yes I know but if there was an error in the nav display, you just cancel managed mode and fly it as you should.. You should never (in my opinion) expect to rely totally on a computer which is prone to these glitches anyway. I personally enjoy having to intervene I these things manually its more fun

 

 

....well this is your view but I don't agree... i find the new VC MUCH better than the previous one which was too dark, too dirty.. the new one has a better reflection of ambiant light offering a much more real contrast between different part (MCP...)

 

Absolutely agree!

I can confirm that they are using a different airfile for the Neo.

Nice detail.

I agree that the VC quality has to be improved. The Airbus X looked better on my system.

 

Plus, the performance could be much better. I'm down to 10% AI. LOL

 

I have a similar FPS problem. Strange thing is it wasn't so bad yesterday, but today I was hovering around 12 FPS at UK2000 Edinburgh and then I had a CTD as a free extra! ^_^

 

And I also preferred the Airbus X VC, which to me looked sharper.

 

I'm having various other problems too, but as I said before these may be down to me not setting it up properly. It does seem to need a bit of coaxing to get into the air, even at light TOW - I've set my controls as per instructions but there seems to be an overly long lag between sidestick input and rotation. More than was apparent with Airbus X at any rate. Not sure if that's how it really is, although once airborne I do like the feel of the FBW.

They have just announced on their forums that they are hoping to release a hot fix tomorrow which will among other things correct the slow rotation problems.

 

Also, the winglet version is not supposed to be Neo. It is just the test aircraft with same old engines but with the new winglets included which I think some airlines have already ordered. They have changed some things like a bit more efficient fuel usage, but I don't think it is much of a difference.

They have just announced on their forums that they are hoping to release a hot fix tomorrow which will among other things correct the slow rotation problems.

 

Also, the winglet version is not supposed to be Neo. It is just the test aircraft with same old engines but with the new winglets included which I think some airlines have already ordered. They have changed some things like a bit more efficient fuel usage, but I don't think it is much of a difference.

 

Correct. The NEO (New Engine Option) is a new and upgraded version of the A320, which will first fly in 2015 (IIRC). In the mean time any current engine option (CEO) A320 that is built after a certain date next year can be equipped with the sharklets, either straight from the factory or in a later retrofit. A320s built before that date can't be retrofit as the internal wing structure is different.

The sharklets reduce fuel burn by a few percent which is reflected in the modified air file (according to Aerosoft statements, I don't have the extended yet). The new engines will reduce fuel burn quite a lot more and the NEO will also have some other changes, but as the NEO will not fly for another two years Aerosoft can't model it yet.

Incorrect. The default 'Z' key does not work in this sim. It will screw up the plane.

 

Interesting, because it doesn't seem to be a problem for me. I have used it for a manual landing, as well as disconecting on the runway after autolands, with no issue!

I just flew from VNKT (Katmandu) to VQPR (Paro Bhutan).. my fav route...with the proper livery (Drukair for the A320). and I had good addons for both the airports. I totally recommend this short route and the wonderful and very economical addons for both these airports from Thai Creations. ($15 each)

 

Flight plan : VNKT IGRIS (SID IGRIS) KIMTI TUMLI PRO VQPR

 

Departure Runway = 20.

 

http://www.virtualir.../DANG4/vnkt.pdf

 

I took off and hit the AP and WOW! it did the 360degeee climb out required off the SID (due to altitude needed to leave that area) very nicely.

 

I managed to use the FMC thingi pretty good ... I removed some unnecessary waypoints inserted by the SID) and the discontinuity and added the PRO VOR to the legs.

 

thence towards PARO VOR (PRO) to prepare for the visual landing on runway 33

 

http://www.dca.gov.b...VQPR_6-1_en.pdf

 

I had to manually maintain FL 170 restriction getting close to the PRO VOR. once I was 5 miles out towards PRO. I cut off AP and athr and flew myself... and once I had the airport on sight at FL160, I flew around the mountains down that valley in an "S" zigsag with full flaps and full speed brake to lose 8000 feet real fast while maintaining <150kts and I was positioned to land nicely...then I screwed it up and touched down at almost 900fpm. Ouch! I had enough runway....

 

Loved it. What a Joy ride!

 

 

 

Manny

I'm still having throttle issues and, to be honest, not really impressed with Aerosoft customer support. I have sought help with this particular one there, but still no response at all. I'll ask here too as someone may know the answer...

 

If I load the Airbus ready for takeoff on the runway and simply firewall the (hardware) throttles, without setting anything up, I only get 85% MAX. The only way to get any more power is through the F4 key. I don't believe it should be like this, but could indeed be wrong. Any help much appreciated.

 

Thanks