TDS Sim Software Forums

(05-31-2022, 04:17 PM)admin Wrote: [ -> ]Thank you for your input, we will look into it.

Related to this...have you ever come across any instances of the installer NOT entering any data into the exe.xml file?

I've had the TDS unit for several months now, and thru each version it has never modified the exe.xml file.  On my system, the exe.xml file is not write protected (at least it's not showing that in the Properties dialog), and I have UAC disabled.

---

Also, what actually updates the /Community/tds-gtnxi-gauge folder? The installer?

I updated my TDS unit to the latest this evening, and yet my /Community/tds-gtnxi-gauge folder still has a 4/27/2022 timestamp, and within manifest.json it says 1.0.2 as the package version.

The WASM file gets updated: TDSGTNXiGaugeModule.wasm

Located here: Community\tds-gtnxi-gauge\Gauge
Please let us know if it is dated end of May 2022

It is dated the end of May 2022.

But you know what I found out? My exe.xml file was not properly formatted. A WORD OF WARNING to everyone who reads this thread -- MAKE SURE your exe.xml file is in the proper format. Here's what mine looked like -- and this is wrong:

<Launch.Addon>
<Name>AFCBridge</Name>
<Disabled>False</Disabled>
<Path>E:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>TDS Sim Software GTNXi Gauge Integration</Name>
<Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
<CommandLine>-FSIntegration</CommandLine>
<NewConsole>True</NewConsole>
</Launch.Addon>

Here is what a proper exe.xml file SHOULD look like:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>

<Launch.Addon>
<Name>AFCBridge</Name>
<Disabled>False</Disabled>
<Path>E:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>TDS Sim Software GTNXi Gauge Integration</Name>
<Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
<CommandLine>-FSIntegration</CommandLine>
<NewConsole>True</NewConsole>
</Launch.Addon>

</SimBase.Document>


Notice how it has the xml version header and the SimBase tags. Yeah, I have no idea how my exe.xml ended up so wrong, but it was. So hopefully this will help someone else having trouble with the exe.xml. Look at the file itself. MSFS wasn't even reading mine. Now my Honeycomb Bravo lights even work!

(06-04-2022, 04:57 AM)Mace Wrote: [ -> ]It is dated the end of May 2022.  

But you know what I found out?  My exe.xml file was not properly formatted.  A WORD OF WARNING to everyone who reads this thread -- MAKE SURE your exe.xml file is in the proper format.   Here's what mine looked like -- and this is wrong:

 <Launch.Addon>
   <Name>AFCBridge</Name>
   <Disabled>False</Disabled>
   <Path>E:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>TDS Sim Software GTNXi Gauge Integration</Name>
    <Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
    <CommandLine>-FSIntegration</CommandLine>
    <NewConsole>True</NewConsole>
  </Launch.Addon>

Here is what a proper exe.xml file SHOULD look like:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>

<Launch.Addon>
<Name>AFCBridge</Name>
<Disabled>False</Disabled>
<Path>E:\MSFS\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>TDS Sim Software GTNXi Gauge Integration</Name>
<Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
<CommandLine>-FSIntegration</CommandLine>
<NewConsole>True</NewConsole>
</Launch.Addon>

</SimBase.Document>


Notice how it has the xml version header and the SimBase tags.  Yeah, I have no idea how my exe.xml ended up so wrong, but it was.  So hopefully this will help someone else having trouble with the exe.xml.  Look at the file itself.  MSFS wasn't even reading mine.  Now my Honeycomb Bravo lights even work!

Thank you for finding this problem and for posting it here, hopefully it will help others.
The TDS GTNXi correctly writes the header with the SimBase properties, so it must be another add-on that is wrongly creating this file.

Oh yes, it was definitely another add-on that wrongly created / modified the exe.xml...because I've had this problem for over a year, way before I had the TDS GTN.

I saw the interaction between you and Viking01 earlier in this thread about the exe.xml and it got me thinking...Thank you for getting my brain on the right path.