Listing L:var

[Gypsy Baron]

EDIT: OKI, got it to work. I had to enable "Extras (Miscellany) in the Logging display

under Logging Details. This wasn't totally obvious from all that I read in the

various manual PDF files.

I'm trying to get a list of L:var used in various aircraft however the

drop-down menu option "List local panel variables" does not appear in

any of the Options and Settings menus.

I have a registered version of FSUIPC and the latest incremental download

from today ( FSUIPC4539 ).

Is this option still available? Is there an entry in the FSUIPC.ini that I

need to create or set to enable that option in a drop-down list?

Paul

EDIT:

I've assigned keys in the Buttons & Switches menu to "LuaSet Log LVars" and "LuaKill Log LVars"

but nothing appears in the log file. I also tried "LuaToggle Log LVars" but that didn't work

for me either.

[Pete Dowson]

OKI, got it to work.

What's that? You seem to have continued something but in a new thread, so I've lost any continuity.

I had to enable "Extras (Miscellany) in the Logging display under Logging Details. This wasn't totally obvious from all that I read in the various manual PDF files.

Sorry, you had to enable Extras logging for what purpose, exactly? What should be made clear in what various PDF files?

I'm trying to get a list of L:var used in various aircraft however the drop-down menu option "List local panel variables" does not appear in

any of the Options and Settings menus.

There is no such drop--down menu item. Where did you get that idea?

Are you perhaps getting mixed up with the Lua plug-in I provided to log L:vars? You need to have the example Lua program in the FS modules folder, and then start it by assigning a keypress or button to it and activate it with that button or keypress.

Is this option still available? Is there an entry in the FSUIPC.ini that I

need to create or set to enable that option in a drop-down list?

Sorry, you'll need to explain why you think there was or ever will be such an option.

I've assigned keys in the Buttons & Switches menu to "LuaSet Log LVars" and "LuaKill Log LVars"

but nothing appears in the log file. I also tried "LuaToggle Log LVars" but that didn't work

for me either.

Oh dear. You really do need to read a little more. There are a number of Lua-related controls, all clearly described in the Lua document:

Lua to RUN a plug-in

LuaKill to Kill a running Lua plug-in

LuaSet with a parameter, to Set one of 32 flags for a running plug-in

LuaClear .... similarly to clear the flag

LuaToggle .... similarly to toggle the flag

LuaDebugto run the plug-in with debug tracing, line by line in the Lua program. (This needs the debug lua plug-in present too).

It seems, by lack of reference to what the facilities are, you tried everything EXCEPT running the plug-in which does what you want. :-(

Pete

[Gypsy Baron]

Sorry if my post was a bit confusing.

The comments at the top of my post after EDIT: were the last observations

once I got the logging of the L:vars working.

I decided to place them up there since I had resolved the issue, rather than

append them to the bottom of the post after my first EDIT: entry.

As to the resolution process:

What initially confused me was the second paragraph in the FSUIPC4 for Advanced Users.pdf

on page 34 that referenced "a new assignable control in the drop-down lists called

List local panel variables". It doesn't exist, at least I could not find it.

I later found the references to the Lua commands and then used the Button and Switches

menu to assign the L:var logging funtions.

Nowhere did I see anything to indicate that I needed to enable the "Extras (Miscellany) "

feature in the Logging menu but that is what was needed to get the L:var logging

to take place. Without it I could press the switches that I had assigned to the Lua funtions

( "LuaSet Log LVars" and "LuaKill Log LVars" ) all day with no effect.

I managed to eventually get the desired outputs after some trial and error.

Trying to bounce between multiple PDF manuals slowed my progress a bit.

So, to sum up, I am able to list the L:Vars which is what I wanted to do.

Paul

[Pete Dowson]

What initially confused me was the second paragraph in the FSUIPC4 for Advanced Users.pdf

on page 34 that referenced "a new assignable control in the drop-down lists called

List local panel variables". It doesn't exist, at least I could not find it.

Oh, did I say that? Let me checkAh, yes! Do you know, I clean forgot I'd added that control.

I just checked. It is certainly there, in its correct alphabetical order, named "List local panel vars". I don't understand why you couldn't find it -- I just dropped the list, hit "L I S" keys reasonably quickly, and there it was! It sits between "Letterbox" and "Lod zoom in".

There's no need whatsoever to enable any other logging options for it to work.

Nowhere did I see anything to indicate that I needed to enable the "Extras (Miscellany) "

feature in the Logging menu but that is what was needed to get the L:var logging

to take place. Without it I could press the switches that I had assigned to the Lua funtions

( "LuaSet Log LVars" and "LuaKill Log LVars" ) all day with no effect.

There's certainly no need to enable Extras logging, and as I already told you, the LuaSet and LuaKill controls do NOT run the Lua plugin. Only the "Lua" and "LuaDebug" controls run a plug-in. Please do read what I write even if you cannot find the Lua documentation. I did even list the different Lua controls for you!

I managed to eventually get the desired outputs after some trial and error.

Trying to bounce between multiple PDF manuals slowed my progress a bit.

Sorry, but i think you must be missing the obvious somehow. There's never a need to bounce any PDF manuals anywhere anyhow.

So, to sum up, I am able to list the L:Vars which is what I wanted to do.

Well, I don't understand how. If you couldn't find the control for it which is most definitely there, and you couldn't work out how to run a Lua plug-in, which you certainly cannot with the controls you've been using, then I've no idea at present how you did it. Maybe you found some debugging tool I'd left in? That's what the Extras option is normally about -- I advise folks on how to use it when I need to get additional information in order to debug or develop something or other. :-)

Pete