Configure Aerosoft Airbus callouts in FSX: enable MCDU crew and checklist audio, set approach minima, and fix missing GPWS altitude calls.
In Aerosoft Airbus for FSX or FSX: Steam Edition, configure callouts from the aircraft’s right-hand MCDU: open its options and checklist pages, enable cockpit and cabin sounds, then switch on the checklist and co-pilot functions you want. GPWS altitude calls remain automatic; approach minimums depend on the value entered on the PERF APPR page.
Which Aerosoft Airbus callouts can be configured?
Aerosoft divides its callouts between automatic aircraft warnings and optional crew, checklist and cabin audio. The normal interface does not let you select each radio-altitude call individually.
| Callout type | Where it is controlled | What triggers it |
|---|---|---|
| GPWS radio-altitude calls | Aircraft sound settings and built-in gauge logic | Descending through programmed radio heights |
| Minimum and 100 above | PERF APPR minima entry | Approaching the entered barometric or radio minimum |
| V1, rotate and crew prompts | Take-off data plus checklist or co-pilot options | The relevant speed or checklist phase |
| Checklist responses | Right MCDU checklist page | Aircraft state and completion of the preceding items |
| Cabin and flight-crew audio | Right MCDU sound or options page | Flight phase and enabled sound categories |
Airbus X, Airbus X Extended and later Aerosoft Airbus packages do not present identical menus. Treat instructions for another generation cautiously; our explanation of the differences between the Extended and Professional generations helps identify which controls belong to which product.
How do I enable Aerosoft Airbus crew and altitude callouts?
- Load the Aerosoft aircraft fully. Wait for the panel to initialise, then open the right-hand MCDU in the virtual cockpit or through its panel pop-up. Use this unit for aircraft options rather than the left MCDU used for normal flight planning.
- Open the sound options. From the right MCDU menu, find the options page and its sound or volume controls. Enable the cockpit, flight-crew and cabin categories required. Names and the use of switches or volume levels vary between releases.
- Enable checklist assistance. On the checklist page, activate the checklist function. Enable the co-pilot or pilot-monitoring option as well if you want spoken responses and automatic completion of eligible items rather than prompts alone.
- Enter take-off data. Complete the take-off performance page, including V-speeds where the package requires them. Missing speeds are a common reason for absent V1 or rotate calls even though other audio works.
- Set the approach minimum. On the PERF APPR page, enter the barometric minimum or radio decision height specified for the approach. Do not enter an MDA as a radio height merely to force a callout; BARO and RADIO minima use different references.
- Test during a normal approach. Descend through the callout heights with the aircraft powered and its radio altimeter operating. Radio-altitude calls refer to height above terrain, not indicated altitude, so they occur differently at elevated airports.
Checklist sequences are state-dependent. If the before-start or approach sequence refuses to advance, check the preceding phase, aircraft state and outstanding checklist conditions rather than repeatedly switching the sound option.
Why are Aerosoft Airbus callouts missing?
The pattern of missing audio usually reveals whether the fault is an FSX sound problem, an aircraft setting or an incomplete flight-data entry.
- Every aircraft sound is silent: check that FSX sounds are enabled, raise the relevant simulator volume categories, inspect the Windows output device and confirm that FSX is not muted in the volume mixer. Our FSX-wide audio troubleshooting checks cover these faults in order.
- Only crew or checklist voices are absent: enable both the checklist and co-pilot options. A checklist can be active without the automated spoken response function.
- Altitude calls are absent: confirm the aircraft is electrically powered and test in a normal descent rather than Slew mode or a jump directly below the trigger height. Skipping across a trigger can prevent the sound from playing.
- Minimum is absent but other altitude calls work: check the PERF APPR page. A missing minimum, or an entry in the wrong BARO or RADIO field, is the usual cause.
- Calls overlap or repeat: another GPWS gauge, crew programme or sound package is probably operating alongside Aerosoft’s system. Disable the duplicate source rather than editing the volume of both.
- The panel and callouts both fail: the Aerosoft gauges may not have loaded correctly. Restore the original panel and sound files or run the package’s repair installation instead of copying gauges from a different aircraft.
Can I customise individual Airbus altitude callouts?
Individual altitude calls are not normally selectable through the Aerosoft interface. Their triggers are part of the aircraft’s gauge logic; replacing a sound clip changes the recording, not the height or condition that activates it.
Manual sound-file or panel.cfg edits are package-specific and can be overwritten by a repair or update. Back up the complete panel and sound folders first, and do not add a generic GPWS gauge unless it is explicitly compatible with that exact Aerosoft Airbus version. Otherwise, duplicate altitude calls and broken gauge numbering are common results.
When should I use an FDC callout profile?
Use an FDC profile when you already have a compatible FDC installation and want structured crew calls, checklists and flight-phase sequencing beyond the Aerosoft aircraft’s native audio. Our Aerosoft Airbus X profile for sequenced FDC callouts is intended for the matching A320/A321 generation.
The profile is not a standalone GPWS installer and will not repair silent native altitude calls. If FDC and Aerosoft announce the same event, disable the overlapping crew category in one system while retaining the aircraft’s built-in safety and radio-altitude sounds.