In another post I showed how to get the Saitek Pro Flight Instrument Panel going.
Today I was able to work on it again and this is the way the exe.xml file looks now.
<?xml version="1.0"?>
<SimBase.Document Type="Launch" version="1,0">
. . . . . . <Descr>Launch</Descr>
. . . . . . . . . . . . <Filename>exe.xml</Filename>
. . . . . . . . . . . . <Disabled>False</Disabled>
. . . . . . . . . . . . <Launch.ManualLoad>False</Launch.ManualLoad>
. . . . . . <Launch.Addon />
<?This is where I start the Saitek Pro Flight Instrument(s) with Prepar3d?>
. . . . . . <Launch.Addon>
. . . . . . . . . . . . <Name>Saitek DirectOutput RadioStack</Name>
. . . . . . . . . . . . <Disabled>False</Disabled>
. . . . . . . . . . . . <Path>C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe</Path>
. . . . . . <CommandLine>-run</CommandLine>
. . . . . . </Launch.Addon>
<?This is where I set SPAD to start with Prepar3d?>
. . . . . . <Launch.Addon>
. . . . . . . . . . . . <Name>SPAD</Name>
. . . . . . . . . . . . <Disabled>False</Disabled>
. . . . . . . . . . . . <ManualLoad>False</ManualLoad>
. . . . . . . . . . . . <Path>C:\Program Files (x86)\SPAD\SPAD.exe</Path>
. . . . . . </Launch.Addon>
</SimBase.Document>
I'm just playing around with colored text, and hopeing that it'll help you see the elements of XML.
If you double click on the file it'll look like this.
Hopefully, one view or the other will help you understand the structure so you too can make simple changes.
Although I can add OPUS to FSX this way, Opus will make Prepar3d crash when included in the exe.xml file.
If I start OPUS up AFTER P3D has started there's no problem.
BTW XML stands for Extensible Markup Language.
For me it's monkey See, monkey Do. I don't know it, and probably never will.
As used here, it's like the old "ini" files. That much I can understand.
