MCE UI Window Minimizing and Checklist Help

[goose_lives69 2]

Anyone else experiencing the MCE UI Window minimizing on its own after a minute or two? Im in the process of setting up VoxScripts and it keeps minimizing before I can make too much progress. 

Also having a few issues with getting checklist to run correctly.

I'm needing help with getting my U.S. carrier's checklist  formatted text file to work with the sim. The checklist for example will ask for one thing and start moving down the list without a response from me to the next items on its own.

Edit:**I also noticed the GPWS SYS Test and Transponder System test switch potions were not listed in the VoxScripts list, any chance to add these, or is that no possible due to their spring loaded nature?**

Thanks in advance for the help and helping me stay current while I'm out on medical leave from work! 

_____________________________________________________________________________
BEFORE START ORIGINATING

[ ] Logbook -- Aboard
[ ] Landing gear pins -- Three Aboard
[ ] Fire warning and over -- Checked
[ ] Start levers --	CUTOFF
[ ] Stab trim cutout switches -- NORMAL
[ ] Lights test	--	Checked
[ ] FMC -- Programed
[ ] Briefings -- Complete
[ ] Oxygenmasks and quantity --	Checked
[ ] EEC -- ON
[ ] Navigation Switches	--	Normal
[ ] Display Switches --	Auto and Normal
[ ] Fuel --	_ Cleared With _ Center Pumps _
[ ] Passenger Signs	-- ON
[ ] Window heat	--	ON
[ ] Hydraulic pumps	--	A's OFF B's ON
[ ] Pressurization	--	Set AUTO
[ ] Flight Instruments	--	_ Set
[ ] Auto Brake	--	RTO
[ ] Takeoff Warning Horn	--	Checked
[ ] Parking Brake	--	Set
[ ] Transponder	--	TARA
[ ] Aileron and Rudder Trim	--	Centered

___________________________________________________________________________
BEFORE START

[ ] FMC --	Programed
[ ] Briefings --	Complete
[ ] Oxygen Mask and Quantity --	Checked
[ ] EEC's -- ON
[ ] Navigation Switches	--	Normal
[ ] Display Switches --	Auto and Normal
[ ] Fuel --	_ Cleared With _ Center Pumps _
[ ] Passenger Signs		--	ON
[ ] Window Heat	--	ON
[ ] Hydraulic Pumps	--	A's OFF B's ON
[ ] Pressurization	--	Set AUTO
[ ] Flight Instruments	--	_ Set
[ ] Auto Brake	--	RTO
[ ] Takeoff Warning Horn	--	Checked
[ ] Parking Brake	--	Set
[ ] Transponder	--	TARA
[ ] Aileron and Rudder Trim	--	Centered

____________________________________________________________________
BEFORE PUSH

[ ] Zero Fuel Weight	--	_ Set
[ ] Gross Weight	--	_ Crosschecked
[ ] PWB Remarks 	--	Reviewed
[ ] N1's 	--	_ Set
[ ] Runway 	--	_ Set
[ ] Flaps 	--	P W B _ C D U _
[ ] V Speeds 	--	_ _ _ Set
[ ] Stab Trim 	--	_ Set
[ ] Min Cleanup Altitude 	--	_ Set
[ ] Flight Deck Door 	--	Lights Out

_____________________________________________________________________________
BEFORE TAXI

[ ] Electrical 	--	Generators ON
[ ] Probe Heat	--	ON
[ ] Anti Ice	--	As Required
[ ] Flight Controls	--	Free
[ ] Flight Deck Windows	--	Closed and locked
[ ] Flaps	--	CDU _ Indicates _ Green Light

_____________________________________________________________________________
DEPARTURE PLAN

[ ] FMC --	Programed
[ ] Briefings --	Complete
[ ] PWB Remarks 	--	Reviewed
[ ] N1's 	--	_ Set
[ ] Runway 	--	_ Set
[ ] Flaps 	--	P W B _ C D U _
[ ] V Speeds 	--	_ _ _ Set
[ ] Stab Trim 	--	_ Set
[ ] Min Cleanup Altitude 	--	_ Set

_____________________________________________________________________________
BEFORE TAKEOFF

[ ] Min Takeoff Fuel --	Verified
[ ] Depature Plan 	--	_
[ ] Attendant Notification 	--	Complete
[ ] Electrical		--	Generators ON
[ ] Anti Ice --	As Required
[ ] Packs --	_
[ ] Bleeds --	_
[ ] Start Switches --	_ Continuous
[ ] APU --	_
[ ] Flaps	--	C D U _ Indicates _ Green Light
[ ] Start Levers	--	Indle
[ ] Recall	--	Checked

