Pilots Callouts

JetNoise

Hello,

2024SU1, F28 V2, not getting the pilots callouts. In EFB its selected. I am getting the other crew callouts, though ...
I am propably missing something ...
Nevertheless, great update and THANK YOU so much for the 2024 version !!
Oliver

Mark

The co-pilot callouts each have several conditions that must be met in order for them to trigger. We'll list what triggers each callout during each phase of flight below:

Take-off phase:

Aircraft is on the ground
Throttle levers set to greater than 40%
Strobe lights switched on
Landing lights switched on

"Thrust set" - throttles in detent position or thrust indicator at 100%
"80 knots" - ASI reading 80 KIAS or greater
"Rotate" - ASI reading VR speed or greater (as shown on speeds card)
"Positive rate of climb, gear up" - Above 50ft AGL, vertical speed greater than 500ft/min, gear down

Climb phase:

Gear up
Above 50ft AGL
Vertical speed greater than 500ft/min

"Flap 11" - Above 600ft AGL, flaps set to greater than 11 degrees
"Flaps up" - Above 800ft AGL, flaps set to greater than 0 degrees, ASI reading greater than VFTO speed (as shown on speeds card)
"Set climb power" - Above 1000ft AGL, flaps up, ASI reading greater than VFTO speed (as shown on speeds card)

Approach phase:

ASI reading less than 250 KIAS
Less than 6000ft AGL
Vertical speed less than -500ft/min
Or BEAM mode engaged and localiser captured
Or GLIDE mode engaged and glideslope captured

"Course bar active" - localiser alive, course bar moving
"Localiser" - localiser captured
"Glideslope" - glideslope captured
"Speed" - ASI reading less than VREF - 5 KIAS and above 150ft AGL
"100 feet to minimums" - 100ft above radio altimeter bug height
"Minimums" - At radio altimeter bug height
"Flaps 11" - Less than 3000ft AGL, ASI reading less than 190 KIAS, flaps set to less than 11 degrees
"Flaps 25" - Less than 2000ft AGL, ASI reading less than 160 KIAS, flaps set to less than 25 degrees
"Flaps 42" - Less than 1500ft AGL, ASI reading less than 150 KIAS, flaps set to less than 42 degrees
"Gear down" - Less than 2500ft AGL, ASI reading less than 170 KIAS, gear not down

Hope that helps.

Mark - Just Flight

JetNoise

@Mark Wow, thats a quick and comprehensive reply !

Mark, for the takeoff phase, i have everything set like said above.
(own this aircraft from day 2 ;-) (MS2020)
I'll check again next flight and report back.
Strange thing, that i am getting NO pilot callouts at all ...
Let me go through my settings once more ...

I don't seem to miss any other sounds except the pilots
callouts
Blue Skies
Oliver

JetNoise

Landing lights: Is it Landing AND Flare out lights ?
This could be it, maybe ....

Martyn

@JetNoise Any one of the three landing lights being switched on should be enough to trigger the takeoff phase - left, right or flare.

JetNoise

@Martyn Then something is bugged somewhere ;-)

I've used the Landing lights with and without the flare lights ...

Will be on approach soon, lets see how it goes this time ...

Oliver

JetNoise

Good morning, @Martyn
de-installed the product, clean (wasm), re-installed. - Fresh start of MSFS24.
C&D and startup per procedure and CL.
Getting all the calls incl "cabin ready"
No Callouts during roll / climb etc. So i assume i will not get the approach calls later on, too ...

Went through all my settings.
I am using the Garuda 3000er livery (for now), GSX, no OTHER tools or mods

Cheers
Oliver

Gluxi

Is VHF1 select?

JetNoise

@Gluxi
I am pretty sure it was. (havn't touched it) but i will tripple check next flight ...
Oliver

Gluxi

Thats was happen to me. i selected PA, and i don't hear any callouts from the Pilots. Next flight, i selected VHF1 back and so the Callouts were hearable.

JetNoise

Thanks for the info, but haven't touched the selectors at all. i am loading into the sim for another trial now..

Fab10

Three flights with the F28 V2.0 for me but none featured any P2 calls, which in turn prompted me to check the JF forum to find this post.
I'm quite confident that all take-off conditions were met but equally happy to learn if not.
Cabin crew calls were functional though.

JetNoise

I am still ruling out a user error, but...
So far i got my callouts back.
I had a old livery installed, but not used (loaded)
It showed up in msfs as a variant of the 3000 and 1000
While i was using the Garuda livery the whole time, it must have had a negative effect.
Deleted that and calls are back. Tested from C&D, Turnaround, and spawn on runway ...
Hope that helps ...

JetNoise

Will do another flight this afternoon and report back ..

brennan

I'd suggest ensuring that you trigger the "Crew take seats for take-off" call from the EFB menu as you approach the runway. I seem to recall in the 146 that if I didn't do that I wouldn't get the co-pilot calls.

JetNoise

I triggered them from the Overhead ( Crew Call ).
EXCEPT from latest tests, I used the EFB...
...

AND its not a"trigger" as per list and tested (now) ...

JetNoise

99.9 % i can call this issue as "solved" @Martyn
To blame is an outdated livery. ( Note: Livery was NOT used during the flights, just was present in Community and loaded as a "variant" of the F28 ...
Can be marked "Solved"
Thanks for all the suggestions and help ...
Oliver

JetNoise

@Martyn , 1st, sorry to ping you again.
It was this 0,01% i missed ;-).
I found the real reason for the missing "pilot calls"

In MSFS 2024 SETTINGS - SOUND the COMMUNICATIONS DEVICE OUTPUT was set to my headphones (by default (after the SU-1 Update maybe )
I put it back on SPEAKERS and the calls are back again (bc i had lost them again ...)
I recommend routing the "Pilots Calls" to the MAIN DEVICE, if possible.
When flying on Networks the Communication device will be the headsets again, thus not playing the pilot calls through the Main device (Cockpit sounds/ calls (like from the Copilot ...

Cheers
Oliver