20 hours ago, rjack1282 said:

Can someone more familiar with this file please review and let me know why none of the programs listed are starting with MSFS.  Thank you.

 

<CommandLine/></CommandLine>

These are all wrong. The syntax is incorrect (the / at the end of the opening tag), and they will destroy the XML 


either remove them (they are not required, especially when they are empty anyway)
or correct them <CommandLine></CommandLine>

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>exe.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>H:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FS2Crew Command Center</Name>
        <Disabled>False</Disabled>
        <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine></CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>E:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FSRealistic</Name>
        <Disabled>false</Disabled>
        <Path>H:\FSRealistic\FSRealistic.exe</Path>
    </Launch.Addon>
</SimBase.Document>

 

For completeness sakes, yes, a single <CommandLine/> would also be correct XML syntax. But the situation in the file of the OP looks like those were present in the first place - and then "something" that doesn't understand XML changed them to the incorrect syntax. No knowing what that was, I would just remove them entirely or use the "full" syntax.

Edited August 21, 20223 yr by Lorby_SI

1 hour ago, Lorby_SI said:

hese are all wrong. The syntax is incorrect (the / at the end of the opening tag), and they will destroy the XML 

You are an absolute legend.  Thank you so much...it is working now.

Well I spoke too soon.  The programs loaded on the first sim start but have failed to load on subsequent starts.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>FenixA320</Name>
    <Disabled>False</Disabled>
    <Path>H:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FS2Crew Command Center</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path>
     </Launch.Addon>
  <Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>FSUIPC7</Name>
    <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
    <NewConsole>False</NewConsole>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSRealistic</Name>
    <Disabled>false</Disabled>
    <Path>H:\FSRealistic\FSRealistic.exe</Path>
  </Launch.Addon>
  <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>E:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
</SimBase.Document>

I have no idea what I'm doing but observed <NewConsole>False</NewConsole> getting adding to the FSUIPC section even after I have deleted it.  With it removed all programs start but that line gets added and then on subsequent starts no programs load.  I delete that line and all programs will again start on one startup.

Your FSUIPC problem could be that you're missing this line:

<CommandLine>-auto</CommandLine>
        

Note the minus sign (or hyphen).

    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine>-auto</CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
    

 

On a sidenote, I've been using Addons Linker from day one. It's an *amazing* utility and I wouldn't dream of running MSFS without it.

Edited August 21, 20223 yr by Adamski_NZ

On 8/21/2022 at 9:40 PM, rjack1282 said:

I have no idea what I'm doing but observed <NewConsole>False</NewConsole> getting adding to the FSUIPC section even after I have deleted it.  With it removed all programs start but that line gets added and then on subsequent starts no programs load.  I delete that line and all programs will again start on one startup.

Sorry, I'm not using FSUIPC. Sounds weird though, obviously "something", maybe FSUIPC itself, is constantly checking the exe.xml and altering it to how it thinks that it has to be - and it is wrong. You should inform the author of FSUIPC, so they can correct their app.

Another option would be to set up the exe.xml just right and then set it to read-only in the file properties.

But this could still be an encoding issue. You should check if the file encoding has changed after this line has magically been added. Because normally the line is correct syntax for an exe.xml in the legacy sims. 

Edited August 23, 20223 yr by Lorby_SI

Good find, I suffer from the same since an unknown timepoint and had no clue, why exe.xml did not work. Have to check semantics obviously

Ok, not entirely successful. I realized that my exe.xml was a total mess up, parts of simconnect.xml seem to have miracously moved over. I tried to correct it on my own, but the only addon that is starting now is FSUIPC7. Can someone have a look:

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>exe.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>      
    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>D:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>D:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>D:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine>-auto</CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
    </SimBase.Document>

To me, no obvious error visible, yet only FSUIPC7.exe gets executed...

Edited August 26, 20223 yr by AnkH

Hmmmm ... I pasted it into a fresh Notepad++ xml file and checked it through. You might want to get the "Snippets" plugin for it, as it will format and syntax/highlight your code for you. If you place your cursor on the opening tag it will automatically highlight the corresponding close tag. If they don't match, one of them won't get highlighted.

Anyway ... I couldn't see anything wrong in the XML, so I suspect it must be one of your addons. Are the paths correct? Try removing all the Launch.Addon sections and adding them back, one by one - until you find the culprit. My money is on the Couatl addon 😉

BTW - it helps readability if you paste XML here using the "<>" code function (and selecting XML in this case), like so ...

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>exe.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>      
    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>D:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>D:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>D:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine>-auto</CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
</SimBase.Document>

Then it's all nicely indented/formatted.

Edited August 26, 20223 yr by Adamski_NZ

Ok... but what I do not get is why it is starting up FSUIPC each and everytime correctly? I mean, this is the last one on the list, or is the .xml executed from bottom to top? Of course I double checked the paths, they are correct. I even changed the .exe files to be executed as administrator. No avail, the only thing that works is FSUIPC. 

10 minutes ago, AnkH said:

Ok... but what I do not get is why it is starting up FSUIPC each and everytime correctly? I mean, this is the last one on the list, or is the .xml executed from bottom to top? Of course I double checked the paths, they are correct. I even changed the .exe files to be executed as administrator. No avail, the only thing that works is FSUIPC. 

I think we are just going to have to wait until Asobo fixes this issue.  I saw you and Umberto's posts over on the FSDT forums and the links to official MSFS forums and I don't think there is a way around it at the moment.  I have tried single entries with just Coautl, FS2Crew, Fenix, etc. with different encodings making sure the syntax was perfect and still could not get programs to open. It has been literally hit or miss with the exact same exe.xml file.  

It is not working at all you/we have to wait until MS/Asobo comes up with a fix - this is a long know issue !

cheers 😉

4 hours ago, AnkH said:

Ok, not entirely successful. I realized that my exe.xml was a total mess up, parts of simconnect.xml seem to have miracously moved over. I tried to correct it on my own, but the only addon that is starting now is FSUIPC7. Can someone have a look:

<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>exe.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>      
    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>D:\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>D:\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>D:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine>-auto</CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
    </SimBase.Document>

To me, no obvious error visible, yet only FSUIPC7.exe gets executed...

The one thing I notice is that the path for FSUIPC does not contain spaces, but the paths for the other items (that are not working) do contain spaces. Perhaps try enclosing the paths for the items with spaces inside double quotes, like this:

<Path>"D:\Addon Manager\couatl64\couatl64_MSFS.exe"</Path>

No idea if that will work or not, but worth a try...

...jim

 

It does nothing pro or contra starting up those two .exe files. However, after several starts of MSFS the last few hours, I can say that FSUIPC7.exe is started up each and everytime correctly, not a single time it did not start up, while neither Couatl nor Fenix apps did start. So honestly, either FSUIPC7.exe does something completely different or the issue lies within Couatl and Fenix executables, although the devs of them insist it is not their fault.

The last thing I am going to try now is adding this manual load false section, as such that the FSUIPC section and the others are identical (except the <CommandLine>-auto</CommandLine> ) syntax.

Edited August 27, 20223 yr by AnkH

I'm not using FSUIPC, and my exe.xml is starting all apps fine

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>exe.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>FenixA320</Name>
    <Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    <Disabled>False</Disabled>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Couatl</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
  </Launch.Addon>
</SimBase.Document>

So that would be another test - remove the entire FSUIPC section and try again. Just to make sure about who is to "blame".

Also remember that if apps are set up so they need Administrator privileges, you have to start MSFS "As Administrator" too. Otherwise the sim will not have sufficient privileges to run the other apps.

Edited August 27, 20223 yr by Lorby_SI