Altitude call out too late

[bisinchi]

Mod Version

Master

{ "built": "2020-11-24T08:08:38+00:00", "ref": "refs/heads/master", "sha": "b570de8c53cd5b52a21c81f8120bfa57d8c53830", "actor": "wpine215", "event_name": "push" }

Describe the bug Altitude callout (500 hundred, 400 hundred, 300 hundred, etc seem a bit late.

Altitude callout (500 hundred, 400 hundred, 300 hundred, etc seem a bit late. The audio seem triggered when the associated altitude is reached, whereas I believe that the audio should be completed at altitude crossing,

To Reproduce execute a normal landing

execute a normal landing and pay attention to altitude callouts. Practising circuits with latest master build, I encountered this. Not sure though if this was the case in previous master or release. 1. 2. 3. **Expected behavior**

audio should be completed at altitude crossing Actual behavior

audio start at altitude crossing, meaning when the sentence is finished, the aircraft is actually below that altitude References

Additional context

Was this working before/when did the issue start occurring?

Is this a problem in the vanilla unmodded game? Not sure.

Discord username (if different from GitHub):

BY REMOVING THIS LINE, I ATTEST THAT I HAVE FOLLOWED THE ISSUE TEMPLATE AND PROVIDED A TITLE, as well as searched for other possible duplicate issues. I acknowledge if this line is not removed and/or the issue template is not respected, my issue will be closed without warning

[Benjozork]

Please add a title and provide references for the behaviour you think is accurate.

[ntlgr]

The OP seems to be right. I have checked multiple videos on YT detailing the PFD on approach and it's always the case. Example: https://youtu.be/bjGT9aJU6jo

[lukecologne]

Documents say the callouts start a bit higher than the altitude you would expect, for example the 100 callout starts at 110 feet, or 50 feet starts a 53 feet.

[bisinchi]

Please add a title and provide references for the behaviour you think is accurate.

Sorry, I missed out on that, it's corrected.

[Benjozork]

Still no references.

[bisinchi]

Still no references. I'm trying to find documents that reference the callout issue. I think it is described in the FCOM of the aircraft, if anyone has access to it (Navigation/radio altimeter section).

[krangerich]

There seems to be no exact description in the FCOM. Here the corresponding part:

The phrase "in the detection zone" might be just a slight indication, that the callout starts before reaching the height

[bisinchi]

Yes, saw that too, was hoping to see more details in the FCOM. Seems like we need to have FWC spec to get the logics for triggering the sounds.

[AirbusA320Pro]

The OP is correct. IRL the Airbus needs to have completed saying to the word/phrase at or before the exact height. The reason for this, as it relates to decision making. If at the exact minimum decision height (DH) the audio only starts to speak, then the aircraft will be well below the intended height before a decision can be made.

[A320PHX]

Related to the altitude callouts, is anyone experiencing every altitude being called out at least twice in a row?

[wpine215]

Related to the altitude callouts, is anyone experiencing every altitude being called out at least twice in a row?

Yes, I've had that issue as well. Probably warrants its own separate github issue if one doesn't already exist for it

[bisinchi]

I have the double callout issue on master downloaded on 1st December. I think this should be a separate issue to this one.

[derl30n]

cc @hotshotp can you address this?

[hotshotp]

cc @hotshotp can you address this?

No, it's all asobo logic for the call-outs and someone else will need to code them

[beheh]

While I can't share the exact reference, I'm aware of the following numbers:

• 2530ft => "Two Thousand Five Hundred"
• 2020ft => "Two Thousand"
• 1020ft => "One Thousand"
• 513ft => "Five Hundred"
• 410ft => "Four Hundred"
• 310ft => "Three Hundred"
• 210ft => "Two Hundred"
• 110ft => "One Hundred"
• 53ft => "Fifty"
• 42ft => "Forty"
• 32ft => "Thirty"
• 22ft => "Twenty"
• 12ft => "Ten"
• 6ft => "Five"

In future the reworked FWC will implement this correctly, but for now we can probably still fix the old system if we want.

[2hwk]

I have a feeling this old issue is already addressed, if so then this can be closed.

[beheh]

@2hwk No, it's not. Our GPWS class still checks for the round altitudes, where it should be checking for the earlier ones I mentioned in an earlier comment. This will eventually be implemented by the new FWC, but somebody could take those numbers and plug it into the old GPWS class to get the correct behavior even without the new FWC.