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

FSX Logging the Flight1 ATR 72

T

ti_dabbelju

Messages
43
Country
germany
Hi,

I want to use the Flight1 ATR for building a simulator. All gauges are in a .dll and you cannot look at the code. The add-on uses only some standard keys and simvars, a lot is custom built into the gauges.

I have managed to assign buttons to some functions with FSUIPC mouse macros. This works well but it's always a toggle function. To make it work with hardware switches and LEDs I need to know the status of switches and variables.

Unfortunately FSUIPC logging doesn't reveal anything useful.

Any ideas how I could access this proprietary data?

Thanks.
 
That's something one would have to contact Flight1 about....
 
I talked to someone who tried but not a chance.

Another thought is: I can open the panel in FS Panel Studio and open the gauge editor. No code but I can see the bitmaps that are used as annunciators. Is there a way to find out what bmps are currently visible?

I thought there are maybe some logging facilities to find out what's going on. Even logging the standard simvars might reveal more of interest.
 
ti_dabbelju said:
I thought there are maybe some logging facilities to find out what's going on. Even logging the standard simvars might reveal more of interest.
Click to expand...

It is different depending on the panel mode.

In VC, switches and needles are managed through AVars-LVars, so it would be possible to inspect their behavior using some available utilities like BlackBox3; LocalVarsLogger and EventsLogger (both in XMLVars bundle), and Doug Dawson's own set.

In 2D panels, everything is probably handled by regular C++ variables, hence you won't be able to do anything here without Flight1's support.

Tom
 
Now that I looked at the download I'm a little lost. What do I need to do to log LVARS that I don't even know if they exist and what they're called? Any idea?
 
Hello, well that's the point! After unpacking and installing the dll I don't know at all what to do! Do I need to add a gauge to the ac's panel? Remember I need to log the ac's behaviour without knowing anything about the variables.
 
I assume you are talking about XMLTools.

Did you download XMLTools 2.0. package or XMLTools installer only?
If the latter, then you'll have to download the complete package and check XMLTools_Examples.pdf.
Install LocalVarsLogger.xml and XMLEventsLogger.xml gauges following pdf instructions.
Then read the documentation to understand how they work.

Tom
 
Thanks, but unfortunately I get a "serious error" in panel.dll and fsx crashes when xmltools is installed. But never mind. I am looking into a different solution now.
 
ti_dabbelju said:
Thanks, but unfortunately I get a "serious error" in panel.dll and fsx crashes when xmltools is installed. But never mind. I am looking into a different solution now.
Click to expand...

That happened because you didn't copy XMLTools folder (which contains the gauges) in FSX's Gauges subfolder. It is clearly descripted in the .pdf documentation.

federicosucari said:
Tom, does your tool read internal XML L:Vars from any addon?
Click to expand...

Yes Federico, it can detect XML, Modeldef (.MDL) and C-gauge defined LVars, even those created at runtime.

Tom
 
  • Like
Reactions: fs1
You must log in or register to reply here.
Back
Top