MooneyDrover

Recently, my FS2020 cockpit (on PC) has been failing at random times, where the Bravo throttle quadrant controls stop working (mid-flight), so flaps won't go down, manual throttle doesn't work, etc. But if I hit ESC then click on Resume, the controls begin working again. Now happening multiple times in a single flight. Has anyone else dealt with this, and maybe found a solution? Thanks, Erik Goodman

Thanks, Oliver! I have taken your advice and started implementing my scripts concerning ground services by using the CDU button pushes, as you suggested, easily found under the PMDG_737 tab with the scripting editor. Clearly labeled... Menu button called Menu, first right-hand button called R1... I'd encourage anyone to try it out. Then, after you land, you don't need to poke around on a CDU to get your jetway to come out and your chocks to be set and your ground power attached... you just ask your AAO first officer to request those things, and she (programmatically) pushes the buttons to make it happen. It's very much easier than I had even expected! I've been able to get all of my "usual" requests to ground handled by my AAO First Officer via this scripting, and it all seems and sounds very natural, now! I'm a happy camper! (And I have also used events from the PMDG SDK.) I do still have one question: How does one indicate that the commands are for the FO's CDU instead of the Captain's? I didn't come across that in my meanderings. I sure appreciate all the great support you provide to the whole AAO community (long may they prosper)... Erik Goodman

Was just about to say, "You have made my day, and also my week!" when I accidentally hit "post" . I am truly impressed with the kind of support you provide for the AAO user community... l can't say enough! I'm sure it will be a key contributor to the future growth of the AAO community1 Erik Goodman

Thanks a lot for clarifying the situation. I just downloaded the PMDG tablet bridge from your website, and am delighted to find that it hass complete instructions and even an example in the readme1 Y I'll let you know how it comes out! Thanks again, Erik Goodman

I can program actions in the PMDG 738 FMC using AAO, but I can't find anything to use to program FS Actions (the other main part of the CDU), such as Pushback, etc. (I use AAO for EVERYTHING else, essentially.) I don't see any sim events triggered when I push the buttons in FS Actions. Is this something that's possible to do from AAO (in MSFS2020)? Any pointers would be much appreciated!! Thanks, Erik Goodman (MooneyDrover)

First of all, I don't know where the post just above came from... it says from ME (MooneyDrover), but I didn't post it, nor do I start MSFS from AAO, nor am I back in the cockpit without any issues. Very strange! Second, thanks for your explanation of the black screen after restart... I will indeed just stop AAO before Restart, then restart AAO after MSFS has completed its Restart. That is not a problem, as long as I know it isn't something that I screwed up myself! So the remaining problem is understanding why the 737COPILOT macro is not working and why the checklist command seems not to invoke the checklist processor. Yes, that is where the scriptfile initvoice.txt IS located. ("initvoicer.txt" was just a typo, sorry). The contents of initvoice.txt there are: <Macro Name="737COPILOT">VOICE:Microsoft Zira Desktop) (VOICERATE:0) (VOICEVOLUME:100) (SPEAK</Macro> and the "Approach Checklist command is now (for testing purposes, and after I changed the SPLIT to a WAIT at your suggestion): (SCRIPTFILE:737\initvoice.txt) (@737COPILOT: Testing 737Copilot after initvoice) (SPEAK: TRYING approach checklist) (WAIT:2000) (CHECKLIST:737\Approach_Checklist_737.txt) But here is what the AAO script processing reports when I press "test": Call: (SCRIPTFILE:737\initvoice.txt) (@737COPILOT: Testing 737Copilot after initvoice) (SPEAK: TRYING approach checklist) (WAIT:2000) (CHECKLIST:737\Approach_Checklist_737.txt) Pr2: (SCRIPTFILE:737\initvoice.txt) (SPEAK: TRYING approach checklist) (WAIT:2000) (CHECKLIST:737\Approach_Checklist_737.txt) Call: (CHECKLIST:737\Approach_Checklist_737.txt) The audio I hear is only "TRYING approach checklist". That is, athe @737COPILOT produces nothing, when it should say, "Testing 737Copilot after initvoice". The output above is identical if I invoke it by voice with my "approach checklist" voice command. Meanwhile, AAO works perfectly for all the other commands except the checklist commands. Zira responds perfectly to the rest. It looks like one of those "it can't possibiy behave this way" situations that I have met so many times in debugging code... only to later find a perfectly logical explanation. Let's hope there is one for this, too. Perhaps a clue is that it now appears NOT to be executing the CHECKLIST: command at all, whereas before I moved everything off OneDrive to be under C:/users/goodm/Documents/Lorby...etc., it used to actually CALL the CHECKLIST: command, producing "please confirm" four times, then "checklist end". That seemed like it found and executed the CHECKLIST command, but the command couldn't find the appropriate checklist. Now it seems like it's not even finding (or at least not executing) the CHECKLIST command.

