06-04-2022, 04:57 AM
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!
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!