Lvar Macros

[Glenn Weston]

Hi Pete, I have a couple of questions regarding macros using Lvars.

Also I must thankyou for the DEC,0 Action fix that you implemented in a recent update, that works perfectly now.

The Version I am running is 4.84, Just updated today actually.

I have two problems.

I am writing macros for the VRS Superbug and unfortunately none of the Lvar values are descriptive at all.

Here is an example that I posted a few weeks ago in regards to the Left DDI Mode knob.

It's a discrete 4 Position Knob & does not cycle, The Lvar is L:BCBGL, Values available are 0=Off 1=Night 2=Auto 3=Day

As the Lvar name is non descriptive I thought I would just create multiple macro files, as the macro file name comes up in FSUIPC pulldown list

and steer away from multi action macros.

So I created 4 Individual macros like so:

LDDIOff.mcro (Filename)

[macros]

1=L:BCBGL=SET,0

LDDINight.mcro (Filename)

[macros]

1=L:BCBGL=SET,1

LDDIAuto.mcro (Filename)

[macros]

1=L:BCBGL=SET,2

LDDIDay.mcro (Filename)

[macros]

1=L:BCBGL=SET,3

And to throw in for good measure, in case somebody would like to handle this function with a rocker switch to save inputs.

I created another 2 macros using the INC/DEC actions

LDDIModeIUp.mcro (Filename)

1=L:BCBGL=INC,3

LDDIModeDn.mcro (Filename)

1=L:BCBGL=DEC,0

As you can see to deck out the complete pit I will end up with a mother load of macro files & I seem to have found that the maximum number of macro

files that will populate in the ini file is 128.

I think I am probably pushing the use of the ini file over the edge but it seemed to be the only way to get nice descriptions against the macro actions.

Can you tell me what is the maximum number of macro files allowed is in the modules folder ?

I could not seem to find it in the docs & I did search them.

So I decided to revisit the Idea of multi action macros tonight but could not seem to get it to work on this version, I had done in an earlier version.

So I would just like to see if I am doing this correctly, this how I am writing the multi action macro.

LDDIMode.mcro (Filename)

[macros]

1=L:BCBGL

1.1=SET,0

1.2=SET,1

1.3=SET,2

1.4=SET,3

following the example in the manual which reads:

The multi-line macro format can still be used with the Lvar macros, as follows:

N=L:name

N.1=action1

N.2=action2

... etc.

I've been delving into Lua & I really think that Lua will be the solution using a Map of Parameter Values assigned to an action list.

I intend to publically post it all once completed at the VRS forums & here in the contributions area.

I am attempting to do all control via FSUIPC alone, so I don't have to run any other software.

I am just trying to work out the best way to tackle it.

Thanks for your terrific support.

Cheers Glenn.

[Pete Dowson]

So I created 4 Individual macros like so:

Very wasteful. Just have one macro

1=L:BCBGL=SET

without the parameter and use the parameter field in the assigned button or switch parameter field.

As you can see to deck out the complete pit I will end up with a mother load of macro files & I seem to have found that the maximum number of macro

files that will populate in the ini file is 128.

Probably, because each macro file is supposed to contain a large number of macros, not one in each! Use the parameters in the assignment for variations on one control. Collect all macros for one aircraft, or at least a complete subsystem of an aircraft, in one macro file.

Can you tell me what is the maximum number of macro files allowed is in the modules folder ?

I could not seem to find it in the docs & I did search them.

I don't know offhand. i can look it up for you, tomorrow maybe, but you should realy never need to know.

So I decided to revisit the Idea of multi action macros tonight but could not seem to get it to work on this version, I had done in an earlier version.

Multi-line macros do all of the actions with one assignment, so that is not something you want. You surely want to select one action. That's what parameters are for and why you can provide them when you assign.

Pete

[Glenn Weston]

Ok thanks, thanks Pete for clearing up the usage of macros for me.

I think I understand the way the mult line macros work now, I obviously didn't quite get it before.

I do understand that one line macros is a very inefficient way to do it but it was the only way to get a nice description of the function because I could make the macro file name describe the function & then the macro file name would show up in the pull down list when assigning a key or button, it would have worked for me but I hit that 128 maximum limit...... So it is no longer an option.

I am still interested to know if 128 is the maximum limit, when you get a chance.

It would be nice if the lvars could be assigned a descriptive name somehow but I am not sure how complex that would be for you to do.

I know some aircraft panels actually have descriptive lvars but unfortunately not the case in the vrs superbug.

Cheers Glenn.

[Pete Dowson]

I am still interested to know if 128 is the maximum limit, when you get a chance.

Yes, it is 128.

It would be nice if the lvars could be assigned a descriptive name somehow but I am not sure how complex that would be for you to do.

It would be a rewrite of the complete macro system. The L:Var name was pushed into the tables in the space normally occupied by the macro name, which is why you can't have both. L:Vars is a "bolt on" rather than a new facility. I'm really not wanting to make such drastic changes at this late time. Sorry.

Pete

[Glenn Weston]

No worries, thanks for the answers Pete.

Regards Glenn