FAQ Latest Topics

Thrustmaster T-Flight Hotas X Joystick

Fri, 23 Dec 2016 11:28:27 +0000

Hi all,

Is the Thrustmaster T-Flight Hotas X Joystic compatible with Aerosofts airbus a320/a321?

CTD A320

Sat, 16 Apr 2016 13:19:18 +0000

Bought and installed the A320 Extended today on Prepar3d v3. Trying to learn the FMC and keep getting CTDs during programming. Should I have the latest version since I bought today or am I missing some updates?

FLT CTRL, ELAC, and SEC switches don't work

Wed, 04 Nov 2015 01:47:26 +0000

So, on Sunday I put up a post named "Landing Speeds." It explained how my plane floated on approach, I found a bit of a solution to that, but don't stop reading. I am using Airbus X Extended A320/A321, and the issue to my flotation issues on landing is this... It seems that the plane is almost flying itself, so I wanted to disable all manual flight control by disabling the ELAC, FLT CTRL, and SEC's switches, but they don't disable when I right or left click on them; they seem to be in-operable. Saddest part here was that in this YouTube link: http://youtu.be/6Mt_XJtTX9Y this Airbus X user seemed to have full control of all of these switches (ge was using the A320)! I really love this product and all I want is to not have to do a go-around every time I try to land this plane. I also don't want to switch back to freeware because I hate those. This isn't a matter of I don't know how to fly- because I do and it's this plane that I love the most- but have the most issues landing with. It's a matter of manual control. Please help me with these switches, i'll run it by one more time: these switches appear to be in-opeable: FLT CTRL, ELAC, and SEC switches. Is there any possible way to make them operable? It would mean the world for any help I can get here! Many thanks now, and in advance! Email me here for any specific questions you may have about my topic: [removed] thanks!

simbrief flight plans

Sat, 14 Nov 2015 05:24:24 +0000

I have installed Airbus x extended on my F drive along with P3Dv3

However when I generate a flightplan using Simbrief I cannot establish in which folder the flightplan should be saved.

Could you advise me which folder is designated for this purpose.

Landing Speed

Mon, 02 Nov 2015 01:48:21 +0000

Hi Aerosoft team,

I recently purchased Airbus X and I love it. There is on flaw that I can't seem to fix for the life of me, though. I have been using the 757 lately, simple ILS landings and approaches, now that is all just as easy on the A320, it's just the speed that irks me. I've made sure that my trim is in the optimal position for landing, I maintain around 130kts on final, but my plane will literally float unless I am under 120kts. If I try to flare the plane at 125kts, and I float- the plane will literally not land at all unless it's under 120kts. I've watched videos of people using the same Airbus A320, and gently landing on the runway at 140kts. I am very experienced with the A320 and this issue is making me more or less annoyed because other people are landing this plane perfectly at a much higher speeds, and I can't even land unless I basically stall the plane. Can't seem to find any fix to this. Answers? Thanks so much. Email me here, please: nicksandro32@gmail.com

Cruising Speed

Sun, 04 Oct 2015 23:14:01 +0000

My Airbus X Extended is not cruising more than 300 knots, is this normal?. I was expecting around 440 knots or above. What do I need to do to fly faster?

I could not find this topic in FAQ, so I decided to post a new topic

Cruising Speed

Sun, 04 Oct 2015 03:38:37 +0000

My Airbus X Extended is not flying more than 300 Knots?, please advice

Kind Regards

Tharanga

CTD Errors

Mon, 11 Nov 2013 01:45:34 +0000

Please make sure you have:

- The latest C++ 2008, 2010 redistributable

- FSX SP2

- Using Stock NavData or any navdata later than 1310

- Admin Access

- 1.16 with hotfix or any other later version of the Airbus.

ND Brightness Knob and TERR ON ND Button

Tue, 24 Sep 2013 16:08:12 +0000

As you may have noticed, the TERR ON ND button is clickable and the ND brightness knobs are split into two.

The reason for this is to standardize the VC models within our internal builds, but no, you wont get TERR ON ND yet. The ND brightness knob is like its real counterpart, split into two, one for the ND main brightness and the other for TERR/WX.

Attention all CORTE Program Developers

Mon, 10 Jun 2013 10:41:57 +0000

There is a format change to the CORTE format to include support for DCT without destroying compatibility with existing flight plans. The format change has been introduced in V1.15.

Example CoRoute:

[CoRte]
ArptDep=EDDF
ArptArr=LOWW
Airway1=UZ650
Airway1FROM=SULUS
Airway1TO=VEMUT
DctWpt2=BUDEX
DctWpt2Coordinates=
Airway3=UZ205
Airway3FROM=BUDEX
Airway3TO=VENEN
DctWpt4=TULSI
DctWpt4Coordinates=47.20161,11.28876

