FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: virtuali on August 25, 2022, 09:39:22 am
-
There's a known bug in MSFS which results in programs started from the EXE.XML file not being launched. It happens to me too, there are several reports on Microsoft forum about this problem, which has been reported since May:
https://forums.flightsimulator.com/t/exe-xml-often-not-starting-addons-correctly/515592/66
Quoting from another user there:
On the GSX forums there are many users saying that Couatl doesn’t start and it’s due to the EXE.XML not starting without them knowing, so they blame GSX. That’s just an example, the same could happen for every single addon based on it.
Quoting from another user there:
On the GSX forums there are many users saying that Couatl doesn’t start and it’s due to the EXE.XML not starting withouth them knowing, so they blame GSX. That’s just an example, the same could happen for every single addon based on it.
This problem has been reported on Microsoft devs forum too, in May:
https://devsupport.flightsimulator.com/questions/8061/exexml-fails-to-launch-my-simconnect-external-appl.html
This reply came directly from Asobo:
That's an issue we're already tracking. It's related to MS Store checking the app (MSFS) has a correct licence but also checking for child apps and failing in this case.
So, clearly a bug, since it seems the MS Store tried to check the license even for child applications, something it shouldn't do.
-
I've had this bug forever, exe.xml usually doesn't work (affects all external execuables that need to be started)
I've made a small batch file to load all the dependencies from the exe.xml in one click. Really easy to do, penty of guidance if you Google 'batch file to start multiple programs' or something like that.
Ive added Couatl to that batch file, ssmeto work fine that way.
IM
-
In the official forum someone basically solved his exe.xml issue by opening the .xml in Notepad++ and forcefully saving the .xml in the UTF-8-BOM encoding. It has to be re-done as soon as anything is changed in the exe.xml by any addon or MSFS itself. So what I really wonder is: how the heck Asobo does not come up with such an easy solution...
-
That was me. Please be aware that although this works for me there’s no guarantee it’s the silver bullet!
One program still refused to run despite changing the encoding so it’s certainly not a 100% fix in any case so I suspect there’s other factors involved and it’s certainly going to be on an individual basis as some users have had no issue with the exe.xml launching add-ons at all.
-
Ok, in another forum, somebody else mentioned wrong semantics in the lines of Aerosoft VDGS, maybe checking this is worth? I think it is in the AS forums... Might be, that you (and me) had a two step issue here, one the wrong encoding and two the wrong semantics for VDGS. Still did not have time to check on my end if the encoding solves my issues, but it is a good starting point.
-
While I think it's possible that in SOME cases the XML file itself might be a problem, there's still an underlying issue with MSFS not loading the file, regardless if it's correct or not, because it's wrongly trying to verify the license also for the child processes, in addition to itself.
Something it cannot be able do, since none of the .exe you'll eventually start from there would use the MS Store license, either because they are freeware (like Honeycomb drivers), or because they have their own licensing system ( Fenix, GSX )
-
I change the encoding in EXE.XML to "UTF-8" and it's been starting every app. Might want to try that. Here's the first line in my file:
<?xml version="1.0" encoding="UTF-8"?>
-
Do you added a BOM or not ?
-
I added BOM at first but MSFS2020 kept giving me CTD so I removed it and used only what you see in my post. Even the Fenix App loads ONLY when I launch a flight using the A320.
-
Ok, I took some second looks into my exe.xml and I realized that it was a complete mess, even the header got mixed up with simconnect.xml, I guess some addon did this corrupting my exe.xml. Now I tried to manually correct the whole .xml, lets see if this works now.
EDIT: not really, FSUIPC7.exe gets started correctly, couatl and Fenix does still not fire up. Funny thing: the couatl task symbol is there, but MSFS still tells me that the engine did not start and I have to manually execute the .exe to get it running. No idea why...
-
cant say anything about the others you had mention but for the fenix app its a know issue that if you start the app first it will work all the time if you dont its a 50 50 chance it will start :)
-
I run MSFS in ADMIN mode and never have a problem with things not auto-starting.
-
That was me. Please be aware that although this works for me there’s no guarantee it’s the silver bullet!
One program still refused to run despite changing the encoding so it’s certainly not a 100% fix in any case so I suspect there’s other factors involved and it’s certainly going to be on an individual basis as some users have had no issue with the exe.xml launching add-ons at all.
Hi,
Where is the location of the xml file please? Getting quite sick of the fact that I have to reboot msfs over and over again because fsuipc has not auto launched (also won’t let me manually launch once msfs has loaded in) I use fsuipc to interact with my VA application. It wouldn’t be so bad if msfs didn’t take 5 mins or so to load in. Never had this issue pre gsx so it’s obviously something with the couatl start up which has changed the xml file causing other apps to not auto start.
-
I change the encoding in EXE.XML to "UTF-8" and it's been starting every app. Might want to try that. Here's the first line in my file:
<?xml version="1.0" encoding="UTF-8"?>
seems to work to me too :)
-
For anyone else reading this, I changed to UTF-8 tonight to cure coualt not starting automatically. For some reason this completely borked by hotas throttle and stick whereby any aircraft didn't react to my inputs. I've just restored the original exe.xml and my hardware is working again.
-
For anyone else reading this, I changed to UTF-8 tonight to cure coualt not starting automatically. For some reason this completely borked by hotas throttle and stick whereby any aircraft didn't react to my inputs. I've just restored the original exe.xml and my hardware is working again.
As explained in the first post of this thread, the issue of add-ons not being started automatically by the EXE.XML, is not really related to an issue related to the EXE.XML encoding.
Sure, if you have a problem with it, it's guaranteed it will not work but, if you read the explanation in the first post carefully, there's another fundamental issue with starting add-ons, that has been confirmed to be a problem in the sim, as indicated in the reply I cited, coming directly from Asobo, and it's caused by simulator trying for some reason to validate the add-ons licenses, something it clearly can't do, not possibly knowing anything about any license requirements of 3rd party add-ons.
MAYBE this could be some kind of derivative bug that, if MSFS has a problem with *its* license, is not supposed to start any add-ons, which seems to be confirmed by the fact that, when the .EXE.XML doesn't seem to start anything, even enabling the Simconnect logging Console results in an unspecified license error.
That is to say than yes, before you have any chance to have the EXE.XML add-ons starting correctly, the EXE.XML must be correct and have the proper encoding, meaning the actual content of the file must match the encoding declaration and, by default, even when an XML declaration is missing, the XML standard dictates the file is assumed to be UTF-8 without BOM, but even if your XML is perfectly fine, there's the OTHER issue explained above.
This SEEMS to have been fixed in SU11 Beta. I'm just starting MSFS again right now while I'm typing this (using the latest SU11 Beta), and my EXE.XML, which has an UTF-8 declaration and NO BOM, started the only two add-ons I have correctly, that is couatl64_MSFS.exe and FenixBootstrapper.exe. To be sure, I tried 3 times in a row, and in all 3 startups, couatl64_MSFS.exe and FenixBootstrapper.exe were correctly shutdown after quitting MSFS, and they were both auto-launched on the following startup so, it seems this might be fixed.
Assuming, of course, the EXE.XML is otherwise correct and doesn't include any errors.
-
An interesting observation on my end: due to a hardware change I did a full re-install of Windows 10 and MSFS last weekend and guess what, this bloody exe.xml suddenly starts up all addon executables including couatl.exe without any hickup every time I fire up MSFS. Even with all my addons back in place, the exe.xml still works as intended. Do not ask me why, because if I compare the "new" and the "old" exe.xml line by line, they look 100% identical.
-
An interesting observation on my end: due to a hardware change I did a full re-install of Windows 10 and MSFS last weekend and guess what, this bloody exe.xml suddenly starts up all addon executables including couatl.exe without any hickup every time I fire up MSFS. Even with all my addons back in place, the exe.xml still works as intended. Do not ask me why, because if I compare the "new" and the "old" exe.xml line by line, they look 100% identical.
Thank you for having confirmed what we already knew it was an issue ( separate from possible "issues" with the EXE.XML itself ) related to some kind of weird Windows/MS Store licensing problem, which was of course already explained in the first post of this thread, and I repeated in my last post.
As I've said, it seems to work much better with the SU11 Beta, previously I was never able to have anything auto-started automatically, and I think this was related to having two MSFS installations ( MS Store and Steam ) with two separate license, on the same PC. Now it always works for me.
-
With SU11, is there anything I can do to make couatl start with MSFS? I'm still having to start it manually.
-
With SU11, is there anything I can do to make couatl start with MSFS? I'm still having to start it manually.
With SU11, it always starts automatically, each time. I never had to start it manually again.
-
Not for me. Looks like more fun troubleshooting MSFS for me.
-
Not for me. Looks like more fun troubleshooting MSFS for me.
SU11 fixed the problem, but this assumes your EXE.XML is clean and not corrupted. Before SU11, it even failed to load EXE.XMLs that were correct, now they work so, check this thread and see if perhaps your EXE.XML has a problem, because if it does, SU11 wouldn't fix anything in that case:
https://www.fsdreamteam.com/forum/index.php/topic,28389.0.html
-
I looked at that thread but don't see that particular issue in my attached exe.xml.
-
I looked at that thread but don't see that particular issue in my attached exe.xml.
Surely there are differences compared to how it's supposed to be, since your file starts with these lines, which are like it used to be an FSX-style exe.xml, apparently some installer has created it as if was in FSX.
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
While the file I posted starts with the correct MSFS-style commands, I've highlighted all the differences:
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
This is how the GSX installer creates the EXE.XML it if no file exists, and it's has been confirmed by Asobo (Boris is an Asobo developer ) it is the correct syntax:
https://devsupport.flightsimulator.com/questions/2191/starting-external-programs-without-using-the-exexm.html?childToView=6873#comment-6873
Note that, f an EXE.XML already exists, the GSX installer will just add its own section to it, without changing anything else.
However, this not being documented anywhere, other than that post on Asobo developers forum, it's not 100% clear what happens if you use the FSX-style syntax, the few tests I made seems to indicate it will be accepted as well, but I have not idea of there are side effects, for example of one of the add-ons in the section use Launch commands only available in MSFS.
Other than that, your file has spaces for indentation, the one I posted has Tabs. Again, not sure if this is a problem or not ( it shouldn't, according to XML standards ), but nobody can be sure of anything.
One thing you haven't said is, are ALL the other programs being started automatically from your EXE.XML, or there are some that don't start as well ? Or it's just Couatl ?
-
One thing you haven't said is, are ALL the other programs being started automatically from your EXE.XML, or there are some that don't start as well ? Or it's just Couatl ?
Just couatl. I tried changing the instances of Launch to SimConnect as you noted with no change.
Then I removed the exe.xml, ran the FSDT installer and unlinked/relinked GSX and it rebuilt the exe.xml to only have couatl (attached). Unfortunately, even that doesn't get it running.
-
Then I removed the exe.xml, ran the FSDT installer and unlinked/relinked GSX and it rebuilt the exe.xml to only have couatl (attached). Unfortunately, even that doesn't get it running.
I can only repeat and confirm it works 100% of the time here. Your file is surely correct now ( since it was created by the GSX installer, you can be sure it is ), so your issue must be something else entirely.
You still haven't answered to my last question, are ALL the other programs being started automatically from your EXE.XML, or there are some that don't start as well ? Or it's just Couatl ?
-
Then I removed the exe.xml, ran the FSDT installer and unlinked/relinked GSX and it rebuilt the exe.xml to only have couatl (attached). Unfortunately, even that doesn't get it running.
I can only repeat and confirm it works 100% of the time here. Your file is surely correct now ( since it was created by the GSX installer, you can be sure it is ), so your issue must be something else entirely.
You still haven't answered to my last question, are ALL the other programs being started automatically from your EXE.XML, or there are some that don't start as well ? Or it's just Couatl ?
Couatl is the only one that won't start. I just tried another fresh exe.xml with just couatl and it didn't start. Then I swapped in FSUIPC in that same file and it started fine.
-
Hello, I have exactly the same problem. Everything lance nickel, except couatl
-
Yep latest updates coutal wont start and now i get that couldnt find valid afcad date for airport, services not available.
-
Yep latest updates coutal wont start and now i get that couldnt find valid afcad date for airport, services not available.
Does it work if you start it manually from its icon ?
-
I use it from the beginning by restarting it manually.
-
I use it from the beginning by restarting it manually.
Please clarify what do you mean with "Restart it manually":
- Couatl starts automatically from the EXE.XML, appears as a Tray bar icon, but doesn't work until you Restart it in flight.
OR
- Couatl starts automatically, works on the starting airport, but requires a Restart in flight
OR
- Couatl doesn't start automatically, but works if you Start it manually.
-
The 3rd. i have to start it by myself
-
The 3rd. i have to start it by myself
Then it means GSX works perfectly fine, and your problem it's just the EXE.XML not working correct, which is a problem of the sim or the way the XML file is formatted.
-
Yes I think. but it only does it with your program, I have FSUIPC, Fenix, FSrealistic which starts by itself, the only one which does not work is couatl
-
Yes I think. but it only does it with your program, I have FSUIPC, Fenix, FSrealistic which starts by itself, the only one which does not work is couatl
Have you tried rearranging the order of the add-ons ? Perhaps the problem is caused because there are several to be launched together and, the way Windows loads dependencies, when multiple programs need to start together, their loading order might matter.
I only have Couatl and Fenix in my EXE.XML and:
- Before SU11 final, NONE of them started automatically
- After SU11 final, BOTH always starts automatically, 100% of the time.
-
Since SU11 couatl never starts, I always now have to start manually. I am also getting some quick messages about building a cache but its quick so cant see actual message and thrirdly the passngers once again now dont walk on. I actually get the first message that 70/ (whatever max amount is) have boarded, then a couple of seconds later 110, then full. Its all over the place once again. I have re-installed the addon manager time and time again, same thing. When this is working it great Umberto but its a pain in the ass when its not.
-
Since SU11 couatl never starts, I always now have to start manually.
Before SU11, Couatl NEVER started automatically for me, both I wasn't really worried, since as clearly explained in this thread, it was an issue with the sim, mistakenly trying to valid a license
After SU11, Couatl ALWAYS starts automatically, 100% of the time so, clearly, the problem has been fixed in SU11.
This, obviously, assume you don't have other issues with the EXE.XML, and it's even possible other add-ons loaded there and their order, might affect this, but again, it's nothing we can control, if the program works, there's nothing we can do to "force" its startup, other than adding the correct line in the EXE.XML, which the installer obviously does already.
I am also getting some quick messages about building a cache but its quick so cant see actual message and thrirdly the passngers once again now dont walk on. I actually get the first message that 70/ (whatever max amount is) have boarded, then a couple of seconds later 110, then full. Its all over the place once again. I have re-installed the addon manager time and time again, same thing. When this is working it great Umberto but its a pain in the ass when its not.
This is a completely different issue, which clearly doesn't have anything to do with this thread, that only explains how the inability to start Couatl automatically, it's nothing we can do about it. Please don't post something totally unrelated in the wrong thread. Open a new one with a proper title, and I'll explain why you get fast pasengers boarding ( has been explained so many times, but I'll explain it again )
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
Is your normal user account with limited permission ?
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
Thank you for posting this airbadger. That solved it for me also. Now, I just have to figure out how to run MSFS as administrator from within the Addons Linker app.
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
Is your normal user account with limited permission ?
TBH I can't figure out how to confirm that one way or another. I log in with my MS account, not a local one, if that matters.
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
Just want to be sure, since you posted this a couple of weeks back, has this been the solve for you? Running MSFS in admin mode?
-
Looks like this issue is solved for me thanks to a tip from the dev at Lorby. Make sure MSFS is set to run as admin.
Just want to be sure, since you posted this a couple of weeks back, has this been the solve for you? Running MSFS in admin mode?
Yes, haven't had issues since
-
Interesting. When I run flight sim in administrator mode, I still have to manually start Couatl engine. It also terminates a lot during my flights.
-
I purchased GSX on day one and everything worked as expected but, from the next build to build Dec 16th Couatl has to be started before or after the sim is loaded.
One possible conflict my be the fact that I use Airport Jetway Pro as I like to see the passengers through the glass sided jetways at default airports.
If I run the sim I get "Couatl Scripting Hasn't Started" and the log file is empty and no icon in the sys tray.
The file below is from starting the sim then Couatl. Which still gives the "Couatl Scripting Hasn't Started" error. However, there is an icon in the sys tray. If one continues to keep clicking GSX in the sim GSX will eventually start.
-
Same exact behavior is happening to me, but I'm not using that 3rd party mod you just mentioned.
Couatl is definitely struggling staying on the entire flight, I constantly have to re-start it manually.
Out of curiosity, are you on SU11 beta (with the AAU 1 update?)
-
However, there is an icon in the sys tray. If one continues to keep clicking GSX in the sim GSX will eventually start
This indicates the program started, and you only had to be patient and way for the airport cache to be regenerated. If you use the SU10 Navdata API option, it won't use the airport cache anymore, so the startup will be faster.
-
Out of curiosity, are you on SU11 beta (with the AAU 1 update?)
[/quote]
No, I am not on the Beta
-
[ If you use the SU10 Navdata API option, it won't use the airport cache anymore, so the startup will be faster.
Thx, that really helped.
-
I solved the problem by starting COUATL as an Administrator BEFORE starting the simulator. That works like a charm on my setup, provided I use the GSX "Taskbar button inside cockpit to start the app.
My setup is Windows 10 and the Microsoft Store version of the flight sim.
-
So, due to my switch from a 8700K to a 13600K I took the plunge and re-installed Windows and MSFS. Then, as reports suggest better scheduler in Windows 11, I also performed a brand new install of Windows 11. Afterwards, I put all my addons back into MSFS, re-installed GSX Pro and guess what? Not a single issue with this nasty content.xml stuff, Couatl started each and everytime I fired up my sim. With the exact same number of addons I had before.
BUT: due to Couatl crashing when arriving at the gate, I modified the Couatl64.exe by ticking the "start as administrator" checkbox and the last update also automatically set "use Windows 8 compatibility mode". And guess what? Now this annoying little .exe does NOT start up with the sim anymore. What a bummer.
I will now remove those two checkboxes again and test. But honestly, I am so sick of this testing around, why this thing cant just run as expected?
-
BUT: due to Couatl crashing when arriving at the gate, I modified the Couatl64.exe by ticking the "start as administrator" checkbox and the last update also automatically set "use Windows 8 compatibility mode". And guess what? Now this annoying little .exe does NOT start up with the sim anymore. What a bummer.
I will now remove those two checkboxes again and test. But honestly, I am so sick of this testing around, why this thing cant just run as expected?
As explained so many times already, we were never, ever, able to replicate the crash in flight. The only data we had is reports from users, and the only choice we have is to trust users that a solution worked for them, if they said so.
Since in the past weeks, we got overwhelming confirmations from multiple user that setting Windows 8 Compatibility mode totally fixed the crash in flight we could never replicate, we set it by default with the installer.
You are the one and only reporting that option is preventing the program to start. Of course, I cannot replicate that either because, before deciding to make the Windows 8 compatibility set as default, I tested it for at least a couple of weeks and, while I couldn't see ANY difference ( it didn't crash before, it doesn't crash now ), but at least I know it doesn't do any harm so, why should I doubt users that *had* the crash, all reporting Windows 8 Compatibility fixed the problem for them ?
If it doesn't work for you, you are the first one saying that so, just turn it off. And best not turn off "both" options at the same time, otherwise you'll never know which one works and which one doesn't.
-
If it doesn't work for you, you are the first one saying that so, just turn it off.
I did, took the checkmark off the "use Windows 8 compatibility mode" and guess what, couatl starts again without hickup together with the sim. So in my case, using the Windows 8 compatibility mode does no good. BTW, I am on a brand new Windows 11 installation, might be that this is the reason and for Windows 10 users, the Windows 8 compatibility helps. Who knows...
-
I am on a brand new Windows 11 installation, might be that this is the reason and for Windows 10 users, the Windows 8 compatibility helps. Who knows...
Most users that confirmed the Windows 8 compatibility flag helped were using Windows 11, and some Windows 10.
-
I hope someone can help me. I just did a fresh install of Windows 11. Installed MSFS, and the add ons from Marketplace. I installed GSX Pro and other FSDreamteam airports. Loaded the sim and got the Couati engine hasn’t started. I started manually with the Couati shortcut that was installed on my desktop. GSX worked fine. I looked at the MSFS xml file and GSX is not on the startup. Fenix and Aerosoft VGDS is there. How can I fix this. Never had a problem before with GSX.
Thanks,
Greg
-
I looked at the MSFS xml file and GSX is not on the startup. Fenix and Aerosoft VGDS is there. How can I fix this. Never had a problem before with GSX.
The addition to the exe.xml are made when installing GSX for the first time. If for any reason you lost the lines (perhaps another add-on has restored from a previous backup), you can use the FSDT Installer to recreate the lines.
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.
-
I looked at the MSFS xml file and GSX is not on the startup. Fenix and Aerosoft VGDS is there. How can I fix this. Never had a problem before with GSX.
The addition to the exe.xml are made when installing GSX for the first time. If for any reason you lost the lines (perhaps another add-on has restored from a previous backup), you can use the FSDT Installer to recreate the lines.
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.
I delinked GSX. I now has the lines in the xml . Started the sim and the same thing happened. Did not start automatically. I checked both Couati exe files and both have run in windows 8 compatibility. I unselected that and now trying again. I let you know what happens.
-
I believe MFS is having an issue with the .EXE file which is used to auto load community things. That is why things like the fenix needed to be opened manually until they recently updated it.
-
It amazes me how can something like this can get through a beta and then to a final release.
The obvious explanation would of course be that it doesn't normally happen.
-
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
-
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.
-
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...
-
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!
-
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.
-
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?
-
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.
-
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.
-
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.
-
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
-
Thanks but happy to report how it's working after the latest update.