FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: joshfellows1997 on October 28, 2017, 12:52:14 pm
-
Hello,
Every time I request something from GSX it will crash Couatl and keep trying to restart it constantly.
I have tried it with different aircraft, different airports, different requests and all come back with GSX crashing and offering an error log, asking if I want to restart it which I press "Yes" and sometimes it will restart and the same issue occurs or it will continue coming back to me with an issue log when trying to restart it which then requires me to press restart again.
Please see attached of 2 scenarios.
I used the Addons PMDG 747 V2 and the FSLabs A320 in all tests.
I have also run the FSDT Updater before restarting the sim with the same occurrence.
Best Regards,
Josh
-
Hi Josh,
I came to find in another thread that the airplane config for GSX of the last version might interfere with the latest build. I'm also getting crashes in PMDG 737, 777 and 747v3 products as well as the FSL A320.
In case of the A320 I've made a new config file within the GSX "customize aircraft" menu of the latest build to ensure compability.
If I've got no config for the FSL A320 in the aircraft folder, GSX works and if I've got a config in the aircraft folder Couatl crashes at every command I give through the GSX menu.
For PMDG airplanes I have no configs whatsoever, as they work good enough for me without further cusomization.
-
Hi Johannes,
Where would I be able to find these cfgs? I haven't actually set up a cfg or downloaded one for any of these aircraft.
-
AppData Roaming -> Virtuali -> Airplanes is the folder. The FSL A320 needs a config for the correct refueling, water and waste positions. Also I have hopes to use the third cargo loader for the bulk cargo once GSX works.
-
Thanks, so do I just remove the FSLA320 folders to see if it will work? I tried it with the PMDG and like you said no change here.
-
yes, just move the folders so GSX can't read the files.
-
I found a solution that works for me. As I removed all FSDT products and installed one by one, testing if there was any of the FSDT native add-ons causing GSX to constantly crash on me.
GSX - when installed freshly, with all folders in ProgramFiles (x86), ProgramData and AppData Roaming deletet entirely - worked just fine, with no crashes. When I installed other FSDT products the crashes came back.
For me the solution to first install all FSDT products except for GSX, deleting the Virtuali folder in AppData Roaming and also deleting the couatl folder in the ProgramFiles (x86)\Addon Manager directory and only then start installing GSX with the latest available installer.
-
Why would I have to do this for something that has been working for months? I up dated mine ever sense the new addon manager came out and it was fine then. Now I get this error. I have done NOTHING to my sim except adding the 787-8/9 sense then and that should not effect anything at all with the Coautl Engines. I should be able to install new products from FSDreamteam or anyone else that uses the software and it should work. What changed now?
-
I would guess that Couatl has a new version that is required to run the latest GSX version but can't overwrite itself.
There's very little to uninstalling GSX, going into the ProgramFiles (x86) folder, deleting the old Couatl and installing GSX again...
-
So uninstall GSX and delete Couatl engine folder in appdata is that correct?
-
no, Couatl is located in the ProgramFiles (x86) folder on your windows installation drive. That should be C:\Program Files (x86)\Addon Manager\couatl
uninstall GSX, delete the couatl folder and reinstall the latest version, see if it works.
-
I had constantly restarts also.
Installing GSX again after other FSdreamteam Airports did the trick.
thanks
-
Sounds like a issue that needs to be addressed by FSDT.
-
I would guess that on some systems the latest installer doesn't overwrite couatl with the latest version that seems to be vital for use with GSX 2.2.0.0...
-
I would guess that on some systems the latest installer doesn't overwrite couatl with the latest version that seems to be vital for use with GSX 2.2.0.0...
It seems like the installer fucks up at some point, because i had a fresh and new and latest GSX version, and still when i installed a FSDT scenery, Couatl started crashing each time i wanted to do something with GSX, be it boarding, fueling, catering, whatever.
-
The installer doesn't have any problems and is not ***up anything. I had a look at error reports that have been posted here and, the ONLY possible cause they could ever happen, is if you have some outdated files.
Normally, is not possible to get outdated files, because BOTH the installer AND the Live Update downloads and install all the latest files.
The only possible reason I can think of why someone is not getting the latest files, is that either a firewall or an antivirus is PREVENTING the Live Update or the installer to do its job. Maybe it has decided that something that "downloads something" must be dangerous. I must say that, on my system, Chrome is now flagging *everything* which is not made by large companies as suspicious. So, I just ignore it.
So, again, you simply cannot have these kind of errors, if all files are updated and, you cannot end up with outdated files, if you run the FSDT Live Update or ANY of the FSDT installer, regardless the order you installed them.
Assuming, of course, you are running reasonably recent versions of them, basically anything we released after June 2017, when we switched to the new Live Update method. If you install something older, then yes, everything can happen, and you will usually have to uninstall and reinstall with the latest versions to fix this.
But, if all the installers you are using are those made after June 2017, then it's impossible you would end up with outdated files, since they ALL launch the SAME Live Updater, which has *also* being downloaded so, not only they launch the Live Update, they also "update the updater" so, really, if there's nothing that interfere with the process, you simply cannot get outdated files.
Fact that everything is fixed if you uninstall, remove all folders and reinstall, clearly indicates there's some kind of interference by an external program (firewall or antivirus or similar), which is allowing YOU to do things like removing the old files, but is preventing the Live Update to DO THE SAME.
-
Hi Umberto,
I sincerely apologize if this thread seems like an "attack" on couatl or something like this to you, it is not meant like this!
On my system the only thing that was working was literally - even after reinstalling all FSDT products - to uninstall GSX, delete couatl and reinstall the latest version. I've tried the live update method as well as only installing the latest GSX over top of all sceneries with permanently having all anti virus and windows defender systems turned to off manually.
I can only report back what I see happening on my system. GSX worked fine after uninstalling all FSDT add-ons and deleting all folders in ProgramFiles(x86), AppData and ProgramData, then installing only GSX. It started crashing once I installed other products (all with latest installers), so I tried uninstalling Addon Manager and installing the latest version with all FSDT products in place - which did not work. The next instance was couatl, so I just deleted the entire couatl folder and reinstalled GSX to keep it simple and it worked ever since...
That's what I can report back after self-testing back and forward and seeing 1-2 people having the same issue resolved by doing the same steps. I suspect couatl to not be overwriting old files correctly based on what I did to get my GSX working, so you might want to look into this. I've found my solution for my system, so I'd like to share that with you for eventual troubleshooting or necessary programming (or whatever might go into fixing this issue).
Please let me know if you need more information for a possible fix, I will be happy to help!
-
I suspect couatl to not be overwriting old files correctly based on what I did to get my GSX working, so you might want to look into this.
I'm SURE the issue is outdated files, because the error reported in the log simply cannot happen and the update file related to that part of the code, has been online since July.
We tried to understand how this is possible, and came out with the following possible reasons:
1) Your local Cloudflare node not updated with the last files we posted. This seems to be very unlikely in this case, since the error discussed here (I'm referring to the files posted in the first thread) simply cannot happen with any set of files released after July.
OR
2) An external software is interfering with the Live Updater or the installer. This seems to be the most likely cause. Maybe the antivirus/firewall is assuming the Live Update or any of our installers might be dangerous or some sort of spyware, just because they download something which, with some excessively prudent heuristic, might be flagged as a suspicious behavior.
OR
3) An OLD version of our installers (one which was made before June 2017) has been used after a new one, with the root of the sim being the installation target for both, which WILL create a mess of old/new files and surely all sort of problems.
Since the old version only installed INTO the root of sim, and the new version lets you choose any folder freely, it's surely possible to cause this mix up, if the first installation with the new installer was made the root of the sim (which is not the default anymore, and it's not really a good idea now), if the a subsequent installation is made using an old installer (which would go into the root of the sim automatically), this would create a mixup of old/new files, especially considering the old installer would also download, but from a different update server, which we don't maintain anymore, but keep up with the latest set of old files, in order not to break installations entirely made using outdated installers.
-
I have a similar problem, but only on final approach after selecting a gate position
Please post your error log.
Is it necessary that I should have the Addon Manager in the "....(x86)" folder?
The Addon Manager will work from any folder, which is why the installer is offering you a choice. It it was required to be installed in a specific folder and won't work otherwise, we wouldn't allowed the destination folder to be freely chosen.
-
I am also facing this problem and it seems the only solution is to install GSX last as Johannes suggested.
If I install any FSDT scenery AFTER GSX then Couatl always crashes when I select any GSX service.
If I install GSX last, after every FSDT scenery, everything works fine.
-
The latest Live Update should have fixed this, so the order of installation doesn't matter anymore.
-
Yes running the live updater fixed mine. So does that mean it was not an issue with firewall or protection because I had none of that turned on when doing it before and also was running as admin. Was the tool actually not working as it should?