DctWptX=WPTNAME
DctWptXCoordinates=lat,lon (coordinates)

Empty Coordinates field will select the nearest way point with the same name.

X indicates the sequence in the FPLN. Please place them with the correct numbering in order for the right sequence to be there.

The remaining fields remain the same with existing CORTE format.

New/Requested Features and Policy towards it.

Tue, 23 Apr 2013 11:16:51 +0000

Just not too long ago, there have been several threads made for requesting new features. You are more than welcome to create feature request threads. but please don't do it excessively.

All Feature requests are evaluated by something I call Feature Value vs Time spent ratio. If the ratio show that time spent is not worth it, it wont be done. If your feature request is really noteworthy/truly innovative/beneficial, trust me, I would definitely deliver that feature, but If I don't there is always a reason why.

Also, please do search before posting for such features. If you posted about a feature that has been answered before, do not be surprised if you post is down voted by others.

Classification of bug importance

Wed, 13 Feb 2013 06:42:15 +0000

There seem to be people who disagree on how we classify bugs. Heres how and here why.

High Importance:

Critical to flight. Usually things like LNAV misbehaving or SID/STAR way points drawn/inserted wrongly.

Mid Importance:

Important/Critical to flight but can be workaround using other functions/features.

Low Importance:

Non essential to flight. Minor system faults like callouts repeatedly going off wrongly.

Note that this is about bugs, and not new features.

I think there's a bug, but the developers don't believe so!!!!!!!

Wed, 13 Feb 2013 06:35:21 +0000

If you are really sure there's a bug, be sure to provide evidence that its a bug.

Note, that when I say evidence, I mean real world evidence (be it in the form of videos or pictures) that that doesn't/do happen in real life. If there's really a bug and its clear from the evidence, we will change it as soon as we can.

However, if you insist that things are buggy without any proof and using pilot friends as your testifier who never post on here, it wont work.

Configuration files

Thu, 24 Jan 2013 15:09:40 +0000

You will find the configuration files in the C:\users\YourName\Documents\Aerosoft\AerosoftAirbusExtended folder.

The shown values are the default values, where there is not explanation the data should not be changed.

NavData.ini

[NavData]

useNavDataPro=1 (set this to 0 if you want to use NaviGraph data)

pathNavDataPro=NavdataPro\NavData\ (the path to the NavDataPro folder, all paths are relative from FSX main folder)

pathNavigraph=Navigraph\NavData\ (the path to the Navigraph folder, all paths are relative from FSX main folder!)

AB_ND_GDI.ini

[ND]

maxAmountDisplayedAirports=150 (limitation of simultaneous displayed symbols due to performance)

maxAmountDisplayedNDBs=150 (limitation of simultaneous displayed symbols due to performance)

maxAmountDisplayedVORDMEs=150 (limitation of simultaneous displayed symbols due to performance)

maxAmountDisplayedWaypoints=150 (limitation of simultaneous displayed symbols due to performance)

[Print]

useDefaultPrinter=1 (1 uses default printer, 0 opens printer selection dialog before performance sheet print)

FMGS.ini

Logging=0 (set to 1 for debugging purposes)

HTML_Interface=1 (1 to activate web server, 0 to deactivate webserver)

BigScreenMCDU=1 (1 for big web MCDU (tablets), 0 for smaller web MCDU (phones))

TODFromXML=1

TOCFromXML=1

[CoRte]

FullRoute=0 (0 = airport+airways, 1 = airport+runway+sid+airwars+star+runway+airport saves in flightplan)

AsInput.ini

[Common]

Logging=0 (set to 1 for debugging purposes)

NullZone=0

[FlightControls]

Enable=1

[FADEC]

InvertAxes=1 (set to 0 when your throttle works inverted)

