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

Source to change exe.xml

Messages
150
I was trying to see how FSX reacts to an application declared in the exe.xml (BTW it seems that there are again a lot of addons using dll, can't understand why with this new facilitiy) and en up doing a small managed code to be called by a setup package and taking care of the exe.xml (or dll.xml)

It's a vs2005 project

José
 

Attachments

and the conclusion is that it react in a different way from launching as a regular process. Now I have to find why.

José
 
exe.xml

Hi J.C.,

I was just looking at the same thing and I agree with you that this is the way to go developing new add-ons.

I put this exe.xml file in my AppData/Roaming/Microsoft/FSX directory:

Code:
<?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>True</Launch.ManualLoad> 
- <Launch.Addon>
  <Disabled>False</Disabled> 
  <ManualLoad>False</ManualLoad> 
  <Name>InnerGears</Name> 
  <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\InnerGears\InnerGears.exe</Path> 
  <CommandLine /> 
  <NewConsole>True</NewConsole> 
  </Launch.Addon>
  </SimBase.Document>

And it seems to work fine. I guess I should turn off the debugging stuff, but other than that?

What did you mean when you said, "it react in a different way from launching as a regular process."?

Thanks,
FlapsOut
 
Last edited by a moderator:
I have been using exe.xml with 3wirex for a while. Only difference is all console output appears in the SimConnect console, and the application path is not the location of the exe, but the location of FSX. Just have to be careful with references to external files.
 
Noticed 2 things:

Working dir is the FSX dir;

When FS crash the ReceiveMessage doesn't return an exception;

José
 
Back
Top