@BARTnFOCUS, please do not post multiple topics on the same problem. I have hidden your other two posts.

12 hours ago, byork said:

Hmmm, what's the path to your EXE.xml?

We're accounting for both Microsoft Store and Steam versions as far we know, but who knows with MSFS if there's some other path to the EXE.xml that we're missing.

Please let me know your exact path so we can cross check it.

Guys, also to help me trouble shoot what's happening for you regarding the Command Center (I suspect it's simply a case of the Command Center not auto starting via your EXE.xml), but please do this:

Manually start the FS2Crew Command Center.

It's located here:

C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe

Then try to run the FS2Crew Command Center via the Toolbar.

Let me know what happens then.

If it still doesn't work, you can still start FS2Crew FBW or PBE manually via the desktop icon.

But let me know anyway.

Thanks,

Hi,

My path is exactly the same as that described by palvarez &, like him, mine is an original purchase from the Microsoft Store - in fact I've never used any Steam programs.

In addition, I, too, have an exe.xml with FS2 Crew Command Center in the same /Roaming/ path.

Hope that helps? 

Byork

1. Ok, when I manually entered the entry you described above into my EXE.xml,  the command center finally worked in the toolbar as advertised. Thanks!

2. As to the other EXE.xml file located in AppData\Roaming\Microsoft Flight Simulator\EXE.xml, is this a file created by your installer? If so, should we delete so it does not create any future conflict? 

Edited August 15, 20214 yr by palvarez

9 hours ago, BARTnFOCUS said:

I cant even get the setup exe to start. Anybody have any issues getting the setup to even start?

What's the name of the EXE you're trying to run?

If you installed the Command Center separately, it's a silent install.

But if you ran the setup file for FBW A32NX, then it installs the command center automatically.

 

1 hour ago, palvarez said:

1. Ok, when I manually entered the entry you described above into my EXE.xml,  the command center finally worked in the toolbar as advertised. Thanks!

2. As to the other EXE.xml file located in AppData\Roaming\Microsoft Flight Simulator\EXE.xml, is this a file created by your installer? If so, should we delete so it does not create any future conflict? 

In these cases, I believe our setup didn't located (or failed locating) your MSFS's EXE.XML file as a result the Command Center's executable wasn't started during MSFS's startup.

Cheers,

Manuel

Edited August 15, 20214 yr by Manuel82

Manuel, my exe.xml is in the path stated in previous notes, but, for your information, I neither have the FS2020 online version or the Steam version. My version of FS2020 is the CD version. (I don't think this shouldn't be the culprit, though)

1 hour ago, palvarez said:

Byork

1. Ok, when I manually entered the entry you described above into my EXE.xml,  the command center finally worked in the toolbar as advertised. Thanks!

2. As to the other EXE.xml file located in AppData\Roaming\Microsoft Flight Simulator\EXE.xml, is this a file created by your installer? If so, should we delete so it does not create any future conflict? 

Yes, you should delete that that 2nd one.

The question on our end is why did our program install it there in the first place.
 

Please send contact me directly.  

If you don't mind, we'd need your assistance in helping us figure out what that happened.

Our program is smart in the sense that it supposed to detect what version of MSFS you have installed, etc., but obviously something got tripped up somewhere.

22 minutes ago, hvw said:

Manuel, my exe.xml is in the path stated in previous notes, but, for your information, I neither have the FS2020 online version or the Steam version. My version of FS2020 is the CD version. (I don't think this shouldn't be the culprit, though)

Well, MSFS has different paths for it's main directory, following is a table of all different versions MSFS has according to what version you bought:

MS Store Version:
C:\Users\<Your username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\

Steam Version:
C:\Users\<Your username>\AppData\Roaming\Microsoft Flight Simulator\

DVD Version:
C:\Users\<Your username>\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\

Alpha Version:
C:\Users\<Your username>\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\

As you can see DVD version may have a different name, I can't confirm, but as to our earlier researches it (in theory) should be like that. My version is the MS Store one.

Sooo... in theory our setup may has failed to recognize/find where your main MSFS path is located, and thus failed to modify the EXE.XML, that's my theory.

Cheers,

Manuel

Edited August 15, 20214 yr by Manuel82
Added more comments

16 minutes ago, Manuel82 said:

DVD Version:
C:\Users\<Your username>\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\

This folder does not exist in my system. However, as I installed FS2020 on my D drive, there is this folder: D:\WpSystem\S-1-5-21-3636314647-3781228133-215861405-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache where already an exe.xml (for fsuipc) resides. 

Would it be advisable to copy the content of FS2Crew's exe.xml into this here exe.xml file and give it a try?

16 minutes ago, hvw said:

This folder does not exist in my system. However, as I installed FS2020 on my D drive, there is this folder: D:\WpSystem\S-1-5-21-3636314647-3781228133-215861405-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache where already an exe.xml (for fsuipc) resides. 

Would it be advisable to copy the content of FS2Crew's exe.xml into this here exe.xml file and give it a try?

I really don't recommend to copy and paste/overwrite your existing's FSUIPC exe.xml file, as it has more stuff in it. You just need to add the entry to your existing FSUIPC exe.xml maybe (But first backup your existing exe.xml before modifying it.

It's a really weird path, as I can see. "D:\WpSystem\S-1-5-21-3636314647-3781228133-215861405-1001" mainly the "S-1-5-21-3636314647-3781228133-215861405-1001" is that how exactly appears in your machine?...it seems a regedit user's ID or something (ehhehe), first time I see it (..it's as to what this phrase says: "we learn something new everyday"). Don't get me wrong, I'm referring to me, I never saw a path like that before.

This is the entry that you need to add to your existing one:

  <Launch.Addon>
    <Name>FS2Crew Command Center</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path>
    <CommandLine></CommandLine>
  </Launch.Addon>

Cheers,

Manuel

Edited August 15, 20214 yr by Manuel82

15 minutes ago, Manuel82 said:

I really don't recommend to copy and paste/overwrite your existing's FSUIPC exe.xml file, as it has more stuff in it. You just need to add the entry to your existing FSUIPC exe.xml maybe (But first backup your existing exe.xml before modifying it.

It's a really weird path, as I can see. "D:\WpSystem\S-1-5-21-3636314647-3781228133-215861405-1001" mainly the "S-1-5-21-3636314647-3781228133-215861405-1001" is that how exactly appears in your machine?...it seems a regedit user's ID or something (ehhehe), first time I see it (..it's as to what this phrase says: "we learn something new everyday"). Don't get me wrong, I'm referring to me, I never saw a path like that before.

This is the entry that you need to add to your existing one:

  <Launch.Addon>
    <Name>FS2Crew Command Center</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path>
    <CommandLine></CommandLine>
  </Launch.Addon>

Cheers,

Manuel

Bad news. Didn't work 😞 

Can you show up your exe.xml content? Just to check if something is missing?....also after modified exe.xml you need to restart msfs as if you are doing the change directly while msfs is running it wouldnt have any effect. Just wanted to ensure that also.

Cheers,

Manuel

22 minutes ago, Manuel82 said:

Can you show up your exe.xml content? Just to check if something is missing?....also after modified exe.xml you need to restart msfs as if you are doing the change directly while msfs is running it wouldnt have any effect. Just wanted to ensure that also.

Cheers,

Manuel

But of course I restarted FS2020 after modifying the exe.xml 🙂 

This is the content of the exe.xml that was created by installing FS2Crew:

<?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>FS2Crew Command Center</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path>
    <CommandLine></CommandLine>
  </Launch.Addon>
</SimBase.Document>