mrm0508

Wow, thank you so much for expanding on this. I have little knowledge of how the sim and AAO treat RPN differently, I end up with a lot of trial and error.....mostly error :) Much appreciated.

These variables are compartment latches, they are either closed (0) or open (1), I am trying to check if they are all open prior to trying to open the compartment (L:SW_SOV_PANELS_Door_Baggage, Bool) which also is either closed (0) or open (1). So, if both latches are closed (both 0) the door won't open and if they are both open, then the door can open. So, I am checking to see if both latches are the same (1 or 0) with "and" and that doesn't work, it only works if I explicitly use "0 ==" or "1 ==" in the expression. It great simplifies the code if I can just use the implicit version. Here is the mousrects code for the clickspot I am working on. This code does not run in AAO as written: (A:SIM ON GROUND, Bool) 1 == if{ (L:SW_SOV_CONFIG_Simple_Openings, Bool) 0 == if{ (L:SW_SOV_PANELS_Latch_Baggage_1_1, bool) (L:SW_SOV_PANELS_Latch_Baggage_2_1, bool) (L:SW_SOV_PANELS_Latch_Baggage_3_1, bool) (L:SW_SOV_PANELS_Latch_Baggage_4_1, bool) (L:SW_SOV_PANELS_Handle_Baggage, bool) and and and and if{ (L:SW_SOV_PANELS_Door_Baggage) ! (>L:SW_SOV_PANELS_Door_Baggage) } } els{ (L:SW_SOV_PANELS_Door_Baggage) ! (>L:SW_SOV_PANELS_Door_Baggage) (L:SW_SOV_PANELS_Door_Baggage) (>L:SW_SOV_PANELS_Latch_Baggage_1_1) (L:SW_SOV_PANELS_Door_Baggage) (>L:SW_SOV_PANELS_Latch_Baggage_2_1) (L:SW_SOV_PANELS_Door_Baggage) (>L:SW_SOV_PANELS_Latch_Baggage_3_1) (L:SW_SOV_PANELS_Door_Baggage) (>L:SW_SOV_PANELS_Latch_Baggage_4_1) (L:SW_SOV_PANELS_Door_Baggage) (>L:SW_SOV_PANELS_Handle_Baggage) } } This is what I did that worked: (A:SIM·ON·GROUND,·Bool)·1·==·if{·(L:SW_SOV_PANELS_Door_Baggage,·bool)·0·==·if{·(L:SW_SOV_PANELS_Latch_Baggage_1_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_1_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_2_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_2_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_3_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_3_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_4_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_4_1,·Number)·(WAIT:3000)·(L:SW_SOV_PANELS_Handle_Baggage,·Number)·!·(>L:SW_SOV_PANELS_Handle_Baggage,·Number)·(WAIT:1000)·(L:SW_SOV_PANELS_Door_Baggage,·bool)·!·(>L:SW_SOV_PANELS_Door_Baggage,·bool)}} ·(L:SW_SOV_PANELS_Door_Baggage,·bool)·1·==·if{·(L:SW_SOV_PANELS_Door_Baggage,·bool)·!·(>L:SW_SOV_PANELS_Door_Baggage,·bool)·(WAIT:5000)·(L:SW_SOV_PANELS_Handle_Baggage,·Number)·!·(>L:SW_SOV_PANELS_Handle_Baggage,·Number)·(WAIT:1000)·(L:SW_SOV_PANELS_Latch_Baggage_1_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_1_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_2_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_2_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_3_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_3_1,·Number)·(L:SW_SOV_PANELS_Latch_Baggage_4_1,·Number)·!·(>L:SW_SOV_PANELS_Latch_Baggage_4_1,·Number)·}

Either of these should flip the boolean value of (L:SW_SOV_PANELS_Door_Baggage, Bool) This does not work (A:SIM ON GROUND, Bool) 1 == if{ (L:SW_SOV_CONFIG_Simple_Openings, Bool) 0 == if{ IMPLICIT (L:SW_SOV_PANELS_Latch_Baggage_1_1, Bool) (L:SW_SOV_PANELS_Latch_Baggage_2_1, Bool) and if{ (L:SW_SOV_PANELS_Door_Baggage, Bool) ! (>L:SW_SOV_PANELS_Door_Baggage, Bool) } } } This works (A:SIM ON GROUND, Bool) 1 == if{ (L:SW_SOV_CONFIG_Simple_Openings, Bool) 0 == if{ EXPLICIT (L:SW_SOV_PANELS_Latch_Baggage_1_1, Bool) 0 == (L:SW_SOV_PANELS_Latch_Baggage_2_1, Bool) 0 == and if{ (L:SW_SOV_PANELS_Door_Baggage, Bool) ! (>L:SW_SOV_PANELS_Door_Baggage, Bool) } } }

Can you access their support Portal - PMDG Simulations? How about their Discord https://discord.gg/

You can select the N1 reference option in the FMC PMDG Setup

Axis and Ohs provides interfaces to many FMC's

No, this is an issue with Live weather, there isn't a way for AAO to turn live weather off for you.

You might as well add the PMDG_737MSFS_Data also

Make sure you have enabled data in the aircraft ini file

To toggle a variable from 1 to 0 or 0 to 1 this operation works well: (V:TheVariable) ! (>V:TheVariable) This basically reads the variable then flips its binary value and writes it back to the same variable

I use 100·(>L:VC_HUD_MOVE_VAL,·number) for HUD down, 0·(>L:VC_HUD_MOVE_VAL,·number) for HUD up

I created the start of scripts for the C750. Right now, it has the APU Panel, Power Panel, some Ext Lights, and Autopilot....enough to get you started anyway. C750 script

That worked, I also had to update the html with the -200ER path

Trying to get the aao-tablet package working with the PMDG -200ER since it uses the same variables as the -300ER. I created a pmdg-777-200er folder with the html file within the package and ran the layout generator. When I run the sim, it shows that the html page is not being loaded into the VFS. Is there something I am missing?

I get sim CTD's when AviaServer 2024 is running (both 2020 and 2024 sim versions). It happens at random times, but it always crashes at some point when the server is running with a memory violation code. I have no sim crashes when the server is not running. Is there a log file I can send you? Mike