No “Autobrake Off” call-out, no ANF Zoom Landing

[JS2Tango]

Using version 1.0.8 I am no longer hearing the “Autobrake Off” callout, only an ECAM warning tone instead.

 

I’ve also read (haza2) that the ANF auto-open behaviour on landing has been disabled in v1.0.8 - I assume this choice was made due to possible lag on touchdown when loading the ANF for the airfield, if it has not already been loaded earlier in the flight. 
 

A suggested fix - pre-load the destination airport within the ANF in the background after importing the route into the MCDU. This will alleviate any lag on touchdown. Loading the destination airfield in the ANF at the gate prior to departure, reduces the opportunity for lag elsewhere in the flight.
 

Thanks.

[Eddie]

Hello Matt,

We're aware of the no auto brake off call out as well as the ANF as per Haza's comment. Your suggested fix is what we've been suggesting people do but with the next update we'll have a little more customizability for this. 

[JS2Tango]

1 hour ago, Eddie said:

Hello Matt,

We're aware of the no auto brake off call out as well as the ANF as per Haza's comment. Your suggested fix is what we've been suggesting people do but with the next update we'll have a little more customizability for this. 

Thanks for the information!

In that case, I’m looking forward to to v1.0.9’s release - hopefully sometime soon!

Cheers!

[Hakatree]

On 4/21/2025 at 5:42 PM, Eddie said:

Hello Matt,

We're aware of the no auto brake off call out as well as the ANF as per Haza's comment. Your suggested fix is what we've been suggesting people do but with the next update we'll have a little more customizability for this. 

Makes sense to disable it after if there was lag, when I realise this was happening I did a couple more landings with BTV configured, and after touchdown I manually set the Efis Rose to plan, and range knob to zoom, there wasn't any lag at all, so I guess the ARPT map was cached somewhere, which should be the way to fix the lag.