• 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.

MSFS Variable prefix types

Messages
927
Country
australia
As I am waiting for the latest update to download I thought I'd ask if anyone knew about the various XML variable prefix types.

L: is, of course, the good old familiar Local variables
M: for mouse variables
K: for writing to events
A: for simulation variables

O: appears to be a very local variable particular to each component in a model (see my earlier post about how to create mouse zones: https://www.fsdeveloper.com/forum/threads/heres-how-to-write-you-own-modelbehavior-code.451037/). I guess the correct terms would be to call O: vars local variables and L: vars global variables.

H: this is something I've seen in OneStore\fs-base-aircraft-common\ModelBehaviorDefs\Asobo\Misc\Clock.xml. It appears that you write to the H: variable and then you can read it in a onInteractionEvent(_args) function in your js. In this case it is the M803 clock js which uses this to check if a button has been pressed in the 3D model. This is something I'd like to test but I can't because MSFS needs to download 21GB of data RIGHT NOW.

Anyone want to add to this list (or know if it's in the SDK docs, I couldn't find it)?
 
Messages
120
Country
italy
Screenshot 2021-02-13 151549.png



old but still useful ;)
 
Messages
927
Country
australia
I guess I forgot about all those old var types.

I did some searching by loading all the model behavior files into Notepad++ and searching for all files.

I found one other new type.

H: (used in html interactions) and O: (local component variables defined by the developer) I mentioned in my original post but I've also found:

I: Looks to be another developer variable. Not really sure what it does or how it's different from O: or L:. It is used in Common\Instrument.xml as (I:XMLVAR_Hours_Delta), Common\Pressurization.xml as (I:XMLVAR_Deploy) and (I:XMLVAR_MICRO_MASK_cover) as well as various other xml files doing all sorts data storage stuff.

So, we have the ones listed by 614NLV which are carried over from FSX and three new ones in MSFS, H: O: and I:
 
Messages
10
Country
southafrica
I: Looks to be another developer variable.

That could be an INPUT variables. They seems to be used in the SPB's for visual-fx (which I think does not work yet).

There are various of those types described in the propdefs (but still not sure how to decode them).
  • INPUTVARIANT
  • INPUTFLOAT
  • INPUTFLOAT3
  • INPUTCOLOR
One of the default values seems to describe it as a GUID + value.
 
Top