4 minutes ago, bahnzo said:

I was under the impression LVARS were only declared by the dev of the plane for us to read

Not at all. LVars are never "declared", everybody can just invent them. In the sim too, that is what they are for. Developers don't "declare" them either, they just use them in their own RPN code and we can read from and write to them any time.

Just be clear about that difference between internal and simulator ones.

The main purpose of LVars in the sim is to transport information from one aircraft module (switch, lever, gauge, aircraft system, animated curtain, whatever) to the other, when that data point doesn't exist in the sim itself. With LVars, developers usually control their animations and illuminations. 

Edited October 20, 20241 yr by Lorby_SI

11 minutes ago, bahnzo said:

But I have no idea if having that sitting there the entire flight (maybe hours even) would cause any sort of issue

No issues. Make sure to look into CONVERSATION scriptfiles though, that is exactly what they were made for.

6 minutes ago, Lorby_SI said:

No issues. Make sure to look into CONVERSATION scriptfiles though, that is exactly what they were made for.

Ok, good to know. I'll put it in tomorrow and see how well it works. I did read the conversation part, but I don't think that's what I'm looking to do. At least not with this checklist. But I can see how that would work well for things like simulating interactions between flight crew members. I was thinking about adding in briefings since the LJ35 checklist calls for it, but...later maybe. 

Edited October 20, 20241 yr by bahnzo

8 minutes ago, bahnzo said:

Ok, good to know. I'll put it in tomorrow and see how well it works. I did read the conversation part, but I don't think that's what I'm looking to do. At least not with this checklist. But I can see how that would work well for things like simulating interactions between flight crew members. I was thinking about adding in briefings since the LJ35 checklist calls for it, but...later maybe. 

Despite the name, CONVERSATION is not about people talking to each other. The main feature is, that you can make it wait until certain conditions are met before proceeding. There doesn't have to be a single SPEAK or SOUND in a CONVERSATION, it is the control flow that is important. 

In your case you would create a master "CONVERSATION" that is tracking the various phases of your flight, and then, for example, calling checklists that suit the current phase.

Edited October 20, 20241 yr by Lorby_SI

42 minutes ago, Lorby_SI said:

In your case you would create a master "CONVERSATION" that is tracking the various phases of your flight, and then, for example, calling checklists that suit the current phase.

Excellent I'll look into that more then. 

I'm also testing the AWS Polly, since they are so generous with their free account now. 

I'm using the setup I learned from the C172 files, so:
 

<Macro Name="ASSIST">VOICE:Microsoft Zira) (VOICERATE:0) (VOICEVOLUME:100) (SPEAK</Macro>

:parking_brake
[](@ASSIST:set parking brake)
(A:BRAKE PARKING INDICATOR, Bool) 1 == if{ (GOTO:batteries_on) }
[0](@ASSIST:check parking brake) (GOTO:parking_brake)

As an example. Is it as simple as inserting the Polly voice to change all my scripts?
ie:  <Macro Name="ASSIST">VOICE:POLLY|en-US Gregory|neural) (VOICERATE:0) (VOICEVOLUME:100) (SPEAK</Macro>

I can't get that to work, but I can get this to speak with the Polly voice:
(VOICE:Polly|en-US Gregory|neural)
(SPEAK:testing pre start checklist)

26 minutes ago, bahnzo said:

I can't get that to work

POLLY vs. Polly

Everything in AAO is case sensitive.

Edited October 20, 20241 yr by Lorby_SI

Can I put my checklist script files in their own folder within the script folder?

(CHECKLIST:\LJ35\LJ35-00-prestart.txt)
 

Is what I'm using but with no luck. 

4 hours ago, bahnzo said:

(CHECKLIST:\LJ35\LJ35-00-prestart.txt)
 

Is what I'm using but with no luck. 

Lose the first backslash. It is just (CHECKLIST:LJ35\LJ35-00-prestart.txt) - see AAO manual, the table with all the AAO commands, there are examples. (CHECKLIST: has additional options to call scriptfiles.

How can I nest a [] for confirmation when using an if statement?

My code: 

(IE:GENERIC_LEAR_STARTER_R) 0 != (IE:GENERIC_LEAR_STARTER_L) 0 != or if{ (@ASSIST:Please Check Generator switches) }

I'm checking to make sure I've remembered to turn the starter switches to the generator position. This works, but if I don't have the gen switches set, then it gives me the reminder, but goes immediately to the next item in the checklist. How can I make it wait for my voice confirmation before continuing?

Edited October 29, 20241 yr by bahnzo

5 hours ago, bahnzo said:

How can I nest a [] for confirmation when using an if statement?

[(IE:GENERIC_LEAR_STARTER_R) 1 == (IE:GENERIC_LEAR_STARTER_L) 1 == and] (@ASSIST:Please Check Generator switches)

It works the other way around. This will be repeated until both switches are set.

Or you could try a GOTO loop

:genswitches
(IE:GENERIC_LEAR_STARTER_R) 0 != (IE:GENERIC_LEAR_STARTER_L) 0 != or if{ (@ASSIST:Please Check Generator switches) (WAIT:2000) }
(IE:GENERIC_LEAR_STARTER_R) 0 != (IE:GENERIC_LEAR_STARTER_L) 0 != or if{ (GOTO:genswitches) }

But - to be honest, I'm not well versed in these matters. I only provide the hammer, I don't build the house. There are AAO testers out there who are way more proficient with this kind of thing... *nudge* 🙂
 

7 hours ago, Lorby_SI said:

Or you could try a GOTO loop

Thanks, I think the GOTO loop would work best considering what I want it to do. I got so obsessed with trying to figure out a way to use the [] I didn't consider a simple option like that would make the most sense. 

This is a neat tool. I happen to use a Bravo quadrant but it has a utility that reads every current A: and L: var running..It gives name, unit, value. I use it observe values when troubleshooting: Better Bravo Lights for Microsoft Flight Simulator | MSFS

34 minutes ago, mrm0508 said:

has a utility that reads every current A: and L: var running..

For LVars you can also do that in MSFS developer mode, without any additional software, on the Tools->Behaviors dialog.

I'm having a problem I'm not sure how to deal with. 

In my checklist, I'm having the co-pilot set the barometer when we pass down through 18,000ft. This should be easy, as I'm just having it use the auto-set in MSFS which I have coded as: [0] 0 (>K:BAROMETRIC)

This works, but for some reason it's not working all the time 100%. I'm not sure why. Any idea? Should I put a (WAIT:500) before it? I noticed that I'm going directly from announcing the start of the checklist to the command, maybe that's it?

Normally, I would just have the code read the barometer and check that it's changed from 29.92 (or in the rare case it's 29.92 below 18K come up with something to deal with it), but I can't find any LVar were the current altimeter setting is stored. 


Also: any idea or tips on how to more easily test something like this? I'm not sure how I could setup the plane to start in the air and descend past 18k, and then reset it to test again, etc. Would slewing achieve that? 

Thanks!

 

Edit: one more. Is there a way to display info I can query from my simbrief flightplan? Some sort of message box or? I'm not sure if I see anything in AAO which would allow that. 

Edited November 7, 20241 yr by bahnzo

On 11/2/2024 at 12:19 PM, Lorby_SI said:

For LVars you can also do that in MSFS developer mode, without any additional software, on the Tools->Behaviors dialog.

I can see how this tool would be useful tho. For me, using dev mode is a pain in the butt, as I don't run MSFS in the same resolution as my monitor, so I have to go and change MSFS, then go back to dev mode, etc etc. Something like this tool would be pretty useful.