Couatl starts manually, but not automatically with the simulator

[maorgr]

Hi virtuali,

for quite sometime Couatl64_MSFS.exe won't auto load neither by modifying exe.dll or copying a shortcut of it to the start up folder in windows or even using FSUIPC7.ini RunIf2=READY,KILL,"C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe"

GSX PRO is updated to the latest version.

Can you please help ?

Thanks in advance,

Maor

[virtuali]

Have you tried this ?

If you Unlink GSX Pro ( choose Uninstall, but only Unlink, don't uninstall ) then Relink again, it will try to add the exe.xml lines back.

In addition to trying to put back the lines that might be eventually missing, it will tell you if your exe.xml has problems, because it's validated before trying to do any changes to it.

[Ankh]

Ok, I found another "solution" to the problem of executables listed in the exe.xml file not being executed when firing up MSFS, including Couatl, and it is definitively contra-intuitive: you need to modify your .exe properties as such as that it is NOT(!) started as administrator. The moment I removed the checkmark for Couatl64.exe, it fired up again with MSFS as it should.

So, for anybody still having troubles that Couatl is not automatically started with the sim, try once by disabling the "start as adminstrator" on your Couatl64.exe and see if this cures your issue as well.

BTW: this was posted on Reddit by someone, is not my personal find. But it works on my end as well...

[ANTIOPE]

Good morning
So that Coualt.exe runs automatically when MSFS2020 is launched, I uninstalled GSX and everything it contains and above all deleted all the coualt lines in regedit. Once done I reinstalled GSx and everything works perfectly for me. if that helps!

[virtuali]

it is definitively contra-intuitive: you need to modify your .exe properties as such as that it is NOT(!) started as administrator. The moment I removed the checkmark for Couatl64.exe, it fired up again with MSFS as it should. 

This is well known and by default we never set Couatl64_MSFS.exe to start as Admin, because it's not required, unless in a specific case of users with limited permissions on their Windows account.

[WebMaximus]

I'm having the same issue since some time ago where Couatl won't start automatically with the simulator anymore. Instead I have to remember to launch it manually every time.

I've tried the Unlink-Link suggestion as well as a complete reinstall to no avail. Have not tried yet to manually remove Couatl entries from the Registry.

Any other suggestions before going that route?

[virtuali]

I'm having the same issue since some time ago where Couatl won't start automatically with the simulator anymore. Instead I have to remember to launch it manually every time.

If you have the current version, the Couatl engine won't be started directly by the sim but, instead, the new couatl64_boot.exe will run instead, which will start the Couatl engine itself, and will monitor it for a restart.

[WebMaximus]

If you have the current version, the Couatl engine won't be started directly by the sim but, instead, the new couatl64_boot.exe will run instead, which will start the Couatl engine itself, and will monitor it for a restart.

That sounds all great and I remember now when reading this how I read about the same thing in the release notes. However, I noticed a couple of times now how the GSX window has been completely empty and when checking in the Windows System Tray Bar, I've noticed how Couatl hasn't been running. After starting it manually, the menu has been normally populated again.

Will do some more testing and avoid starting Couatl manually and see if it will still work in the way you describe.

[WebMaximus]

Just did another test and what actually happens is when I try to open GSX via the in-game panel, I get a message telling me the Couatl scripting engine hasn't started.

So looks like this new tech to make it start doesn't work over here. If I start Couatl manually though, all is fine.

[virtuali]

So looks like this new tech to make it start doesn't work over here. If I start Couatl manually though, all is fine.

Before saying that, you should first check if the autostarter is in use to begin with. Check the couatl line in your EXE.XML start this file:

couatl64_boot.exe

And of course, it should not be set to disabled. The updater should have changed the line but, if the exe.xml for any reason restored to a previous version, you are not using the auto-restarter. If your line looks fine, then check if the auto started started in the Task Manager. If it has, check if you have this file:

%APPDATA%\Virtuali\Couatl64_boot.log

[WebMaximus]

Thanks but happy to report how it's working after the latest update.

[Murf]

I don't know what changed, GSX was working fine earlier this week. But now all I get in the sim is the GSX Loading window.... and it never loads up.

Any ideas??? Please keep in mind I am program illiterate!!   

[virtuali]

To exit from the loading loop:

- Close the toolbar menu first

- Choose Restart from the small Couatl icon in the Traybar notification area.

- Wait about 10 seconds before opening the menu again so, don't start immediately.

When you open the menu again, allow it to load, don't open or close it quickly because, if you do that while is still loading (because my 10 seconds might be more on your system), you will make it stuck doing that.

In general, you can reduce A LOT the chance for this to be happening in the first place, if you use the menu as suggested in the manual, that is:

- Open it with the mouse on the toolbar only when you first start GSX, and then close and open it only with the Hotkey.

- Close it from the toolbar only when you are done with GSX, or before ending a flight. This will stop MSFS trying to opening it again on the next start, which increase the chance for the menu to be stuck