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

XMLTOOLS for FSX and P3D updates

taguilo

Resource contributor
Messages
1,585
Country
argentina
Guys,

XMLTools v2.01 for FSX and XMLTools3D for P3D v3.x are now availables in the Resources pages.

Auto/manual installation supported.

History:

XMLEVENTS V1.1: Bug correction for negative values improperly returned
SIMVARS V1.1: Added Pause and Sound status detection.

Both also include a pdf example on how to call the classes from a C++ gauge.

Have fun!

Tom
 

Heretic

Resource contributor
Messages
6,830
Country
germany
On one hand: Yay, thanks!

On the other hand: So many manuals to update with up-to-date links. Urgh!


- Edit:

Is the P3D v3 version backward compatible?
 
Last edited:

taguilo

Resource contributor
Messages
1,585
Country
argentina
Is the P3D v3 version backward compatible?

I believe it is. SIMVARS is the only class that depends on Simconnect, which compiles with a version dependent lib, so the other ones must work fine (and SIMVARS probably too).

Tom
 

Heretic

Resource contributor
Messages
6,830
Country
germany
I've tried to use the new "pause" status variable in a project, but both (C:SIMVARS:Pause State,Enum) 1 != and (C:SIMVARS:Pause State,Enum) 0 == do not work.
Same for (C:SIMVARS:Current View Mode,Enum) and (C:SIMVARS:Sound State,Enum).
XMLTools otherwise works perfectly.

This is the same malady that has befallen Doug Dawson's sound gauge.

I'm suspecting FSX:Steam as the culprit, although I do have all available SimConnect versions installed.
 

taguilo

Resource contributor
Messages
1,585
Country
argentina
All three work fine for me.
Could you check you XMLTools.dll version in FSX:STEAM folder? It should say v2.01 version in DLL file properties.

Tom
 

Heretic

Resource contributor
Messages
6,830
Country
germany
I use an external folder for my FSX Modules and adapt my dll.xml accordingly.
The version number is correct.


And testing the variables with another model, they do seem to work for alright. Don't know what went wrong before. Weird.
 
Last edited:

Heretic

Resource contributor
Messages
6,830
Country
germany
Would it be possible to implement a "value hold" function into XMLTools (actually just SIMVARS)?

Consider the following scenario:
I'm using SIMVARS to overwrite, e.g. (A:GENERAL ENG EXHAUST GAS TEMPERATURE:1, celsius). Said simulation variable is driving a 3D modeled EGT needle. The code for overwriting the simvar is called from a 2D gauge, running at 18 Hz. The VC model is refreshed at 30 Hz. After every 2D update cycle, the simvar will be updated via XMLTools from the 2D gauge. Between these update cycles, the simvar will be updated by FSX flight dynamics engine. The result is a twitching needle and the effect becomes uglier, the larger the difference between the value of (C:SIMVARS:GENERAL ENG EXHAUST GAS TEMPERATURE:1, celsius) and (A:GENERAL ENG EXHAUST GAS TEMPERATURE:1, celsius) is.

Since I assume that XMLTools is refresh at the same rate as all the other simulator modules, would it therefor be possible to bridge the gap between 2D panel update cycles with the last known value for a variable updated by SIMVARS? This could maybe be done by comparing the retrieved value of the second last 2D refresh cycle with the one from the last 2D refresh cycle and only updating them if the values differ.
To declare that a variable modified via SIMVARS will take precedence, there could be maybe something akin to the "key capture on" vatriable for XMLKEYS.
 
Messages
371
Country
france
Hello Tom,

I use XMLTools since 3 years without any problem.

But I just installed on my laptop Windows 7 32b (previously XP), FSX SP2.

Curiously, XMLTools 2.0 or 2.01 doesn't work.

I did the correct declaration in dll.xml :

<Launch.Addon>
<Name>XMLTools</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>XMLTools.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

When I launched FSX, XMLTools is correctly detected (I have got the 2 message box about trusted software). FSX has added the XMLTools declaration in the FSX.cfg TRUSTED section (ending by "=1"

I use only XMLVars code in my gauges and nothing work. (panel works on my home computer).

- I updated VCRedist x86 by lastest version 2017
- I set Windows security at the lowest level
- I run FSX in administrator mode
- I patched UIAutomationcore.dll

I don't understand. If someone has an idea......

Thank you very much
 
Messages
371
Country
france
Hello Tom,

Sorry for the delayed feedback.

I had only VCRedistribuables 2017 installed and I thought that it will be adequates.

I have installed VCRedistribuable 2010 and now all works fine :)

Note : Before installing VCRedist 2010, I tried your installer and it crashed.

It seems that Installer cannot work if ther is a post 2010 version of VCredist installed on the computer.

Thanks

Francois
 

Kekelekou

Resource contributor
Messages
226
Country
france
After every 2D update cycle, the simvar will be updated via XMLTools from the 2D gauge. Between these update cycles, the simvar will be updated by FSX flight dynamics engine. The result is a twitching needle

Oh boy, I am planning for my BN2 damage mod to use XMLTools in order to hijack the RPM calculations and force a sluggish engine response to throttle inputs on a cold engine.
So I am going to check if I experience the same issue. And if so, second Björn's request. :)
 

Heretic

Resource contributor
Messages
6,830
Country
germany
Not sure if it'll work for pistion engines as well, but I recently found out that restricting fuel flow to the engine avoids twitching RPM, EGT, etc...needles while making the engine do what I want.

Having a poissibility to only influence a specific variable, however, would be nice.
 

taguilo

Resource contributor
Messages
1,585
Country
argentina
Would it be possible to implement a "value hold" function into XMLTools (actually just SIMVARS)

Bjöern,
I understand what you mean. Actually to solve that issue I do not read the AVar but instead write my custom value to the CVar and an LVar, and that one is used in the Moldelfef (where CVars are not supported); for 2D panels reading the CVar directly works fine.

Anyway, I need to take a look to other problems in XMLTools (x64 version as well) so hope to have time to do that soon, and I will check this issue to see if it can be improved.

Tom
 

Heretic

Resource contributor
Messages
6,830
Country
germany
I understand what you mean. Actually to solve that issue I do not read the AVar but instead write my custom value to the CVar and an LVar, and that one is used in the Moldelfef (where CVars are not supported); for 2D panels reading the CVar directly works fine.

Anyway, I need to take a look to other problems in XMLTools (x64 version as well) so hope to have time to do that soon, and I will check this issue to see if it can be improved.

Yeah, custom L: vars are the ideal solution, but not an option at all if you don't have access to the source file.

One other issue with XMLTools is that the pause and view mode detection stops working after several aircraft reloads.
 

Kekelekou

Resource contributor
Messages
226
Country
france
My idea was to control engine RPM, but it seems that the only RPM that can be accessed through XMLTools are the propeller's ones.
Tom, any chance that engine RPM will be added to the C:SIMVARS? Not requesting anything, just asking so that I don't waste time working on something that just can not work (since some A:vars can't be controlled externally).

So I might have to go down the fuel flow route anyway. Thank you Heretic for suggesting that.
 

Heretic

Resource contributor
Messages
6,830
Country
germany
Manifold pressure and brake power are settable via SimConnect Not sure if they'll have the desireable effect though.
 

ddawson

Resource contributor
Messages
862
Country
canada
Manifold pressure and brake power are settable via SimConnect Not sure if they'll have the desireable effect though.
They are both continually updated by the sim; they will operate in the same way as you described in post #8.

Doug
 
Top