_____________________________________________________________________________
CLIMB

[ ] Pressurization 	--	checked 
[ ] Start Switches 	--	_
[ ] APU			--	_

_____________________________________________________________________________
DESCENT

[ ] Minimums 	--	Set
[ ] V Ref and V Target			--	_ _ Set
[ ] Autobrake --	_
[ ] Recall			--	Checked

_____________________________________________________________________________
APPROACH

[ ] Altimeters 	--	_ Set
[ ] Packs 	--	Auto
[ ] Start Switches --	_ Continuous

_____________________________________________________________________________
BEFORE LANDING

[ ] Speedbrake		--	Armed  Green light
[ ] Landing Gear		--	Down three green
[ ] Flaps		--	_ green light

_____________________________________________________________________________
PARKING

[ ] Parking Brake		--	_
[ ] Start Levers		--	Cutoff
[ ] Fuel Pumps		--	_
[ ] Window Heat		--	Off
[ ] Probe Heat		--	Auto
[ ] Anti Ice		--	Off
[ ] Hydraulic Pumps		--	Electrics Off
[ ] Start Switches		--	Off
[ ] Oil Quantity		--	_ percent
[ ] Hydraulic Quantity		--	_ percent
[ ] Radar		--	Test
[ ] Transponder		--	Stand by and zeros

 

Edited June 29, 2023 by goose_lives69

[FS++ 715]

8 hours ago, goose_lives69 said:

Anyone else experiencing the MCE UI Window minimizing on its own after a minute or two? Im in the process of setting up VoxScripts and it keeps minimizing before I can make too much progress. 

Also having a few issues with getting checklist to run correctly.

I'm needing help with getting my U.S. carrier's checklist  formatted text file to work with the sim. The checklist for example will ask for one thing and start moving down the list without a response from me to the next items on its own.

Edit:**I also noticed the GPWS SYS Test and Transponder System test switch potions were not listed in the VoxScripts list, any chance to add these, or is that no possible due to their spring loaded nature?**

Thanks in advance for the help and helping me stay current while I'm out on medical leave from work! 

_____________________________________________________________________________
BEFORE START ORIGINATING

[ ] Logbook -- Aboard
[ ] Landing gear pins -- Three Aboard
[ ] Fire warning and over -- Checked
[ ] Start levers --	CUTOFF
[ ] Stab trim cutout switches -- NORMAL
[ ] Lights test	--	Checked
[ ] FMC -- Programed
[ ] Briefings -- Complete
[ ] Oxygenmasks and quantity --	Checked
[ ] EEC -- ON
[ ] Navigation Switches	--	Normal
[ ] Display Switches --	Auto and Normal
[ ] Fuel --	_ Cleared With _ Center Pumps _
[ ] Passenger Signs	-- ON
[ ] Window heat	--	ON
[ ] Hydraulic pumps	--	A's OFF B's ON
[ ] Pressurization	--	Set AUTO
[ ] Flight Instruments	--	_ Set
[ ] Auto Brake	--	RTO
[ ] Takeoff Warning Horn	--	Checked
[ ] Parking Brake	--	Set
[ ] Transponder	--	TARA
[ ] Aileron and Rudder Trim	--	Centered

___________________________________________________________________________
BEFORE START

[ ] FMC --	Programed
[ ] Briefings --	Complete
[ ] Oxygen Mask and Quantity --	Checked
[ ] EEC's -- ON
[ ] Navigation Switches	--	Normal
[ ] Display Switches --	Auto and Normal
[ ] Fuel --	_ Cleared With _ Center Pumps _
[ ] Passenger Signs		--	ON
[ ] Window Heat	--	ON
[ ] Hydraulic Pumps	--	A's OFF B's ON
[ ] Pressurization	--	Set AUTO
[ ] Flight Instruments	--	_ Set
[ ] Auto Brake	--	RTO
[ ] Takeoff Warning Horn	--	Checked
[ ] Parking Brake	--	Set
[ ] Transponder	--	TARA
[ ] Aileron and Rudder Trim	--	Centered

____________________________________________________________________
BEFORE PUSH

