GSX Pro not showing up in Toolbar - installer updates 2020 not 2024?

[robains]

MSFS 2024 SU2

GSX Pro installed and active v3.5.6

Tried running couatl64_boot.exe ... shows up in SysTray - About shows 5.0

Then start MSFS 2024 (Steam version), enter EGLL and flight.  Bring up the MSFS Toolbar and no GSX icon?

Checked EXE.XML for MSFS 2024 and there is no entry for Couatl?

<SimBase.Document Type="SimConnect" version="1,0">
<Descr>Auto launch external applications on MSFS start</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.Addon>
<Name>FSL Control Center</Name>
<Disabled>False</Disabled>
<Path>C:\FlightSimLabs\ControlCenter\FSLControlCenter.exe</Path>
<CommandLine>-NOTIFY</CommandLine>
</Launch.Addon>
</SimBase.Document>

HOWEVER, I checked the EXE.XML for MSFS 2020 and the entry exists:
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_boot.exe</Path>
</Launch.Addon>
</SimBase.Document>

In the FSDT Universal Installer I have 2024 Steam and  Release Channel selected but it seems it did NOT update the correct sim.  When 2024 was selected it updated 2020??

I enabled logging per manual in Couatl_MSFS.INI:

useAirportCache=0
logFile=”couatl.log”

can't find any log?

There is a couatl64_boot.log with limited info Attached file:

6/12/2025 10:55:00 PM: Couatl64_boot Log started
6/12/2025 10:55:00 PM: Working folder set to C:\Program Files (x86)\Addon Manager\couatl64 according to FSDT registry root key
6/12/2025 10:55:00 PM: Thread "couatl64_MSFS.exe"  added to monitoring
6/12/2025 10:55:00 PM: MSFS has quit
6/12/2025 10:55:00 PM: EXCEPTION Object reference not set to an instance of an object.
6/12/2025 10:55:01 PM: Waiting to connect to Couatl64 shared memory
6/12/2025 10:55:02 PM: Waiting to connect to Couatl64 shared memory
6/12/2025 10:55:03 PM: Waiting to connect to Couatl64 shared memory
6/12/2025 10:55:04 PM: Waiting to connect to Couatl64 shared memory

As you can see there is an exception.

I have P3D, MSFS, and MSFS 2024 installed ... should it be trying to load "couatl64_MSFS2024.exe" when I run MSFS 2024 ... why is it loading couatl64_MSFS.exe?

Rob

[virtuali]

It's not clear if you enabled GSX in MSFS 2024 as well.

When you install GSX, and you have more than one version of MSFS installed, it won't automatically be enabled in both, it will be enabled only on the simulator you had selected when you performed the installation. To activate into the other sim, select it first from the drop-down menu, and click RELINK, so it will now show installed in both.

[robains]

And that's the bug on a "default" install (no prior versions of GSX on the computer but with MSFS 2020 and MSFS 2024 installed).  After installer completes, it defaults to 2024 Steam Release Channel (per my original post): 

In the FSDT Universal Installer I have 2024 Steam and  Release Channel selected but it seems it did NOT update the correct sim.

I activate with my key, but it installs into MSFS 2020 NOT what I selected from the dropdown (2024).



Also notice at the bottom of your installer it's showing MSFS 2020 folder path even when I have 2024 Steam selected.

So on initial load of the installer, it's defaulting the dropdown to 2024, but installing to 2020 and/or thinks I'm using 2020.

On a side note: SimBrief connection doesn't seem to work.  I enter my correct "Alias" but when I try to load ReLoad SimBrief it just comes back with HTML error message.  I know it's the correct Alias but I have it working in JF Tomahawk EFB in MSFS 2024.  But JF require UserId and Password in order to connect to SimBrief, but you only seem to require the Alias?? (don't see how that is going to be valid credential set)

[virtuali]

And that's the bug on a "default" install (no prior versions of GSX on the computer but with MSFS 2020 and MSFS 2024 installed).  After installer completes, it defaults to 2024 Steam Release Channel (per my original post): 

There's no "bug", it defaults to what it finds on your system.

In the FSDT Universal Installer I have 2024 Steam and  Release Channel selected but it seems it did NOT update the correct sim.

yes, it does. I see the drop down is active, which means it has detected TWO MSFS installed, do you see the same community folder for both ? Different ?

Also notice at the bottom of your installer it's showing MSFS 2020 folder path even when I have 2024 Steam selected.

There must be a problem with your installation, possibly a remnant of an old MSFS 2020 install, the installer searches in two very different folders, so it cannot confuse 2020 with 2024 ( nobody ever reported this before, and having just MSFS 2024 for Steam installed is a common case ). The file it looks for is the UserCFG.OPT file and in Steam it's located here:

%APPDATA%\Microsoft Flight Simulator
%APPDATA%\Microsoft Flight Simulator 2024

So, maybe your UserCFG.OPT file for 2024 is pointing to the 2020 Community.

On a side note: SimBrief connection doesn't seem to work.  I enter my correct "Alias" but when I try to load ReLoad SimBrief it just comes back with HTML error message.  I know it's the correct Alias but I have it working in JF Tomahawk EFB in MSFS 2024.  But JF require UserId and Password in order to connect to SimBrief, but you only seem to require the Alias?? (don't see how that is going to be valid credential set)

Yes, it's the Alias, and it works. And yes, there's no need for a password, since the only thing GSX takes from Simbrief is your last generated flight. That one doesn't require a password, but it only lasts for a limited time so, if you either haven't generated a plan, or it expired, it will give you an error.

[robains]

As you can see the package paths are different and correct.

C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator
UserCfg.opt
InstalledPackagesPath "C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator\Packages"

C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024
UserCfg.opt
InstalledPackagesPath "C:\Users\robai\AppData\Roaming\Microsoft Flight Simulator 2024\Packages"

As far as SimBrief, thanks for the clarification. Will future versions of GSX Pro allow for more than just the last flight?
 

[virtuali]

Do you maybe have another installation in another user account ?

[robains]

No, I’m the only account.

The dropdown that selects the sim seems to be the issue on initial start of your Installer.

I was able to resolve by copying the MSFS 2020 Coualt entry in the EXE.XML to the MSFS 2024 EXE.XML and then do a “Re-Link” via your Installer.

Anyway, just wanted to report this issue and steps to replicate:
1.  Clean PC with NO prior versions of GSX or MSFS 2020 or MSFS 2024
2.  Install MSFS 2020
3.  Run MSFS 2020 at least once to get it setup.
4.  Install MSFS 2024
5.  Run MSFS 2024 at least once to get it setup.
6.  Buy and install GSX Pro for 2020/2024
7.  Once install completes do NOT click on the drop down that selects MSFS version … leave it at “2024 Steam Release” (the default).
8.  Activate (enter activation key code)
9.  Run MSFS 2024 — there will be NO menu for GSX
10.  Run MSFS 2020 - there will be a menu for GSX

Important that NO prior versions of GSX Pro or MSFS 2020/2024 exist on your test computer.  Also Step 7 is VERY important to replication of issue.

Hope that helps,
Rob.