• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 Lua in XML gauges

S

SkippyBing

Messages
368
Country
unitedkingdom
Has anyone got a sample gauge with Lua script in an XML gauge? I can't get even the simplest code to work so either I'm missing something obvious or my P3D is just borked!

e.g.

This does nothing:

<Gauge Name="Test" Version="1.0">
<Size X="500" Y="326"/>

<Element>
<Select>
<Value>
!lua varset("K:FLAPS_1", 0)
</Value>
</Select>
</Element>

</Gauge>
 
It’s been a while since I looked at this but remember getting the basic clock in the SDK working

Try this instead:

!lua return varset("K:FLAPS_1", ”0”)
 
No joy. The gauge is definitely set up right as I've just thrown a bit of standard XML code to set an LVar and that worked. Think I'll play around with the clock sample to see if I can make sense of it.
It's annoying as I had a snippet of code working a few years ago but I've lost it now!
Thanks for trying.
 
So after getting a vaguely working clock gauge (seriously have you tried creating graphics for a gauge you haven't written?!) I turned on content error logging and noticed my test gauge was throwing an error the clock wasn't.
It appears that for Lua to work in an XML gauge the !lua statement must be immediately after the <Value> tag. i.e.:

<Value>!lua

not

<Value>
!lua

Which is almost obvious if you look at the two sample scripts in the SDK.
 
You must log in or register to reply here.
Back
Top