[ ] Zero Fuel Weight	--	_ Set
[ ] Gross Weight	--	_ Crosschecked
[ ] PWB Remarks 	--	Reviewed
[ ] N1's 	--	_ Set
[ ] Runway 	--	_ Set
[ ] Flaps 	--	P W B _ C D U _
[ ] V Speeds 	--	_ _ _ Set
[ ] Stab Trim 	--	_ Set
[ ] Min Cleanup Altitude 	--	_ Set
[ ] Flight Deck Door 	--	Lights Out

_____________________________________________________________________________
BEFORE TAXI

[ ] Electrical 	--	Generators ON
[ ] Probe Heat	--	ON
[ ] Anti Ice	--	As Required
[ ] Flight Controls	--	Free
[ ] Flight Deck Windows	--	Closed and locked
[ ] Flaps	--	CDU _ Indicates _ Green Light

_____________________________________________________________________________
DEPARTURE PLAN

[ ] FMC --	Programed
[ ] Briefings --	Complete
[ ] PWB Remarks 	--	Reviewed
[ ] N1's 	--	_ Set
[ ] Runway 	--	_ Set
[ ] Flaps 	--	P W B _ C D U _
[ ] V Speeds 	--	_ _ _ Set
[ ] Stab Trim 	--	_ Set
[ ] Min Cleanup Altitude 	--	_ Set

_____________________________________________________________________________
BEFORE TAKEOFF

[ ] Min Takeoff Fuel --	Verified
[ ] Depature Plan 	--	_
[ ] Attendant Notification 	--	Complete
[ ] Electrical		--	Generators ON
[ ] Anti Ice --	As Required
[ ] Packs --	_
[ ] Bleeds --	_
[ ] Start Switches --	_ Continuous
[ ] APU --	_
[ ] Flaps	--	C D U _ Indicates _ Green Light
[ ] Start Levers	--	Indle
[ ] Recall	--	Checked

_____________________________________________________________________________
CLIMB

[ ] Pressurization 	--	checked 
[ ] Start Switches 	--	_
[ ] APU			--	_

_____________________________________________________________________________
DESCENT

[ ] Minimums 	--	Set
[ ] V Ref and V Target			--	_ _ Set
[ ] Autobrake --	_
[ ] Recall			--	Checked

_____________________________________________________________________________
APPROACH

[ ] Altimeters 	--	_ Set
[ ] Packs 	--	Auto
[ ] Start Switches --	_ Continuous

_____________________________________________________________________________
BEFORE LANDING

[ ] Speedbrake		--	Armed  Green light
[ ] Landing Gear		--	Down three green
[ ] Flaps		--	_ green light

_____________________________________________________________________________
PARKING

[ ] Parking Brake		--	_
[ ] Start Levers		--	Cutoff
[ ] Fuel Pumps		--	_
[ ] Window Heat		--	Off
[ ] Probe Heat		--	Auto
[ ] Anti Ice		--	Off
[ ] Hydraulic Pumps		--	Electrics Off
[ ] Start Switches		--	Off
[ ] Oil Quantity		--	_ percent
[ ] Hydraulic Quantity		--	_ percent
[ ] Radar		--	Test
[ ] Transponder		--	Stand by and zeros

 

Welcome aboard goose_lives69

The UI should only auto-minimize when in these screen panels, General, Command, Checklist, ATC, Sim, and About.

It should remain put when editing the flows.

Regarding checklist...

Only a single underscore "_" is allowed per line. You can speak anything you want there and FO won't challenge you

For items that the human recorded voices weren't prepared to handle like "PWB", write it as "P W B".

You can have a line checked by Fo only and move to next by adding this marker at the end of the checklist Line

[ ] flaps -- Set     //2

If both you and the Fo are expected to reply, use  //3

With no marker, by default you are expected to reply.

The flows aren't set in stone, nor are they realistic by default.

Think of them as a list of actions you expect Fo to perform. You can add more, remove some until the task sharing is ideal for your airline.

You can add these commands to any flow...

check gpws

gpws test

test gpws

verify gpws

check transponder

test transponder

transponder test

verify transponder.

