Project Magenta in FSX: Missing V1/VR/Minimums/Retard callouts and wrong AP off sound

A few things to check with PM + FSX sounds

Hi D5Tweddle,

Those missing callouts (V1/VR/Minimums/Retard) and the “wrong” AP disconnect tone usually come down to one of two things: either the specific PM sound set isn’t being called, or the conditions that trigger those callouts aren’t actually being met (even though other callouts are).

1) Confirm the callouts are actually enabled/available in your PM setup
Some PM modules let you pick which callouts are active and/or which sound set is used. Since you’re already getting 80kts, gear, and radio alt callouts (100/50/30), the sound system is at least partly working — it’s just not firing the “calculated” ones (V-speeds/minimums/retard) and the Airbus-specific AP sound.

If you have a PM config utility or options page for sounds/callouts, double-check:

• Callouts/V-speeds are enabled (not just RA height callouts)
• “Airbus” sound set is selected (if there’s a choice)
• Any “co-pilot” or “FWC” style callouts are enabled (wording varies)

2) V1/VR callouts depend on V-speeds being set somewhere
The sim can’t magically guess V1/VR unless the PM side is getting V-speeds from an FMC/MCDU or wherever PM expects them.

So the practical test is:

• On a takeoff where you expect V1/VR, are V1/VR actually entered/set in the PM FMC/MCDU (or whatever you’re using to drive the Airbus)?
• Are you running the full PM Airbus stack (MCDU/FCU/etc.), or just parts of it?

If V-speeds aren’t populated in the place PM is reading from, you’ll still get the “simple” callouts (80kts, RA heights), but not V1/VR.

3) “Minimums” requires minimums to be set
Same story: the “Minimums” call isn’t purely a radio alt height callout — it usually triggers based on a decision height / minimums setting.

So check if you’ve actually set:

• BARO minimums (MDA) or RADIO minimums (DH) in whatever PM component controls it

If minimums aren’t set, you won’t get the call even though you get 100/50/30.

4) “Retard” is usually tied to Airbus mode/logic
“Retard” tends to be Airbus-specific logic (flare/land mode / autothrust state depending on model). If PM isn’t in the exact mode it expects, or you’re not running the Airbus module that generates that callout, it may never trigger.

This also ties into why you might be hearing a “Boeing” autopilot disconnect tone — it suggests you may be using a generic PM sound pack or a default wav mapping rather than the Airbus one.

5) Make sure you’re not mixing sound sources
In FSX setups, it’s easy to have callouts coming from multiple places (PM, aircraft panel, another gauge, etc.). If part of your callouts are from one source and part from another, you can wind up with “some callouts work, others don’t” and the wrong AP tone.

A quick isolation test:

• Try the same flight with a very plain/default aircraft (just for testing) and see if PM callouts change.
• Alternatively, temporarily disable any other GPWS/callout gauge in the aircraft panel you’re using (if applicable) and see if PM then provides the missing ones.

A couple questions so I can point you to the exact fix

• Which exact PM modules are you running (FCU? MCDU? external sound module? etc.) and are you flying an Airbus panel/aircraft intended for PM?
• Where are you setting V1/VR and minimums right now (in a PM MCDU, in the FSX aircraft FMC, or not at all)?
• Are the “missing” callouts missing on every flight, or only certain aircraft/panels?

Answer those and I can narrow it down to “settings issue” vs “sound set/file mapping issue” and what to change.