The checklist reading unfortunately doesn't work well for me. As an example, below is a simple landing checklist I'm trying to use.

_____________________________________________________________________________
LANDING

[ ] Start switches                  --    Continuous //2
[ ] Speed brake                    --    Armed //2
[ ] Gear                                --    Down //2
[ ] Flaps                               --     Green light //2

_____________________________________________________________________________

This is what I have in my text file. There are several issues: On reading the speed brake entry, instead of just checking the speed brake being armed the F/O de-arms the speed brake every time and then finishes the line. Next, it randomly says something like "Hi, I'm Trav, we'll be working together" in the middle of the checklist. In the last line, the F/O waits for me to respond because it doesn't seem to notice the //2 for co-pilot response at the end.

Sometimes it also doesn't read a word, like skipping "Pilot" in [ ] Pilot and flight attendant briefings or just reading "Departure" instead of the full line [ ] Departure announcement.

Any tips on how to work with custom checklists? Some checklist parts work fine while others don't work very well for some reason even though these are pretty simple and short.

8 minutes ago, threegreen said:

The checklist reading unfortunately doesn't work well for me. As an example, below is a simple landing checklist I'm trying to use.

_____________________________________________________________________________
LANDING

[ ] Start switches                  --    Continuous //2
[ ] Speed brake                    --    Armed //2
[ ] Gear                                --    Down //2
[ ] Flaps                               --     Green light //2

_____________________________________________________________________________

This is what I have in my text file. There are several issues: On reading the speed brake entry, instead of just checking the speed brake being armed the F/O de-arms the speed brake every time and then finishes the line. Next, it randomly says something like "Hi, I'm Trav, we'll be working together" in the middle of the checklist. In the last line, the F/O waits for me to respond because it doesn't seem to notice the //2 for co-pilot response at the end.

Sometimes it also doesn't read a word, like skipping "Pilot" in [ ] Pilot and flight attendant briefings or just reading "Departure" instead of the full line [ ] Departure announcement.

Any tips on how to work with custom checklists? Some checklist parts work fine while others don't work very well for some reason even though these are pretty simple and short.

The human recorded co-pilot voices may not always have all the custom vocabulary you may come up with. There are alternative words you could use.

I suggest you send your custom checklist and we'll run it in the debugger.

cannot explain why he says "hi", unless somehow he got speech command "what's your name" or something similar (check your mike sensitivity).

MCE is multi-threaded. While going through the checklist, you can always ask him the odd question, get him to flip the odd switch or dial something, not to mention interact with ATC.

He can check about anything in PMDG 737 NGX/NGXu apart from some items in FMC-CDU like waypoints and such.

It's possible you are having issues with MCE not getting data from the sim.

With NGX loaded in the sim, no engines running, start MCE and go to <Sim> tab.

It should show "on ground, No engines running". Within 10 seconds after you start the first engine, it should reflect on the panel. Equally, when you're airborne it should see it as such.

Otherwise, nothing will work as expected. You may not get call-outs or things like that.

We advise users to resist the temptation to override folders permissions, or disable Windows UAC.

You would just need to install MCE to default path and in the worst case, run "Pepar3D.exe" as admin in order to guarantee smooth opeation.

 

 

 

 

Thanks, I will check mic sensitivity. The lines above work better with an underscore in the response.

I've noticed however that during the checklist, the F/O always asks to check the battery switch again even though it's in the proper position and matches with my response. He doesn't seem to be able to confirm the switch position. This works fine outside of the checklist though.

He also thinks the APU switch is on when it is in fact off during the checklist and he starts the APU and then confirms it's off.

16 hours ago, threegreen said:

Thanks, I will check mic sensitivity. The lines above work better with an underscore in the response.

I've noticed however that during the checklist, the F/O always asks to check the battery switch again even though it's in the proper position and matches with my response. He doesn't seem to be able to confirm the switch position. This works fine outside of the checklist though.

He also thinks the APU switch is on when it is in fact off during the checklist and he starts the APU and then confirms it's off.

All those perceived failures to read state could be down to one setting in your PMDG aircraft

With PMDG NGX & NGXu, the "mcpmd73X.dll" in \MCE dlls\ folder, interacts with that plane using the PMDG SDK. Make sure Data broadcasting is enabled, or else, the dll won't have access to switches status.

Go to \Prepar3D v4\PMDG\PMDG 737 NGXu\ and open "737NGX_Options.ini". Ensure

[SDK]
EnableDataBroadcast=1

On 7/28/2021 at 12:39 PM, FS++ said:

[SDK]
EnableDataBroadcast=1

Is turned on as my throttle quadrant needs it to work.