Now, if you wanted to be able to say "GPWS SYS Test" (which isn't a built-in command), I refer you to this thread where you can learn how to "eductae" your Fo to understand ANY speech you want to come up with.

 

 

[goose_lives69 2]

Gerald thanks for the quick update. Some follow ups for you:

Quote

The flows aren't set in stone, nor are they realistic by default.

Is there a way to prompt the Voxscript flows without the FO saying "Starting flow" etc. when doing them? I have the Confirmation's empty  on a majority of Voxscript flows, but he still insist on saying that he's starting the flow. I saw someone mention they had a similar issue with this also but the thread died, is a work around to have the FO confirmation statement be blank or "ok"? I also have chattiness turned off also already so I'm not sure what else to do here to keep them quiet and just doing the flow when asked.

 

Quote

You can add these commands to any flow...

check gpws

gpws test

test gpws

verify gpws

check transponder

test transponder

transponder test

verify transponder.

When you say flow, do you mean the voxscript ones or the actual program's? If so how do I edit the actual program's flows? I haven't found anything after searching on here on how to do so, so I was under the impression custom flows had to all be built with VoxScripts. 

Additional question, I don't see these actions listed in the Available_Comands.dat file. Is there a comprehensive list of items that aren't in the VoxScipts Avalable_Comands.dat list? I saw you mentioned each one of those switches/positions has to be updated in updates due t o the modifying of various files.

I had a small list of mappings I'd like to request to get added to the next update for the PMDG pack if possible:

1. Ability to Test Oxygen on both sides

2. Ability to test GPWS SYS and TCAS switches (as apart of a flow/voxscript)

3. Ability to hack the Chrono clock timers 

4. Mapping the  Gen 1 and Gen 2 Electric Switches (I couldn't find anything similar to these in the available commands list)

5. Extending the landing lights is an available action, but retracting is not, please offer the ability to retract retractable landing lights.

6. Mapping of the APU switch to the OFF position cause "Start APU" exists already

7. Ability to have FO restore TRIM to a neutral setting of some sort (6.0?) as part of flows 

 

 

Maybe I'm going down the wrong path here with how I built my flows and could have edited the existing program's flows. Seems like everything I tread on here said build you own flows with VoxScript for best results.

Thanks again for your help and continued commitment towards support this product for so long!

 

Edited June 29, 2023 by goose_lives69

[FS++ 715]

14 hours ago, goose_lives69 said:

Gerald thanks for the quick update. Some follow ups for you:

Is there a way to prompt the Voxscript flows without the FO saying "Starting flow" etc. when doing them? I have the Confirmation's empty  on a majority of Voxscript flows, but he still insist on saying that he's starting the flow. I saw someone mention they had a similar issue with this also but the thread died, is a work around to have the FO confirmation statement be blank or "ok"? I also have chattiness turned off also already so I'm not sure what else to do here to keep them quiet and just doing the flow when asked.

There is an option in mce.ini

Change "AutoNotifyOnSilentFlowStart=1" to "AutoNotifyOnSilentFlowStart=0"

When you say flow, do you mean the voxscript ones or the actual program's? If so how do I edit the actual program's flows? I haven't found anything after searching on here on how to do so, so I was under the impression custom flows had to all be built with VoxScripts. 

By flow, I mean script as edited in Voxscript panel.

Additional question, I don't see these actions listed in the Available_Comands.dat file. Is there a comprehensive list of items that aren't in the VoxScipts Avalable_Comands.dat list? I saw you mentioned each one of those switches/positions has to be updated in updates due t o the modifying of various files.

Affirmative, you cannot get the Fo to switch something he wasn't trained to perform accurately. It's not a generic solution. He has to be taught how to do the switching on each supported complex plane. What you can do is tell him to do it using your own verbiage if the built in commands for the item don't spring to your mind naturally and of course dictate the sequence and pace of the switching as per your SOPs

 

Not all commands are listed in "Available commands_dat". Dialling commands for instance aren't as they cannot be scripted. Others were simply overlooked when the list was compiled.

I had a small list of mappings I'd like to request to get added to the next update for the PMDG pack if possible:

1. Ability to Test Oxygen on both sides. He can check his side with command "check oxygen".

2. Ability to test GPWS SYS and TCAS switches (as apart of a flow/voxscript). Add the commands listed above to the relevant script.

3. Ability to hack the Chrono clock timers He can start the flight timing with "start timing" command and launch chrono with "start chronometer". I guess not listed

4. Mapping the  Gen 1 and Gen 2 Electric Switches (I couldn't find anything similar to these in the available commands list). Try these commands "engine one generator on", "generator engine one on", "apu generator on", "connect apu generator" )there are many other speech variations)

5. Extending the landing lights is an available action, but retracting is not, please offer the ability to retract retractable landing lights. Maybe just missing in "Available commands.dat" list. Try command "retract landing lights"

6. Mapping of the APU switch to the OFF position cause "Start APU" exists already. Not sure I understand this

7. Ability to have FO restore TRIM to a neutral setting of some sort (6.0?) as part of flows. Try commands "reset pitch trim", "reset elevator trim", "pitch trim reset"... "reset rudder trim", "reset aileron trim"..

You can find more speech commands by looking at the Windows menu

Start->Multi Crew Experience->shared commands.

 

Maybe I'm going down the wrong path here with how I built my flows and could have edited the existing program's flows. Seems like everything I tread on here said build you own flows with VoxScript for best results.

Your understanding is correct. Just edit the pre-made flow or make your own n Voxscript panel. No programming required, just put English speech commands in a specific sequence and trigger the flow (script) with the pre-made or altered trigger sentence for flexibility.

Thanks again for your help and continued commitment towards support this product for so long!

You're welcome. We will continue to do so for as long as it takes.

Thanks for flying with us.

Answers embedded.

Edited June 30, 2023 by FS++

[goose_lives69 2]

A lot of help there Gerald, I appreciate it. I've got the flows working well now and only have a couple basic lingering questions I have not been able to find a clear answer too.

 

1. Ramp Services/Operations person. Im not seeing any documentation on what prompts they respond too. I've had luck asking for catering and that's it after randomly asking for stuff. Additionally, how do we turn off their hello at the beginning of a flight? I saw something about a modification the ini file in another post, but could not find the =0 setting mentioned. Not sure if it needs added to the ini to work?

2. When running checklist, some responses require me to say "point" or "decimal" in my responses to things like verifying fuel on board or the trim setting that is currently set. I often find the FO thinks im asking for a frequency of some sort to be set or setting of a heading when responding to some of these checklist items. Is there anyway to get them not to do this? Ive ran the voice trainer a few times now and have the same problem.

 

Best

[FS++ 715]

On 7/5/2023 at 6:50 PM, goose_lives69 said:

A lot of help there Gerald, I appreciate it. I've got the flows working well now and only have a couple basic lingering questions I have not been able to find a clear answer too.

 

1. Ramp Services/Operations person. Im not seeing any documentation on what prompts they respond too. I've had luck asking for catering and that's it after randomly asking for stuff. Additionally, how do we turn off their hello at the beginning of a flight? I saw something about a modification the ini file in another post, but could not find the =0 setting mentioned. Not sure if it needs added to the ini to work?

2. When running checklist, some responses require me to say "point" or "decimal" in my responses to things like verifying fuel on board or the trim setting that is currently set. I often find the FO thinks im asking for a frequency of some sort to be set or setting of a heading when responding to some of these checklist items. Is there anyway to get them not to do this? Ive ran the voice trainer a few times now and have the same problem.

 

Best

With regards Ramp services....

Documentation is available via the Windows menu. Start->Multi Crew Experience_you will see many docs. You'll find the commands not listed in "Available_Commands.dat" there.

Refer to "GSX&AES pdf doc for speech commands to use.

In general all commands addressed to rampy must start with either the name of the ramp agen or "ramp agent", "despatch", "ramp coordinator".

Eventually, if you can't be bothered to remember the many built-in commands, make your own. See how in this thread.

Regarding checklist...

If the reply always starts with the same word, you'd be better off writing "that_word(s)" followed by an underscore.

[ ] Checklist item   -- familiarWord _

That should help the speech engine differentiate between those replies and the specific commands to dial VHF, NAV freqs

[goose_lives69 2]

Re Ramp Services, thanks. I see the doc now, not sure how I missed it. 

I still do not know how to disable their load in message saying they are available and it's not in the documentation. 

 

Re: Checklist items, works much better now, is there a way to have the FO ignore the FLAPS per se in a checklist for an individual line? I know the check box to ignore positioning is there, but in my example, we are cross referencing the FLAPS in the CDU field under INIT REF with the calculated data only at the gate before push back. The flaps aren't actually set until clear of the gate area.  Using "CDU _" as my checklist response/item warrants the FO to trying to think I need him to verify the flaps are currently set to there.  

Edited July 7, 2023 by goose_lives69
spelling

[FS++ 715]

25 minutes ago, goose_lives69 said:

Re Ramp Services, thanks. I see the doc now, not sure how I missed it. 

I still do not know how to disable their load in message saying they are available and it's not in the documentation. 

 

Re: Checklist items, works much better now, is there a way to have the FO ignore the FLAPS per se in a checklist for an individual line? I know the check box to ignore positioning is there, but in my example, we are cross referencing the FLAPS in the CDU field under INIT REF with the calculated data only at the gate before push back. The flaps aren't actually set until clear of the gate area.  Using "CDU _" as my checklist response/item warrants the FO to trying to think I need him to verify the flaps are currently set to there.  

You're right, not only undocumented, but it's not even there in the default mce.ini Thanks for reporting this.

Look at this section

[RAMP]
NoRampToOfficeTalk=0
NoPaxDoorsAutoHandling=0
NoCargoDoorsAutoHandling=0

Add the following line....

NoGreeting=1

Will get back to you regarding the other unusual flaps consideration

 

[FS++ 715]

On 7/7/2023 at 8:48 PM, goose_lives69 said:

 

Re: Checklist items, works much better now, is there a way to have the FO ignore the FLAPS per se in a checklist for an individual line?

As part of the reply, try using keyword "check" or "verify" in which case you may reply with anything and he won't challenge you on that

[ ] item referring to flaps    -- check _

EDIT: Forgot to mention...

GSX integration is only in Ultimate and MSFS editions.

If using the PMDG 737 or any other aircraft specific product, it will come in next update sometime this month.

Edited July 9, 2023 by FS++

[goose_lives69 2]

Hey Gerald, hope you had a great weekend. 

I included check_verify_PWB_ CDU _ (intentionally meaning it will only listen for CDU = x in my response)

The FO still thinks I want flaps to the takeoff setting and is verifying the flaps are actually there. Is there any one just to ignore this line's Flaps response? 

 

Side Note: PMDG error, the FO is setting the transponder to TA mode when I'm asking for it to be set to standby.

[FS++ 715]

16 hours ago, goose_lives69 said:

Hey Gerald, hope you had a great weekend. 

I included check_verify_PWB_ CDU _ (intentionally meaning it will only listen for CDU = x in my response)

The FO still thinks I want flaps to the takeoff setting and is verifying the flaps are actually there. Is there any one just to ignore this line's Flaps response? 

 

Side Note: PMDG error, the FO is setting the transponder to TA mode when I'm asking for it to be set to standby.

FO looks for keywords like "flap" or "flaps", "cowl" etc to identify item.

Considering you're using TTS voices which can utter anything, a workaround would be to type "flaap" or "flaaps".

FO will then see it as unhandled item and will accept any answer.

As for PMDG 737, only have the 700 variant. It's possible the transponder equipment on other variants isn't the same, hence Fo possibly mishandling the switch.

Could you post a picture of the actual transponder panel on your plane? Thanks

[goose_lives69 2]

On 7/11/2023 at 5:22 AM, FS++ said:

FO looks for keywords like "flap" or "flaps", "cowl" etc to identify item.

Considering you're using TTS voices which can utter anything, a workaround would be to type "flaap" or "flaaps".

FO will then see it as unhandled item and will accept any answer.

As for PMDG 737, only have the 700 variant. It's possible the transponder equipment on other variants isn't the same, hence Fo possibly mishandling the switch.

Could you post a picture of the actual transponder panel on your plane? Thanks

Thing is PMDG still has a lot of customizable features even within the same model. However, the transponder is widely the same on all of them. 

[goose_lives69 2]

Gerald, following up on my transponder issue in addition to another:

 

Above is what the transponder looks like, if Im at this step and the challenge is "Stby" or "Stand By" it says its wrong and mvoe the switch to the TA Only Mode. 

 

I am noting that in my Before Takeoff Checklist, APU: AS REQUIRED or if I try just a _ for the checklist response. Often the APU is OFF at this stage of the flight during taxi out. However, if the APU is in its cooldown/shutdown phase (swith is in the OFF position) it still thinks the APU is on and challenges me to double check the item. Is there a way to just look at the switch and understand the APU is indeed off because its in its self cool down phase on the PMDG? 

[FS++ 715]

On 8/1/2023 at 8:31 PM, goose_lives69 said:

Gerald, following up on my transponder issue in addition to another:

 

Above is what the transponder looks like, if Im at this step and the challenge is "Stby" or "Stand By" it says its wrong and mvoe the switch to the TA Only Mode. 

 

I am noting that in my Before Takeoff Checklist, APU: AS REQUIRED or if I try just a _ for the checklist response. Often the APU is OFF at this stage of the flight during taxi out. However, if the APU is in its cooldown/shutdown phase (swith is in the OFF position) it still thinks the APU is on and challenges me to double check the item. Is there a way to just look at the switch and understand the APU is indeed off because its in its self cool down phase on the PMDG? 

Package has been updated.

If you bought your PMDG 737 crew copy from Simmarket, get the update from there. If it's from our website, please contact support in order to get the dowload link. Thanks