FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: AfflictedSim on October 05, 2022, 04:41:34 pm
-
Hello,
I've been faffing with this couatl for ages trying to get it to work. I have GSX L1/L2 on P3D and have experienced issues with GSX basically for as long as I've owned the product...
I have already completely uninstalled, restarted, made exclusions, and disabled antivirus and it still doesn't work. Sometimes it does and other times it doesn't, it's very frustrating.
*This is to do with MSFS, my P3D version works fine at the moment.*
-
You shouldn't open a new thread, with one with the same, identical subject is flagged as Sticky:
https://www.fsdreamteam.com/forum/index.php/topic,26759.0.html
With clear instructions what you are supposed to do to create a diagnostic log. Also, if you are able to start it manually, but not automatically, that's a known MSFS bug with the EXE.XML processing, which has also its own dedicated thread here:
https://www.fsdreamteam.com/forum/index.php/topic,26924.0.html
-
Attached is my log file.
I loaded up the simulator and spawned in. Put in the Couatl_MSFS ini then restart couatl.
-
I loaded up the simulator and spawned in. Put in the Couatl_MSFS ini then restart couatl.
Your log shows the program started normally, then it just stopped. Are you sure you allowed enough time to start so the log could be completed ?
Some users with a similar problem reported it fixed by adding the whole Addon Manager folder to the antivirus Exclusions.
-
Every single couatl-related thing is under exclusions in my antivirus, from the whole folder itself down to the executable files. I've already uninstalled, turned off antivirus completely and then ran the installer as admin and installed GSX that way - the same issues occur.
-
Try running the FSDT Live Update, this will force a cache rebuild, then check the new log which should show the airport cache regeneration process, I need to check if it completes correctly.
-
Here is the log after running FSDT live update.
-
Here is the log after running FSDT live update.
No, that log looks is coming after another restart, since it doesn't show the cache being rebuilt ( it just loaded the existing one ), which will always happen after running the updater. Be sure you don't restart Couatl, because the 2nd run after the first cache rebuild will overwrite the log.
-
I don't understand.
So do I quit all GSX processes? Close MSFS. Run FSDT live update, then open MSFS, spawn in, restart couatl, give it 5 mins, then give you the log?
-
restart couatl, give it 5 mins, then give you the log?
That's the problem: you should not restart couatl, not if it has started automatically, because by restarting you are overwriting the log.
If you want to save the "run the FSDT Live Update" step, remove this folder:
C:\ProgramData\Virtuali
It will achieve the same effect of triggering a cache rebuild at the next start
-
I followed your steps. This time, I opened GSX and it immediately started deboarding for some reason.
-
I did same thing again, this time it loaded but immediately says 'couatl scripting engine not started'.
Log attached.
-
I did same thing again, this time it loaded but immediately says 'couatl scripting engine not started'.
Your log shows the airport cache regeneration took 162 seconds. During that time, you can't call GSX until it completes. None of your log shows any issues anyway, it seems you are just quitting the sim before allowing it to complete loading, at least that is what the log shows.
-
I don’t understand why the airport cache takes so long when I already have a GSX profile for the airport?
-
I loaded up in EGKK, which I've spawned in several times and have a custom airport profile for thus no airport cache should need to be generated.
I try to click GSX, it says the error message, I wait 10 minutes, still same error message.
-
Heres another time, loaded up a new airport with no previous spawn before and no custom GSX profile. I Started GSX and the error came up, waited 10 minutes, and no cache had been generated yet. Yet, when looking in the windows pop-up bar, couatl said it had 'successfully generated airport cache'.
-
I loaded up in EGKK, which I've spawned in several times and have a custom airport profile for thus no airport cache should need to be generated.
Who said that ?
Until we'll release the update to use the new Navdata API, GSX will always require an airport cache, even more so if you have a profile, because it needs to associate the profile with the .BGL loaded, which is only known if there's a valid airport cache.
-
Heres another time, loaded up a new airport with no previous spawn before and no custom GSX profile. I Started GSX and the error came up, waited 10 minutes, and no cache had been generated yet. Yet, when looking in the windows pop-up bar, couatl said it had 'successfully generated airport cache'.
What about this scenario?
-
What about this scenario?
That I can't reproduce it. Your log shows GSX just stopped with no apparent reason. A possible reason might be Simconnect stopping, since GSX use Simconnect communication as a "clock" for itself, if Simconnect stops, GSX will stop as well.
If it's not the antivirus ( which is by far the most common cause ), it's possible might be a bug in the sim when multiple Simconnect clients are connected. You might try to see if this happens if no other add-ons that use Simconnect are active, except GSX.
-
Where is simconnect located? Same folder as addon manager?
-
Where is simconnect located? Same folder as addon manager?
The Simconnect server is part of the sim, and the Simconnect client is statically linked in every .exe that use it. If something is wrong with it, there's not much anybody can do, other than proceed by elimination and find possible conflicts. Which is why I asked to try with GSX alone.
-
The only other addons I use are the fenix and volanta in the background.
-
The only other addons I use are the fenix and volanta in the background.
Then proceed by elimination, and not use one or the other. I don't think there's a conflict with Fenix, since everybody use it with GSX, so try the other one.
If nothing changes, check again to be sure the Addon Manager folder is excluded by the antivirus.
-
EVERYTHING to do with couatl or GSX or a flight simulator is excluded in both the folders and the file .exe’s so it’s definitely not to do with my antivirus.
I just tried without volanta and only fenix and the same issues happen.