Great work with the Airbus !

Just out of curiosity, what was the reason for removing the audio brief? I found this to be one of the best features for FS2Crew. I saw the comments in the manual, but wanted to learn more about the decision to exclude it from this version. 

Thanks, 

I have a question about the Audio departure brief as well: I set the cruising altitude for instance in the config and the readback from Blackbox is "cruising flight level is as shown". This is for most items that I entered in the brief like speeds as well, the response is always "as shown". Also applies to the PM asking whether I am happy with my FL when reaching cruise.

23 minutes ago, nthabti79 said:

cruising flight level is as shown

Fs2Crew can't read any values in the MCDU due to the fact that no SDK is available. Thus the only option is to play a "dummy" sound which applies to all values hence "as shown".

 

 

Edited July 13, 20196 yr by 30K

1 hour ago, 30K said:

Fs2Crew can't read any values in the MCDU due to the fact that no SDK is available. Thus the only option is to play a "dummy" sound which applies to all values hence "as shown".

 

 

I know, but the values were entered in the Fs2crew Config panel, thus readable.

17 minutes ago, nthabti79 said:

were entered in the Fs2crew Config pane

Where did you enter the optimum and recc max fl in the briefing?

Regarding the speeds, to which speeds does the F/O respond "as shown"?

1 hour ago, 30K said:

Where did you enter the optimum and recc max fl in the briefing?

Regarding the speeds, to which speeds does the F/O respond "as shown"?

Sorry, my mistake, he responded to the speeds with "zero". I'll have to check the flow again and tell you exactly where he says "as shown" and I thought "I entered those values".

Hi Nizar,

You're thinking of the Progress page on the MCDU.

In real-life (or least where I did the training), you'll read off the Optimum and Recommend Max and Cruise Flight levels on the MCDU Prog page.

We can't read Rec Max and Optimum due to tech limits so we have to say "as displayed".

And this ties in with the audio brief.

The "Airbus Brief Style" in the FCOM involves basically reading the MCDU and all the numbers in it.

A very large amount of numbers are read back.

When talking normally as a real person, if you spew out a lot of numbers it can sound ok.

But we have to cut numbers up and string them together.

If you're just dealing with a couple sets of numbers, that's okay.  But given the huge amount of numbers that would need to be said to follow the Airbus briefing style, it would get grating and irritating very quickly.

That's why we didn't model an Audio brief in this version.

If we had a text to speech engine we could do it, but those still don't sound very good.

Cheers,