AxesCount=1 (one throttle, add // in front when you got two throttle channels)

Event1=AXIS_THROTTLE_SET (one throttle, add // in front when you got two throttle channels)

//AxesCount=2 (two throttles, remove // when you got two throttle channels)

//Event1=AXIS_THROTTLE1_SET (two throttles, remove // when you got two throttle channels)

//Event2=AXIS_THROTTLE2_SET (two throttles, remove // when you got two throttle channels)

FBW.ini

[FBW]

Logging=0 (set to 1 for debugging purposes)

EnableFMGS_Interface=1

AirbusXConnectExtended.ini

[Common]

Logging=0 (set to 1 for debugging purposes)

DataRequestPeriod=10

[Payload]

AircraftTitleCheckingEnabled=1

ExitAfterLoading=0

[server]

Enabled=1

Port=4040 (Post used in internal HTTP server. Default value: 4040)

If your Arrival/Departure transition is missing...

Mon, 14 Jan 2013 05:26:43 +0000

Well, scroll up.

My TOGA N1 is too Low!

Fri, 21 Dec 2012 03:06:46 +0000

A lot of users are falsely reporting the N1 is too low. The truth is that the N1 is accurate and completely follows the charts from the FCOMs.

The rated N1 is affected by this three factors,

Pressure Altitude
OAT - Outside Air Temperature
Airspeed of the aircraft

On a Cold day, with a low Pressure altitude, a TOGA N1 can be as low as 85.1%.

On a hot day, with high pressure altitude, a TOGA N1 can be as high as 91.2%.

So, do not be alarmed if you see such low N1, if you think you cant make if off that runway, check your payload/fuel and Flap setting.

Strange light effect

Tue, 25 Dec 2012 15:19:34 +0000

If you see this:

It is almost certainly caused by the flight loaded in slew mode. We do not think we can change this.

T.O. INHIBIT showing at take-off

Mon, 03 Dec 2012 14:39:20 +0000

The purple T.O. INHIBIT that shows on the ECAM on take-off might surprise you, but it is normal when you do a FLEX or TOGA take-off . One of those quirky Airbus things.

Spoiler (and spoiler animation)

Tue, 23 Oct 2012 10:38:15 +0000

The default behavior of FSX is a binary one where spoilers (speedbrakes) can only be fully extended or fully retracted. This means that when the spoilers are extended in flight and you press the [/] key to retract them, they will first fully extend and then retract. This is unavoidable FSX behavior that is very hard to avoid.

The best way to use the spoilers is to link them to an unused channel on your control unit (I used the little slider on the X52 Throttle) or to use lever in the VC. If you use the [/] key command you will have to live with this minor inconvenience.

Autobrake issues

Tue, 11 Dec 2012 09:29:46 +0000

If the autobrakes do not engage or autobrakes do not disengage when stepping on rudder pedals (with brake axis assigned) , check the calibration of rudder pedals, make sure that null zone is minimal and senstivity is full.

If after the above steps fail, gather this log ASINPUT.log in the following situations

1. Toe Brakes set in FSX and freshly calibrated and used in taxi and NO autobrake

2. Toe Brakes not stepped/not used totally and NO autobrake.

After each situation, reload aircraft. Remember to gather the logs before reloading, as it reloads flush the old logs out.

Can't get to INIT B (or also known as INIT 2)

Wed, 05 Dec 2012 09:29:16 +0000

That's probably because it is only available when the engines are off!

F9, F10, F11, F12 key assigment

Fri, 26 Oct 2012 10:40:29 +0000

The standard view commands of FSX are slightly altered when you run the Airbus X. If you prefer the standard assignment you need to edit the aircraft.cfg. Those views were already part of the Airbus X. To “delete” those F9 to F12 views, the aircraft.cfg has to be changed e.g. just delete the lines “Hotkeyselect” = 1 to 4 in CAMERADEFINITION.000 - CAMERADEFINITION.003 - CAMERADEFINITION.004 – and CAMERADEFINITION.005.

Airbus X Extended with GSX

Fri, 12 Oct 2012 15:35:17 +0000

Beta tester Chris Done has configured a set of files so that Airbus X Extended will interface with GSX. For GSX users, simply drop the folders in the above Zip file into the following location: C:\Users\\AppData\Roaming\Virtuali\Airplanes

The following door keyboard combinations can be used:

Shift+E followed by 1 = Front Left Door
Shift+E followed by 2 = Aft Left Door
Shift+E followed by 3 = Front Cargo Door
Shift+E followed by 4 = Aft Cargo Door

Airbus X Extended - GSX Configs.zip

2D panels included

Mon, 01 Oct 2012 12:36:50 +0000

We only have 2D panel for the MCDU because we feel that 2D panels are more or less outdated and can be replaced by VC views. 2D panels can never have the correct shading and colors (as the light changes) and almost always have an unrealistic straight on view. We do have an extensive view system that has dozens of different panels. All of these panels can be undocked so you can move them to other locations or other screens.

http://www.youtube.com/watch?feature=player_embedded&v=RNC2S92qzz4

Overspeed

Wed, 26 Sep 2012 10:50:02 +0000

If you see overspeed where you do not expect it, check the weather. Many 3rd party weather tools make very harsh layers and this can cause problems like these. Some weather tools have smoothing options or you can use FSUIPC to smooth the layers for you.