After having to pause to fix some other things, I have returned to the checklist problem. I had a difficult time trying to figure out where the configuration is stored that tells the Checklist command where to look for checklist scripts... after trying to reorganize the file structure to reflect where the documentation for the checklists I downloaded are supposed to be, I managed to screw things up so that the checklist processing no longer enters a checklist at all. That is, instead of giving me the prompt "please confirm" several times then saying "checklist end", it now says nothing at all. The script to invoke the checklist is now: (SCRIPTFILE:737\initvoice.txt) (@737COPILOT: Testing 737Copilot after initvoice) (SPEAK: TRYING approach checklist) (SPLIT:2000) (CHECKLIST:737\Approach_Checklist_737.txt) Contents of initvoicer.txt is: <Macro Name="737COPILOT">VOICE:Microsoft Zira) (VOICERATE:0) (VOICEVOLUME:80) (SPEAK</Macro> and when I use several AAO commands before the checklist command, Zira answers me just fine... but she does NOT say "Testing 737Copilot after initvoice", and says only "TRYING approach checklist"... i.e., SPEAK works just fine, but "@737COPILOT" does not. I don't understand that, given that the 737COPILOT macro seems to be defined fine in initvoice.txt. NOW for the additional wrinkle: I have had a recurring problem (since my big crash a few month ago) of MSFS2020 crashing to black when I tell the simulator to "RESTART" the flight. I have now discovered that that happens whenever AAO is running at the time I push "RESTART". If I run commands with AAO (working fine), then kill AAO and hit RESTART, the restart goes fine, and I can then start AAO again and it, too, works just fine (except for the checklist problem). If I keep AAO running and hit RESTART, the music keeps playing, but all three main screens go black and MSFS no longer responds to mouse clicks, ESC key presses, or anything else... I have to use the OS to kill MSFS2020 and then restart it from scratch. So I would be very appreciative of ideas you might have... I have reloaded AAO, but the problem persists. Thanks much, Erik

Curiouser and curiouser! I checked, and the voice I use (Microsoft Zira) is still where it's supposed to be. I also moved the Documents folder to be directly under the "C" drive, rather than under OneDrive, which had grabbed it despite my not wanting to use OneDrive at all. I used the "Watch AAO script processing" window and learned that the script is, indeed, executing... The "Please confirm" is coming from the checklist processing, so the checklist is found, and is doing the first programmed check and waiting for my response. But I hear nothing when it prompts me, and even if I respond "Check", nothing happens. But at the same time, if I give my other commands (like Autobrake to RTO, Dim cockpit lights, toggle dome light, etc.), they are all executed properly and Zira answers me as programmed. I'm stumped!

Sorry I wasn't explicit enough in my post. What I am testing is the script that calls the checklist. For example, the script that calls the Approach Checklist is called "Approach Checklist, and is in the B737_Voice script group (which I downloaded from the web, and enhanced, but which used to work just fine. All of those checklists are still in the same place, and they look fine in Wordpad. Here's the script I test: (SCRIPTFILE:737\initvoice.txt) (CHECKLIST:737\Approach_Checklist_737.txt) I would normally call that script with a voice command I have created (in this case, the command is just "approach checklist". But when I call it with that command while MSFS is running, AND when I call it from the script editor, I just get the behavior for a missing checklist file, namely four "Please confirm" prompts and then "Checklist end." Is there someplace that might have gotten corrupted that tells the CHECKLIST: command where to look? It looks just right to me.

On my PMDG 737-800, I have been using AAO checklists without problems for a year, modifying them without any difficulty. After a recent system crash, I had to restore all the voice commands, and all worked fine except that none of the checklist commands would work. When I bring up a checklist script that worked perfectly before, in AAO's Script Editor, and push Test, it gives me four "Please confirm" prompts, then "Checklist end." It acts as if the checklist processor can't find the checklists, but they are exactly where they were before. Any help would be very much appreciated. It's taken me 2 months to recover from the crash, and this is almost the last item unresolved. Thanks, Erik

I've searched high and low for a way to use AAO to "ask" ground to connect pit power or a GPU to a PMDG 738. It's normally done through the FMC, ground services menu, but I would like to bypass that, as I have for pulling/setting the chocks. Has anyone found a way to do this? Thanks, Erik Goodman