FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: paul_lbg on August 18, 2022, 09:46:27 pm
-
Good evening,
just bought GSX Pro for MSFS, the couatl scripting engine however doesn't seem to start. I tried with the Fenix A320 at Skiathos Airport by ORBX if that matters.
-
I’m getting the same error.
-
go to where you installed the "Addon manager" folder whilst installing GSX and in there you'll see a folder called couatl, go in there and you can run the program before starting MSFS
-
Same issue here, despite Couatl64_MSFS is running in the Task Manager.
-
Same issue here, despite Couatl64_MSFS is running in the Task Manager.
yep, that was the case for me as well, I rather think it's a bug between the sim and couatl
-
Same issue here, despite Couatl64_MSFS is running in the Task Manager.
If it's just stuck, it's 100% a server problem. As you might now, we use Cloudflare to prevent the usual "site going down the release day", which happened to every other major release. Because of the Cloudflare network of 260 nodes spread around the world, we don't risk having the server put down, so NOBODY could download anything.
The side effect of this, is that it takes a few hours for all nodes to get all the current files, and this time we updated A LOT of files so, if you run the FSDT Live Update again, all right files will eventually be up.
A crucial file that, it not updated, will stop the program from working, is this one:
http://update.virtualisoftware.com/setup/fsdtroot/couatl64/bglmanx_fsdt.dat
If you can't get the latest version through the updater, because your Cloudflare node still has the previous version, downloading it from here should fix the problem. The file you downloaded MUST be placed in the following folder:
Addon Manager\couatl64
And overwrite the file with the same name which is already there. This should get you going, until the servers catch up.
-
Same here, installed Ok but nothing in MSFS Top menu. Run couatl for MSFS, restarted MSFS and nothing in menu
Good evening,
just bought GSX Pro for MSFS, the couatl scripting engine however doesn't seem to start. I tried with the Fenix A320 at Skiathos Airport by ORBX if that matters.
-
Same here, installed Ok but nothing in MSFS Top menu. Run couatl for MSFS, restarted MSFS and nothing in menu
You don't say if you tried the file I posted in the message before yours.
-
Tried the above and still not working with the file. Not sure what's going wrong here, glad I'm not the only one though
-
Not working for me with the file installed
-
Hello,
Also updated the file/rand the updater. No success, I can't see GSX in MSFS.
Regards
Steve
-
I have downloaded the file provided by you @virtuali, placed it as per instruction and still nothing. I have manually launched Couatl64_MSFS as an admin and the process was there until the flight loaded - as soon as I spawned in Fenix A320 at EPWA airport the process disappeared. When I lauch it when the sim is already running, nothing happens - I don't get that "COUATL scripting engine not starting in MSFS" message and neither I get a visible GSX window.
-
same problem here
-
Here same issue. I get the icon but when pressing it I get the same "COUATL scripting engine not starting in MSFS" message.
-
I have downloaded the file provided by you @virtuali, placed it as per instruction and still nothing. I have manually launched Couatl64_MSFS as an admin and the process was there until the flight loaded - as soon as I spawned in Fenix A320 at EPWA airport the process disappeared. When I lauch it when the sim is already running, nothing happens - I don't get that "COUATL scripting engine not starting in MSFS" message and neither I get a visible GSX window.
Same thing. Tried the file, tried the updater. Not working.
-
Same here, downloaded and overwritted the DAT file, but the situation is the same.
-
Hello, same here without success
-
Try again, it's even possible your browser is playing tricks on you: because the updater downloaded the old file, your browser might have cached it, so you are again getting the old version from the forum. Try a different method, by using the file attached here.
-
Try again, it's even possible your browser is playing tricks on you: because the updater downloaded the old file, your browser might have cached it, so you are again getting the old version from the forum. Try a different method, by using the file attached here.
You sure you have the right file linked? I ask because over on AVSIM someone said the right file size is 126,144 (assuming KB), but this file you're linking is 710KB..
-
Try again, it's even possible your browser is playing tricks on you: because the updater downloaded the old file, your browser might have cached it, so you are again getting the old version from the forum. Try a different method, by using the file attached here.
Nothing, same issue with the last .zip file.
-
You sure you have the right file linked? I ask because over on AVSIM someone said the right file size is 126,144 (assuming KB), but this file you're linking is 710KB..
And that's precisely why we DO NOT want people using Avsim for support, when the one and only place that can fix things it's obviously here. That user must have mixed up his numbers, because the correct size, in bytes, it's 726,144 bytes so, it seems somebody must have confused a 7 for a 1.
-
Try again, it's even possible your browser is playing tricks on you: because the updater downloaded the old file, your browser might have cached it, so you are again getting the old version from the forum. Try a different method, by using the file attached here.
Still nothing - Couatl64_MSFS process disappeared as soon as the flight loaded, manually starting it when the sim is running does nothing - no "COUATL scripting engine not starting in MSFS" message, no GSX window still...
-
You sure you have the right file linked? I ask because over on AVSIM someone said the right file size is 126,144 (assuming KB), but this file you're linking is 710KB..
And that's precisely why we DO NOT want people using Avsim for support, when the one and only place that can fix things it's obviously here. That user must have mixed up his numbers, because the correct size, in bytes, it's 726,144 bytes so, it seems somebody must have confused a 7 for a 1.
Well, whatever you're linking is also not working, so I don't think the issue is that someone posted on AVSIM vs here, is it? Anyway, you guys are clearly getting slammed right now, hoping you can fix it in a few hours.
-
Hi, Thanks
replaced files, restarted MSFS. I get GSx icon but when I click it says couatl scripting engine hasn't start.
Same here, installed Ok but nothing in MSFS Top menu. Run couatl for MSFS, restarted MSFS and nothing in menu
Good evening,
just bought GSX Pro for MSFS, the couatl scripting engine however doesn't seem to start. I tried with the Fenix A320 at Skiathos Airport by ORBX if that matters.
-
I have included a video below of the issue we're facing. Couatl is running but the menu does not load. GSX vehicles are there but just no menu
https://youtu.be/krbi9pTFNRA (https://youtu.be/krbi9pTFNRA)
(Video is still processing in HD, but you can tell what I'm doing)
-
You are probably getting an error.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
Modify message
-
I am having the same exact issues, tried loading the file umberto posted, no changes. I can see the process active via Process Lasso, but upon loading initially the message "COATL Scripting Engine hasn't started" appears, then the same issues as posted in the video above.
GSX Menu is there but nothing happens when clicking on it..
-
You are probably getting an error.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
Modify message
Modify message
-
I cannot get any Live update... nor get coualt to run
-
You are probably getting an error.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
Modify message
I do not see the Couatl.LOG file, however, these show up. Would you like me to attach the Couatl.err file instead?
-
I cannot get any Live update... nor get coualt to run
Please open a new thread, because this thread is not related to any issues with the Live Update. If the Live Update doesn't start, nothing will work, but if we mixup your issue with the one discussed here, it will only made the thread unreadable. Please open a new thread with a proper subject and try to explain your problem as precisely as possible.
-
I do not see the Couatl.LOG file, however, these show up. Would you like me to attach the Couatl.err file instead?
You have visibility of file extensions disabled in your windows explorer, so it's not easy to understand which file is which. The .err file is ok.
-
I'm attaching both couatl.LOG created using the method you described and Couatl.err which was already there
-
I do not see the Couatl.LOG file, however, these show up. Would you like me to attach the Couatl.err file instead?
You have visibility of file extensions disabled in your windows explorer, so it's not easy to understand which file is which. The .err file is ok.
Ahh I see, I see them now. I've attached this for you
-
Both your logs don't show any errors. It's very likely that, an error might have happened only after opening the GSX Toolbar menu so, be sure you do that, then exit Couatl from its Traybar icon and check the log again.
There isn't any need to reload the simulator at any time, the Couatl program now has a Tray bar icon, and can be started and restarted as many times as you need, without restarting the sim. But keep in mind, when you restart it, a previous log that might contains useful information from the previous session, will be overwritten.
So, as soon you realize the menu doesn't open after you click on it, exit Couatl with the Tray bar icon, and check the new log file. And attach it, Zipped.
-
Both your logs don't show any errors. It's very likely that, an error might have happened only after opening the GSX Toolbar menu so, be sure you do that, then exit Couatl from its Traybar icon and check the log again.
There isn't any need to reload the simulator at any time, the Couatl program now has a Tray bar icon, and can be started and restarted as many times as you need, without restarting the sim. But keep in mind, when you restart it, a previous log that might contains useful information from the previous session, will be overwritten.
So, as soon you realize the menu doesn't open after you click on it, exit Couatl with the Tray bar icon, and check the new log file. And attach it, Zipped.
Here you go - launched Couatl64_MSFS, tried to load in-game panel, after few seconds of nothing even the tray icon disappears, so here is the newest log zipped after the process has stopped
-
Both your logs don't show any errors. It's very likely that, an error might have happened only after opening the GSX Toolbar menu so, be sure you do that, then exit Couatl from its Traybar icon and check the log again.
There isn't any need to reload the simulator at any time, the Couatl program now has a Tray bar icon, and can be started and restarted as many times as you need, without restarting the sim. But keep in mind, when you restart it, a previous log that might contains useful information from the previous session, will be overwritten.
So, as soon you realize the menu doesn't open after you click on it, exit Couatl with the Tray bar icon, and check the new log file. And attach it, Zipped.
Here you go
-
hi, i try all the think but i still have the same error...
i can not use it at all
-
i am also having the same issue i have reinstalled in case of a dodgy download my antivirus and firewall are off and exceptions added just incase and have use the file you have provided and overwritten.
I have even tried to restart from the taskbar but still get same error
-
Both your logs don't show any errors. It's very likely that, an error might have happened only after opening the GSX Toolbar menu so, be sure you do that, then exit Couatl from its Traybar icon and check the log again.
There isn't any need to reload the simulator at any time, the Couatl program now has a Tray bar icon, and can be started and restarted as many times as you need, without restarting the sim. But keep in mind, when you restart it, a previous log that might contains useful information from the previous session, will be overwritten.
So, as soon you realize the menu doesn't open after you click on it, exit Couatl with the Tray bar icon, and check the new log file. And attach it, Zipped.
Here's mine
-
Nothing changed, you still don't have any errors, and nothing in your shows you ever pressed the Toolbar icon to start GSX, are you sure you did that and THEN exited the program without restarting it ?
-
These are just some potential fixes that I have came across, and I want to share.
This GSX issue seems to have been a thing for years across P3D version as well. Here are some fixes I'd recommend. It seems that Couatl crashes when MSFS opens, because it struggles to open and read parts of .py files - from the couatl.ERR file.
> Add C:\Program Files (x86)\Addon Manager as an exclusion in your antivirus firewall before you install.
> Try running the FSDT Live Updater to fix any lost files.
> Uninstall all of your Visual C++ files through Control Panel, restart your PC, go onto Microsoft's website and re-download the Visual C++ Redistributables (x64) (google it).
The Visual C++ fixed for me, but occasionally I still get the script error, and have to restart PC/sim. I'll keep looking into it and let you know if I find anything.
-
Nothing changed, you still don't have any errors, and nothing in your shows you ever pressed the Toolbar icon to start GSX, are you sure you did that and THEN exited the program without restarting it ?
100% yes I did click it. It seems that couatl crashes when I click it as there's nothing to exit after clicking the button in-sim
-
I've done 2 pc restarts, 6 reinstalls 12 couatl restarts and nadda, plus im not able to find the log.
-
Nothing changed, you still don't have any errors, and nothing in your shows you ever pressed the Toolbar icon to start GSX, are you sure you did that and THEN exited the program without restarting it ?
Well as I said - couatl process disappears from task manager as soon as I click on the gsx icon in the msfs toolbar. I have packed the log without restarting couatl.
-
Attached err file, cant see log file
Hi, Thanks
replaced files, restarted MSFS. I get GSx icon but when I click it says couatl scripting engine hasn't start.
Same here, installed Ok but nothing in MSFS Top menu. Run couatl for MSFS, restarted MSFS and nothing in menu
Good evening,
just bought GSX Pro for MSFS, the couatl scripting engine however doesn't seem to start. I tried with the Fenix A320 at Skiathos Airport by ORBX if that matters.
-
Nothing changed, you still don't have any errors, and nothing in your shows you ever pressed the Toolbar icon to start GSX, are you sure you did that and THEN exited the program without restarting it ?
Well as I said - couatl process disappears from task manager as soon as I click on the gsx icon in the msfs toolbar. I have packed the log without restarting couatl.
Exactly the same as me, even with it running as administrator. May be a couatl issue here
-
Nothing changed, you still don't have any errors, and nothing in your shows you ever pressed the Toolbar icon to start GSX, are you sure you did that and THEN exited the program without restarting it ?
Here is the process I am using to test:
https://www.youtube.com/watch?v=gnheUTniing; here is the log file from the video (https://www.youtube.com/watch?v=gnheUTniing; here is the log file from the video)
-
Hi everyone and thanks fsdt for releasing GSX for MSFS.
I've got the same engine error as everyone else and I tried all the tricks and copied the files provided in this post. Please find attached my couatl file. Looking forward to getting support with this so that I can enjoy GSX.
Best
adlouah
-
Attached err file, cant see log file
Your log clearly indicates it's a SERVER UPDATE issue. Like several others, you are getting an error from a line that has been moved in the file, so you surely have an outdated version of some files.
-
I thought it was just me so I'm glad to see (in a strange way!) lots of others having exactly the same problem.
Installation went very smoothly. On loading up a flight, I get the new GSX icon but when I click it, it says "COUATL SCRIPTING ENGINE HASN'T STARTED". The Couatl app IS loaded and is happily sitting in my sys tray and even says "Airport Cache loaded successfully" if you hover over the icon. I've added the 'updated' file and no change.
Just teething troubles I am sure but disappointing not to be able to try this out this evening.
-
I've just loaded up MSFS fresh and new. Checked couatl and it's still running, clicked to load into flight and it was still running...flight loaded in, models of GSX loaded in and bam, couatl disappeared from the taskbox. Something is crashing couatl and no idea what it is.
Couatl is being ran in administrator mode, logfile is still the same as before and doesn't show any errors
-
I've just loaded up MSFS fresh and new. Checked couatl and it's still running, clicked to load into flight and it was still running...flight loaded in, models of GSX loaded in and bam, couatl disappeared from the taskbox. Something is crashing couatl and no idea what it is.
Couatl is being ran in administrator mode, logfile is still the same as before and doesn't show any errors
FWIW, this sounds different from my issue. My Couatl continues to run no issue, regardless. Just getting the in-sim error and no main menu. Might be two different problems here.
-
The Couatl app IS loaded and is happily sitting in my sys tray and even says "Airport Cache loaded successfully" if you hover over the icon. I've added the 'updated' file and no change.
You are probably getting an error.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
-
Pleas see Couatl.err.zip file
couatl v3.2 (build 4792)
panic log started on Thu Aug 18 18:15:10 2022
problem raised by engine or unspecified addon
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named wx
Application aborted because of a Python error
{}
-
Pleas see Couatl.err.zip file
couatl v3.2 (build 4792)
panic log started on Thu Aug 18 18:15:10 2022
That's a log file made by the Couatl for FSX. Have you tried to start it manually from the (wrong) folder ?
-
Facing the same error, here is my error log
regards
steve
-
OK I got it to work, although I still have to start COUATL64_MSFS by hand (it wont start automatically)
I unstinstalled ALL my FSDT products, including the P3D versions, deleted all FSDT folders (APPDATA, Addon Manager, etc.)
Upon loading FS20, GSX menu was there, but still was getting the message that couatl was not started, I started it by hand, and finally got GSX to work. Not sure if this will help anyone, but it is working for now. Umberto, how do I get COUATL to start automatically?
-
Here you go. This is the latest log file to update. Hope it helps as I am certainly not wanting to uninstall all my GSXLevel 2 installation for P3D.
The Couatl app IS loaded and is happily sitting in my sys tray and even says "Airport Cache loaded successfully" if you hover over the icon. I've added the 'updated' file and no change.
You are probably getting an error.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
-
Facing the same error, here is my error log
As with others, your log clearly indicates it's a SERVER UPDATE issue. Like several others, you are getting an error from a line that has been moved in the file, so you surely have an outdated version of some files. Try this:
- Remove this folder:
%APPDATA%\Virtuali\UpdateCache
- Run it again and see if it downloads something new.
-
Hi, thanks
I copied the file you attached in your email.
Also updated fax through installer. Tried all proposed solution but the problem still there.
I get the fax icon in the Msfs menu, I click on it , it gets highlighted then the script message appears again.
Thanks for the support
Attached err file, cant see log file
Your log clearly indicates it's a SERVER UPDATE issue. Like several others, you are getting an error from a line that has been moved in the file, so you surely have an outdated version of some files.
-
I might have a fix. It wouldn't work for me as I installed Addon Manager in my HDD. However, once I uninstall it all and installed it on my SSD it works. I recommend trying that guys :) It finally works for me.
-
So, couatl crashes at airports that are custom that we own. For example, I've been trying at the MaccoSim Manchester Airport and this is where it never worked.
I moved to another airport in the middle of the Atlantic Ocean and it worked with no issues (after starting back up couatl of course). I was confused, I went back to Manchester to see if it was a slight bug, it then didn't work again at Manchester. I then moved to ANOTHER airport I know I don't have any addons for (Edinburgh) and it's working with no issues!
I purchased Manchester directly from the vendor, and not through the marketplace. It seems that it has an issue with ALL addon airports, and not just marketplace airports, so it'll only work at airports that are default with the sim (or included with the Deluxe/Premium Deluxe airports)
-
Completely unisntalled all GSX related stuff - including for Prepar3d - and then reinstalled, I still had to run the x64 script manually to get it going but it is finally working. Before the reinstall the menu would not appear and eventually the Live Updater started giving errors and would not work at all, this caused me to do the complete uninstall which seems to have fixed pretty much everything. Hope this might help someone.
-
So, couatl crashes at airports that are custom that we own. For example, I've been trying at the MaccoSim Manchester Airport and this is where it never worked.
I moved to another airport in the middle of the Atlantic Ocean and it worked with no issues (after starting back up couatl of course). I was confused, I went back to Manchester to see if it was a slight bug, it then didn't work again at Manchester. I then moved to ANOTHER airport I know I don't have any addons for (Edinburgh) and it's working with no issues!
I purchased Manchester directly from the vendor, and not through the marketplace. It seems that it has an issue with ALL addon airports, and not just marketplace airports, so it'll only work at airports that are default with the sim (or included with the Deluxe/Premium Deluxe airports)
Just tried loading in at a default airport and works well. Addon airport - couatl crash
-
Just tried loading in at a default airport and works well. Addon airport - couatl crash
Your error log, please.
-
Completely unisntalled all GSX related stuff - including for Prepar3d - and then reinstalled, I still had to run the x64 script manually to get it going but it is finally working. Before the reinstall the menu would not appear and eventually the Live Updater started giving errors and would not work at all, this caused me to do the complete uninstall which seems to have fixed pretty much everything. Hope this might help someone.
Did you just uninstall GSX from P3D or everything. I cannot get the Couatl engine to start and no GSX in the MSFS menu. Even if I manually start Couatl 64 no GSX in the menu. I have overwritten the bglmanx that was posted but no luck.
-
I cannot get the Couatl engine to start and no GSX in the MSFS menu. Even if I manually start Couatl 64 no GSX in the menu.
open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
- DO NOT copy the file in a message, but use the "Attach" function of the forum to ZIP the log file and Attach it to a post.
-
Facing the same error, here is my error log
As with others, your log clearly indicates it's a SERVER UPDATE issue. Like several others, you are getting an error from a line that has been moved in the file, so you surely have an outdated version of some files. Try this:
- Remove this folder:
%APPDATA%\Virtuali\UpdateCache
- Run it again and see if it downloads something new.
I tried this with the same issue and i'm still having the same issue
-
Here is the zip file.
-
Just tried loading in at a default airport and works well. Addon airport - couatl crash
Your error log, please.
Couatl.err file doesnt update unless loading GSX at non addon airport
Couatl.log -
Running in mode: Microsoft Flight Simulator
Python 2.7.16 Stackless 3.1b3 060516 (default, Mar 9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 4797)
log started on Fri Aug 19 01:14:20 2022
connecting to SimConnect...
connected to SimConnect
connected to bglmanx
Simulator version: 11 0 282174 999
RunningMode::pathToInstalledPackages F:\Microsoft Flight Simulator
Loading addons
Loading addon common
Addon common loaded
Loading addon LiveUpdate
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
host file found, checking it
createDefaultContainer
Current locale is English_United Kingdom.1252
Initializing audio...
Available devices:
Generic Software on Speakers (Razer Barracuda X)
Generic Software on LG ULTRAWIDE (NVIDIA High Definition Audio)
Generic Software on LG HDR WQHD (NVIDIA High Definition Audio)
Generic Software on Realtek Digital Output (Realtek USB Audio)
Audio disabled per user settings
Slew mode False
bglmanx list contains 24 AddOn(s)
Loading addon LFSB
Addon LFSB not installed or missing one or more files, skipping.
Traceback (most recent call last):
File "<string>", line 97, in loadAddons
File "<string>", line 49, in importAndCreateInstance
ImportError: No module named LFSB
Loading addon GSX
Current sim directory is F:/FSDT/Addon Manager/couatl64
airportCacheOptimizeSearch enabled, excluding files larger than 4000000 bytes
Airport cache loaded successfully
emulateText_MSFS Airport cache loaded successfully 4
Addon GSX loaded
Starting system monitors
Simulator version (from MAIN.DLL) is 11.0.282174.999
isPBRAvailable returned False
isRTTAvailable returned False
GetSimObjectsFolder() returned F:\FSDT\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
GetAdditionalSimObjectsFolder() returned F:\FSDT\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
GetAdditionalSimObjectsFolderV5() returned
GSX SimStart
Loading aircraft.cfg from F:\Microsoft Flight Simulator\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading engines.cfg from F:\Microsoft Flight Simulator\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading flight_model.cfg from F:\Microsoft Flight Simulator\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading gameplay.cfg from F:\Microsoft Flight Simulator\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading systems.cfg from F:\Microsoft Flight Simulator\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
this airplane has 10 exits
GSX flightLoaded C:\Users\Jacob Axford\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
aircraftDb.py provides aircraft data with priority 2 baseName = FNX320
Using aircraft data from aircraftDb.py
Specific .cfg file for G-EZTH not found in SimObjects\Airplanes\fnx320, using standard GSX.CFG file
Specific .cfg file for G-EZTH not found in C:\Users\Jacob Axford\AppData\Roaming\Virtuali/Airplanes\fnx320, using standard GSX.CFG file
Found gsx.cfg file at C:\Users\Jacob Axford\AppData\Roaming\Virtuali/Airplanes\fnx320\gsx.cfg
User collision geometries reloaded
Loading airport EGCC from \\?\F:\Microsoft Flight Simulator\Community\maccosim-egcc\scenery\global\scenery\egcc.bgl
Creating model cache...
Model cache loaded
-
Good Evening,
I've attached 3 separate log files from my system, after carefully following the steps from the previous posts listed here. I've initiated the Couatl64_MSFS.exe file as Administrator BEFORE running the sim to see what it would do. Upon loading the Fenix at a Non-3rd Party airport (IAH) I attempted to call the GSX menu without success. (Waited 45-50 seconds) I restarted Couatl using the tray icon and was then greeted with "Couatl scripting engine is not running". After a few seconds I attempted to call it up again with no response.
2nd Restart yielded the same result, and the 3rd after closing Couatl completely/restarting it did not work on my end. Additional airports tested were SFO/ABQ & DFW with the same result.
-
These lines from the "restart 3" file:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Shows you haven't got the current version of the files, because your local Cloudflare node is still updating, because of the big number of files involved. The correct files should eventually come up with the Live Update.
You can try uninstalling / reinstalling as well.
-
Hello there,
Thank you for all your hard work and support. I get the same message as everyone else (COUATL scripting engine hasn't started). I replaced the .dat file as you suggested but that did not work. Attached is my log file as per your instructions.
Please disregard. You answered in the previous post. I'll let you know if it works.
-
These lines from the "restart 3" file:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Shows you haven't got the current version of the files, because your local Cloudflare node is still updating, because of the big number of files involved. The correct files should eventually come up with the Live Update.
You can try uninstalling / reinstalling as well.
Understood sir, I will attempt to uninstall / reinstall it and worst case, be patient.
-
Please disregard. You answered in the previous post. I'll let you know if it works.
Yes, your log has the exact same error as the previous one, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
-
Hello there! :)
Unfortunately I am also getting the error, where the GSX tile won't open in MSFS. Installation was smooth, Couatl is starting with MSFS, but when I click the tile, nothing happens. Couatl.exe just sits idle in the task manager and MSFS at some point is reporting "Couatl Scripting engine hasn't started". The log is attached.
-
Getting the same issue - tried all suggestion in the thread so far (and I have experience with P3d) - coutal scripting engine not started - even tried the file posted here. Will try another update tomorrow
-
Hello there! :)
Unfortunately I am also getting the error, where the GSX tile won't open in MSFS. Installation was smooth, Couatl is starting with MSFS, but when I click the tile, nothing happens. Couatl.exe just sits idle in the task manager and MSFS at some point is reporting "Couatl Scripting engine hasn't started". The log is attached.
I think the .zip file was broken, so another attempt :)
-
Please disregard. You answered in the previous post. I'll let you know if it works.
Yes, your log has the exact same error as the previous one, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
Just wanted to follow up and say this procedure worked. Thank you!
-
I think the .zip file was broken, so another attemp)
Yes, your log has the exact same error as the previous ones, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
-
same problem here,
-
same problem here,
If you mean you already checked your log and noticed you have the same error as the previous posters:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Then yes, you DO have the same error so, as suggested for the others, try a complete uninstall and reinstall:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
-
same problem here,
If you mean you already checked your log and noticed you have the same error as the previous posters:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Then yes, you DO have the same error so, as suggested for the others, try a complete uninstall and reinstall:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
Worked for me thanks. Sad to still see the baggage carts driving though the wing cones.
Also, sometimes you have to cycle the GSX toolbar button twice to re trigger the menu as the button didn't deselct when the menu closed.
Thanks,
Kian
-
I have a bunch of other fsdreamteam addon installed for both MSFS and P3D. Are you suggesting we reinstall everything? Or is there a specific folder within the addon folder we can target instead?
same problem here,
Then yes, you DO have the same error so, as suggested for the others, try a complete uninstall and reinstall:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
-
Please disregard. You answered in the previous post. I'll let you know if it works.
Yes, your log has the exact same error as the previous one, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
This worked for me. Thanks.
-
Did a complete reinstall as outlined in this forum and I still get the scripting engine error. Error is the same
problem raised by engine or unspecified addon
{}
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart
-
I think the .zip file was broken, so another attemp)
Yes, your log has the exact same error as the previous ones, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
This worked, although I needed to restart the PC after the 3rd and before the 4th step. Once done, the addon activates.
-
Also, sometimes you have to cycle the GSX toolbar button twice to re trigger the menu as the button didn't deselct when the menu closed.
I suggest reading the manual, Page 67 explains how the menu works.
-
I think the .zip file was broken, so another attemp)
Yes, your log has the exact same error as the previous ones, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
Perfect, thanks! Working now :)
-
Hi everyone and thanks fsdt for releasing GSX for MSFS.
I've got the same engine error as everyone else and I tried all the tricks and copied the files provided in this post. Please find attached my couatl file. Looking forward to getting support with this so that I can enjoy GSX.
Best
adlouah
Kindly referring to this post of me where I attached my log file. Can this please be analysed? Please note that I can’t run the live update due to the “unhandled exception” error popping up when trying to start.
-
This is my log file. I've uninstalled and re-installed GSX for both MSFS and P3D.
As an aside, something seems to have broken SODE jetways on P3D with GSX.
-
This is my log file. I've uninstalled and re-installed GSX for both MSFS and P3D.
your error has been discussed in several posts, and it's the sure indication you haven't got the latest files, because the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
-
This is my log file. I've uninstalled and re-installed GSX for both MSFS and P3D.
your error has been discussed in several posts, and it's the sure indication you haven't got the latest files, because the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
I did that, and now GSX in both P3D and MSFS is broken.
I've even tried VPNing to a couple different regions (New York and Italy) of the world and still no dice.
-
I had the same issue, solved by unistall everything and doing a clean reinstall.
The thing is that probably is not possible to keep both the MSFS and the P3D versions, because I installed first the MSFS one, checked the sim and everything was working, then I installed again the P3D version, checked again and the issue is back!
-
The thing is that probably is not possible to keep both the MSFS and the P3D versions, because I installed first the MSFS one, checked the sim and everything was working, then I installed again the P3D version, checked again and the issue is back!
We obviously tested both MSFS version and P3D version, and they surely work together. But it would be best if you install the MSFS last.
-
The thing is that probably is not possible to keep both the MSFS and the P3D versions, because I installed first the MSFS one, checked the sim and everything was working, then I installed again the P3D version, checked again and the issue is back!
We obviously tested both MSFS version and P3D version, and they surely work together. But it would be best if you install the MSFS last.
Which is what I did, and still everything has caught fire.
-
Hello Umberto, again,
I followed all your instructions I could find so far (live update, redownloading the installer, uninstalling all fsdt products incl. the addon manager and manually removing all leftover files, redownloading the installer/live update),...
On any addon scenery (tested various, free/payware, including Basel) the Menu will not appear. On default airports it does - once. Selecting something (stairs/gpu or something else) some vehicles are spawned, and nothing further happens.
The log indicates some files are missing.
As I'm residing in Switzerland, as you do, I assume we're in the same Cloudflare region. Trying various VPN locations doesn't help either.
After trying now for hours to get your product working, I'm really disappointed now. And the only thing I read over and over again is: Try again.
Doing so much troubleshooting for a product which doesn't work (or the installer/infrastructure/file distribution logic/... is broken) can't be expected and you may have to rethink the way this product gets distributed. Right now, it's very frustrating.
Please find attached the newest log from the freshly installed product, with a test in Malta (default scenery) with the Fenix A320. - I confirm, that everything has been uninstalled/deleted/cleaned/reinstalled/reactivated before I ran the test.
I also only have MSFS installed.
Regards
Steve
-
As I'm residing in Switzerland, as you do, I assume we're in the same Cloudflare region. Trying various VPN locations doesn't help either.
Your log doesn't indicate a caching problem, as if you got older files. It seems something must have happened during the installation of the 2nd package gsx-world-of-jetways, which includes lots of object required by GSX. It's normally installed together with the first package, gsx-pro so, check this:
- do you have fsdreamteam-gsx-pro in the Addon Manager\MSFS folder AND with a link to it in the Community ?
- do you have fsdreamteam-gsx-world-of jetways in the Addon Manager\MSFS folder AND with a link to it in the Community ?
If not, uninstall and reinstall, and pay attention if there are any errors.
-
Hello Umberto,
- do you have fsdreamteam-gsx-world-of jetways in the Addon Manager\MSFS folder AND with a link to it in the Community ?
If not, uninstall and reinstall, and pay attention if there are any errors.
I do have a linked "world of jetways" but the target folder does not exist.
I uninstalled it again, reinstalled it again, no change. The jetways folder is missing within the addon manager\msfs directory.
Edit: Liveupdate does not detect the missing folder, and hence won't update it. I created it manually now and liveupdate does import files now. I'll report back.
-
As I'm residing in Switzerland, as you do, I assume we're in the same Cloudflare region. Trying various VPN locations doesn't help either.
Your log doesn't indicate a caching problem, as if you got older files. It seems something must have happened during the installation of the 2nd package gsx-world-of-jetways, which includes lots of object required by GSX. It's normally installed together with the first package, gsx-pro so, check this:
- do you have fsdreamteam-gsx-pro in the Addon Manager\MSFS folder AND with a link to it in the Community ?
- do you have fsdreamteam-gsx-world-of jetways in the Addon Manager\MSFS folder AND with a link to it in the Community ?
If not, uninstall and reinstall, and pay attention if there are any errors.
Yes, they're both there and linked from Community.
-
As I'm residing in Switzerland, as you do, I assume we're in the same Cloudflare region. Trying various VPN locations doesn't help either.
Your log doesn't indicate a caching problem, as if you got older files. It seems something must have happened during the installation of the 2nd package gsx-world-of-jetways, which includes lots of object required by GSX. It's normally installed together with the first package, gsx-pro so, check this:
- do you have fsdreamteam-gsx-pro in the Addon Manager\MSFS folder AND with a link to it in the Community ?
- do you have fsdreamteam-gsx-world-of jetways in the Addon Manager\MSFS folder AND with a link to it in the Community ?
If not, uninstall and reinstall, and pay attention if there are any errors.
Yes, they're both there and linked from Community.
Can you open the world of jetways folder? for me, I got an error... Folder hasn't been downloaded/installed by the installer.
If so, create a folder "fsdreamteam-gsx-world-of-jetways" in your C:\Program Files (x86)\Addon Manager\MSFS directory and then re-run the liveupdater.... I get a ton of of new files as we speak.
-
As I'm residing in Switzerland, as you do, I assume we're in the same Cloudflare region. Trying various VPN locations doesn't help either.
Your log doesn't indicate a caching problem, as if you got older files. It seems something must have happened during the installation of the 2nd package gsx-world-of-jetways, which includes lots of object required by GSX. It's normally installed together with the first package, gsx-pro so, check this:
- do you have fsdreamteam-gsx-pro in the Addon Manager\MSFS folder AND with a link to it in the Community ?
- do you have fsdreamteam-gsx-world-of jetways in the Addon Manager\MSFS folder AND with a link to it in the Community ?
If not, uninstall and reinstall, and pay attention if there are any errors.
Yes, they're both there and linked from Community.
Can you open the world of jetways folder? for me, I got an error... Folder hasn't been downloaded/installed by the installer.
If so, create a folder "fsdreamteam-gsx-world-of-jetways" in your C:\Program Files (x86)\Addon Manager\MSFS directory and then re-run the liveupdater.... I get a ton of of new files as we speak.
Yes, there are a few folders and a couple of JSON files in the root.
-
same problem here,
If you mean you already checked your log and noticed you have the same error as the previous posters:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Then yes, you DO have the same error so, as suggested for the others, try a complete uninstall and reinstall:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
What do you mean by this? Are you saying we need to delete the whole of the "Addon Manager" folder? Completely delete all P3D and MSFS products?
-
Works after awhile. I just waited and it worked.
Doing a clean install would help also as I had GSX for P3D V5
-
The thing is that probably is not possible to keep both the MSFS and the P3D versions, because I installed first the MSFS one, checked the sim and everything was working, then I installed again the P3D version, checked again and the issue is back!
We obviously tested both MSFS version and P3D version, and they surely work together. But it would be best if you install the MSFS last.
I've just tried again, installed the P3D version first and then the MSFS one, not working...
-
We found a problem with some 3rd party airports that have parking with a Jetway bridge, but without the Jetway, a very uncommon situation, which we never encountered before, but it made the Couatl engine crash entering the airport.
The fix is online now.
-
same problem here,
If you mean you already checked your log and noticed you have the same error as the previous posters:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Then yes, you DO have the same error so, as suggested for the others, try a complete uninstall and reinstall:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
Worked for me thanks. Sad to still see the baggage carts driving though the wing cones.
Also, sometimes you have to cycle the GSX toolbar button twice to re trigger the menu as the button didn't deselct when the menu closed.
Thanks,
Kian
Which folder did you delete? The instruction is not clear.
-
Hello again Umberto,
getting closer... The menu opens now (default/addon airport), but for some reason it stalls again (no vehicles come etc.).
What I'm not sure with, are these entries in the log:
Model cache created
SharedMemInterface created
Searching for jetways...
70 StaticObject found
Jetway LOWW_Jetway_Largo at parking Gate 35
Jetway LOWW_Jetway_Corto at parking Gate 23
onEnteredAirport LOWW
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone1'
{'Airport': 'LOWW', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
No MSFS Flight plan loaded, checking Simbrief for a dispatch from LOWW
The loaded flight plan to doesn't match the one on SimBrief, from LGKV to LOWW
aircraftEngaged
emulateMenu_MSFS
emulateMenu_MSFS CHOICE 1
channel.balance = -1
Requested assistance services at Gate 32
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Staircase_CDS_2438_VIE'
{'Airport': 'LOWW', 'Requested assistance services at': 'Gate 32', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Tug_M1A_VIE'
{'Airport': 'LOWW', 'Requested assistance services at': 'Gate 32', 'User Pos': (48.118255251049014, 16.569849793061373, 183.455 m, 2.96975 m, 205.97791183877192, 0.012683035805821419, 0.001745329238474369, 0.00027441938690417675, 3.18211187210083, 1.0)}
emulateText_MSFS [GSX] Handling by Flughafen Wien AG 2.0
emulateText_MSFS [GSX] Catering service requested 2.0
emulateMenu_MSFS
emulateMenu_MSFS CHOICE 0
channel.balance = -1
emulateText_MSFS [GSX] Deboarding requested 2.0
Total payload:2930 lbs.
Estimated number of passengers = 14
context.services.numPassengers = Total payload:2930 lbs.
Estimated number of passengers = 14
14
-
Which folder did you delete? The instruction is not clear.
The instruction said to remove the whole folder YOU chose for the Addon Manager. If you haven't chosen anything, the default is:
C:\Program Files (x86)\Addon Manager
this is the folder to be removed, after you uninstalled the various FSDT products you might have inside.
-
Good Day Virtual,
I believe I've finally have all the updated files, and I no longer get the script engine not running in MSFS (after a manual start), but I only see vehicles moving about my add-ons scenery. The GSX icon does not respond- no menu. I have attached my log file.
Thank you
-
I believe I've finally have all the updated files
No, I'm afraid you haven't yet. This error:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Has been discussed in several posts, and it's the sure indication you haven't got the latest files, because the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
-
Thank you for the clarification.
Your instruction was not clear though as you said "Go into your Addon manager folder (the one you chose for the installation)", which means a folder inside the Addon Manager.
It would have been better saying "Go to your Addon manager folder (the one you chose for the installation) and delete it"?
-
I believe I've finally have all the updated files
No, I'm afraid you haven't yet. This error:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
Has been discussed in several posts, and it's the sure indication you haven't got the latest files, because the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
Noted, I'll give it a go later tonight and revert; thanks
-
Hello,
I had the same problem and solved it like this:
1. Deactivating the licenses of my GSX products
2. Uninstall GSX products in FSDT Universal Installer
http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34098;image (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34098;image)
3. Uninstall FSDT Addon Manager
http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34100;image (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34100;image)
4. Delete the addon directory
c:\Program Files (x86)\Addon Manager\
(Important: You need Administrator rights to delete this folder!)
5. Reinstall FSDT Universal Installer
6. Install and activate GSX MSFS
7. Download the bglmanx_fsdt.dat and overwrite the old one:
http://update.virtualisoftware.com/setup/fsdtroot/couatl64/bglmanx_fsdt.dat
in c:\Program Files (x86)\Addon Manager\couatl64\
8. After Start MSFS I got no reaction from GSX - after starting the
c:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe
with my normal user rights GSX works for me now.
I hope this instructions will be helpfull for you!
-
Hello,
I had the same problem and solved it like this:
1. Deactivating the licenses of my GSX products
2. Uninstall GSX products in FSDT Universal Installer
http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34098;image (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34098;image)
3. Uninstall FSDT Addon Manager
http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34100;image (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=26480.0;attach=34100;image)
4. Delete the addon directory
c:\Program Files (x86)\Addon Manager\
(Important: You need Administrator rights to delete this folder!)
5. Reinstall FSDT Universal Installer
6. Install and activate GSX MSFS
7. Download the bglmanx_fsdt.dat and overwrite the old one:
http://update.virtualisoftware.com/setup/fsdtroot/couatl64/bglmanx_fsdt.dat
in c:\Program Files (x86)\Addon Manager\couatl64\
8. After Start MSFS I got no reaction from GSX - after starting the
c:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe
with my normal user rights GSX works for me now.
I hope this instructions will be helpfull for you!
The only thing is, I can't delete my whole Addon Manager folder otherwise I will delete GSX for Prepar3D...
-
I have this error in my logs too:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
I've followed all the steps to uninstall, delete the folder C:\Users\<USER>\AppData\Roaming\Virtuali, restart the PC, re-install but still have the issue.
Is it just a case of waiting until the files in your servers update then run an update?
Shame that the attempt to avoid websites crashes still came back to bite - you're damned if you do, damned if you don't :)
-
Is it just a case of waiting until the files in your servers update then run an update?
Seems like it, because that's surely not what we have online here.
-
I have the same issue - just bought it this morning and have struggled since to get it up running - without any luck. I have unlinked and uninstalled 2 times - still no luck. I changed the mentioned bglmanx_fsdt.dat - still no luck.
I start manually the Couatl64_MSFS.exe file before starting MSFS2020
Doing anything wrong???
-
Is it just a case of waiting until the files in your servers update then run an update?
Seems like it, because that's surely not what we have online here.
Ok :) Thank you for all your help, really appreciate it. Any idea how long it will take those files to refresh on the servers? If not I'll just try again later :)
-
I don't know how to make any sense out of this. Was having the same issues as others and followed the instructions here. Eventually one time the GSX box popped up letting me warp to another gate. Then rebooted sim and now gsx box won't pop up anymore. To make it even stranger just rebooted and back to the message about the scripting engine not being found.
-
still not starting after re-installed
I've also tried the update function, seems like those files are going into P3D folder, not sure if this is the reason? I still run P3Dv5 and GSX on same computer
-
Works for me.
changing the administrator permissions from read-only to full control for the GSX PRO folders and subfolders (including the shortcut created in "community", in all its folders and restarting couatl as administrator without having to close the simulator. After the cache is fully read, you click on the GSX tab again. For me it solved it. It's a permission and read only problem in the module files.
-
I've also tried the update function, seems like those files are going into P3D folder, not sure if this is the reason? I still run P3Dv5 and GSX on same computer
Please don't post screenshot, but post the log, so I could see which version you started.
-
I accidentally found something interesting: GSX menu launches within MSFS when the product is not activated, once I activate it doesn't run.
Purchased GSX yesterday and I was suffering the same issue as many users over here, about GSX not launching.
After reading and applying all the workarounds described in this thread without success, this morning I tried to reinstall my FSDT addons from scratch, and accidentally discovered that GSX ran if I don’t activate the product within the FSDT installer.
Steps performed:
1. Deactivated and uninstalled all FSDT products within FSDT installer.
2. Uninstalled the FSDT installer and deleted the Addon Manager folder.
3. Reinstalled the FSDT installer and then GSX and other products.
4. Started MSFS and GSX immediately opened with a yellow “Warp to trial mode airport” message shown in the GSX main menu.
5. Found I forgot to activate GSX within FSDT installer, so I closed MSFS and proceeded to activate GSX with my key.
6. Relaunched MSFS and GSX menu is not shown again.
Could this be a licensing issue instead of other causes?
-
Spent a few hours on this tried std airports and all the suggestions here it was a clean install and i've updated a couple of ttimes just to make sure.
Any suggestions i didnt expected this to be still in beta I have a fairly clean install and have only 1 add on airport (not using that currently)
I get COUATL not loaded after starting a flight then, if i externally restart coutl when i hit the GSX button no menu appears
installation went ok
Running in mode: Microsoft Flight Simulator
Python 2.7.16 Stackless 3.1b3 060516 (default, Mar 9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 4801)
log started on Fri Aug 19 16:22:33 2022
connecting to SimConnect...
connected to SimConnect
connected to bglmanx
Simulator version: 11 0 282174 999
RunningMode::pathToInstalledPackages C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages
Loading addons
Loading addon common
Addon common loaded
Loading addon LiveUpdate
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
host file found, checking it
createDefaultContainer
Current locale is English_United Kingdom.1252
Initializing audio...
Available devices:
Generic Software on Speakers (Realtek USB Audio)
Generic Software on U28D590 (2- NVIDIA High Definition Audio)
Generic Software on Headphones (3- Rift S)
Generic Software on Headphones (Oculus Virtual Audio Device)
Generic Software on Realtek Digital Output (Realtek USB Audio)
Preferred device 'generic software on speakers (realtek high definition audio)' not available, using default device
Created OpenAL device: Generic Software on Speakers (Realtek USB Audio)
Device info:
Major version: 1
Minor version: 1
Frequency: 44100
Refresh: 40
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX
Context info:
Vendor: Creative Labs Inc.
Version: 1.1
Renderer: Software
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Slew mode False
bglmanx list contains 24 AddOn(s)
Loading addon LFSB
Addon LFSB not installed or missing one or more files, skipping.
Traceback (most recent call last):
File "<string>", line 97, in loadAddons
File "<string>", line 49, in importAndCreateInstance
ImportError: No module named LFSB
Loading addon GSX
Current sim directory is C:/Program Files (x86)/Addon Manager/couatl64
airportCacheOptimizeSearch enabled, excluding files larger than 4000000 bytes
Airport cache loaded successfully
Addon GSX loaded
Starting system monitors
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart
Loading aircraft.cfg from C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO
Loading engines.cfg from C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO
Loading flight_model.cfg from C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO
Loading gameplay.cfg from C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO
Loading systems.cfg from C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\asobo-aircraft-a320-neo\SimObjects\Airplanes\Asobo_A320_NEO
this airplane has 10 exits
GSX flightLoaded C:\Users\Scott Wilson\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
aircraftDb.py provides aircraft data with priority 2 baseName = ASOBO_A320_NEO
Using aircraft data from aircraftDb.py
Specific .cfg file for ASX320 not found in SimObjects\Airplanes\Asobo_A320_NEO, using standard GSX.CFG file
Specific .cfg file for ASX320 not found in C:\Users\Scott Wilson\AppData\Roaming\Virtuali/Airplanes\Asobo_A320_NEO, using standard GSX.CFG file
User collision geometries reloaded
-
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
This specific error has been discussed in several posts, and it's the sure indication you haven't got the latest files, because the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
-
I had same issue. The reason is we installed gsx for p3d/fsx before. So, gsx for msfs and p3d are same folder. I uninstalled all gsx versions and re-instaled gsx for msfs only, it is working great now
-
Wasted an ENTIRE day with this and nothing works. If this is GSX Pro, I have been robbed.
-
Same problem . No log file but a coatl.err file attached.....
-
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart
-
thanks i was hoping to keep my p3d gsx config i've done a lot of work on it and still use it
why are these 2 products not working together and why are servers not updating with the correct files. If this is the case does the installer not pick this up that a file has been updated but its cache is stale ?
i dont use anything else that's like this. If I hit the fsdt update button again it seems to run through a lot of files each time. i.e. it never says no update required
is this still in beta? i've just spent hours today looking at 1990's log files
Example : Flybywire installer , you have a couple of versions of the aircraft and it keeps everything updated and that's freeware- never had an issue
questions
1)Is there any way for me to get this working and not have to uninstall all the other gsx products ?
2) If I wait until tomorrow or next week, will cloudflare be updated with the correct file so that just hitting the update button will fix this
-
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart
This specific error has been discussed in several posts, and it's the sure indication you haven't got the latest files, becau the servers in your area haven't completed sync all new files, see here:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg173512.html#msg173512
and follow the suggestions there.
-
Still not working after full reinstall.
Still have this error:
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
-
Exactly the same.
Reinstalled countless times now and absolutely nothing works.
My P3d has now been screwed by this release.
THANK YOU
-
I can only confirm this problem is due to a delay of your local node to get the correct file. We refreshed it multiple times by now, and many users reported that after a while, it eventually arrived.
Try to empty your browser cache, it might help.
-
Good job FSDreamteam...same issue here...couatl not working although i started it...no show, also updated the .dat file in the Couatl64 directory...no show...busy for whole afternoon.
Also i have read (after purchase) that it doesn't work in VR....did not see that warning before purchase.
I know FSDT is widely known by statements that it is always a users fault / mistake and never the fault of FSDreamteam so i will also immediatly give up...as nowadays appears to be normal with some FS addons....waste of money.
Very very disappointing.....
-
I know FSDT is widely known by statements that it is always a users fault / mistake and never the fault of FSDreamteam so i will also immediatly give up...as nowadays appears to be normal with some FS addons....waste of money.
I don't know what you are trying to say, you can search ALL threads here, and you won't find A SINGLE case of anybody saying it's the "user's fault", and that's a fact everybody can see.
All problems are surely caused by server caching being slow to catch up with this huge release, that contain 25000 files that need to be replicated on 260 servers. How this explanation translates into saying it's "user's fault", I really don't undertand.
Multiple user confirmed they eventually got all the correct files.
-
So I was able to load up in Denver. Repositioned from one gate to another twice. Then the gsx menu would no longer appear. Exited to the sim menu. Restarted. Attempted to click gsx
"Couatl scripting engine hasn't started"
ideas?
-
Does it start if you start it manually with its desktop icon ? Also, it would be best if you enable Logging in the GSX Settings, so if it happens again, you can check the log and see if there was an error.
-
Will deleting the Addon Manager folder remove all FSDT products for MSFS and P3d? I have many in P3d and wonder if there is a workaround to save those?
-
Will deleting the Addon Manager folder remove all FSDT products for MSFS and P3d? I have many in P3d and wonder if there is a workaround to save those?
Why not just reinstall them using their installers ?
-
I know FSDT is widely known by statements that it is always a users fault / mistake and never the fault of FSDreamteam so i will also immediatly give up...as nowadays appears to be normal with some FS addons....waste of money.
I don't know what you are trying to say, you can search ALL threads here, and you won't find A SINGLE case of anybody saying it's the "user's fault", and that's a fact everybody can see.
All problems are surely caused by server caching being slow to catch up with this huge release, that contain 25000 files that need to be replicated on 260 servers. How this explanation translates into saying it's "user's fault", I really don't undertand.
Multiple user confirmed they eventually got all the correct files.
search
1 of m
http://www.fsdreamteam.com/forum/index.php?topic=19104.0
can you post manually the files that need updating my current v of couatl is 4.0 0.4801
i'm in the uk
my p3d v4 gsx2 is now broken and I havnt uninstalled anything just installed gsx pro for msfs
these are both fsdt products
-
Will deleting the Addon Manager folder remove all FSDT products for MSFS and P3d? I have many in P3d and wonder if there is a workaround to save those?
Why not just reinstall them using their installers ?
Trying to save some time and avoid further errors..
-
search 1 of m
In which you found a post which ended assessing that yes, it was user fault, and another user closed it with:
"You should modify your arrogant attitude. GSX Level 2 functions perfectly without problems otherwise thousands of users would be complaining. It is obvious you have a problem with your system. Do as Umberto says and he will solve your problem"
This was direct at that user, of course. You just made my point, than you very much.
-
I'm also getting the "COUATL scripting engine not starting in MSFS" error and when clicking on the "GSX" entry in the toolbar, nothing happens beside showing the mentioned error.
"Couatl64_MSFS.exe" is running elevated as the FlightSim. I have added the "logFile=couatl.log" to Couatl.ini in "%AppData%\Virtuali", however no log file is being written besides Couatl.err.
I have uninstalled GSX Pro completely, removed "%AppData%\Virtuali\UpdateCache", cleared my Browser Cache and reinstalled it with the latest FSDreamTeam Live Installer and made sure that "bglmanx_fsdt.dat" is matching with the file mentioned in the earlier posts. The Simlinks for "fsdreamteam-gsx-pro" and "fsdreamteam-gsx-world-of-jetways" are present in the Community Folder and pointing to the MSFS Folder within Addon Manager. So far, no success and the same error remains.
I'm residing in Switzerland if it helps pinpointing the Cloudflare Node, if it is of any relevance.
I noticed that the same files are being downloaded by FSDT Live Updater whenever I run it. Is that expected?
Start checking for MSFS updates
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\addon.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\aircraftid.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\areaWithObjects.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\audioManager.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\airlines.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\collisions.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\criticalsection.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\debugMarkers.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\debugUtils.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\digitalClock.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\dynamicShadows.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\engineNoiseEmitter.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\fsm.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\math_utils.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\line.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\messageQueue.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\mpmenu.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\multishape.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\namedtuple.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\preferences.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\rwsl.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\sceneryAddOn.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\simulatorModes.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\togglableDynamicObject.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\train.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\windsock.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\youcontrol.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\cities.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\__init__.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\stars.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\Datatypes.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\__init__.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\Metar.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Ding1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Jetway_Boarding.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Muffler_Idle.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Engine1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Idle1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Idle2.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\seat_belt.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\xCarRev_01.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\xjet1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\baggage_loader\luggage_drop_1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\baggage_loader\luggage_grab_1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\catering\Truck_Crane.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\fueltruck\xTruckRPM1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\fueltruck\xTruckRPM2.wav
DOWNLOADING file D:\FlightSim\Addon Manager\texture\rules_handling.cfg
DOWNLOADING file D:\FlightSim\Addon Manager\model\rules_fueltruck.cfg
DOWNLOADING file D:\FlightSim\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\menu
DOWNLOADING file D:\FlightSim\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\tooltip
GSX Pro updated.
DOWNLOADING file D:\FlightSim\Addon Manager\MSFS\fsdreamteam-airport-lszh-zurich\layout.json
Scenery files digitally signed to [redacted]
FSDT Zurich for MSFS updated.
Start checking for FSX/P3D updates
Checking hosts file
Fixing sim compatibility settings
Fixing sim compatibility settings
Checking if Visual Studio 2008 Runtimes x64 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
DOWNLOADING Visual Studio 2008 Runtimes x64 files
DOWNLOADING file C:\Users\[redacted]\AppData\Local\Temp\vcredist_x64_2008.zip.001
CREATING Visual Studio 2008 Runtimes x64 .ZIP archive
EXTRACTING Visual Studio 2008 Runtimes x64 .ZIP archive in C:\Users\[redacted]\AppData\Local\Temp\
Removing temp file C:\Users\[redacted]\AppData\Local\Temp\vcredist_x64_2008.zip.001
Removing ZIP file C:\Users\[redacted]\AppData\Local\Temp\vcredist_x64_2008.zip
Checking if Visual Studio 2015-2019 Universal Runtimes x64 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
DOWNLOADING Visual Studio 2015-2019 Universal Runtimes x64 files
DOWNLOADING file C:\Users\[redacted]\AppData\Local\Temp\vc_redist.zip.001
CREATING Visual Studio 2015-2019 Universal Runtimes x64 .ZIP archive
EXTRACTING Visual Studio 2015-2019 Universal Runtimes x64 .ZIP archive in C:\Users\[redacted]\AppData\Local\Temp\
Removing temp file C:\Users\[redacted]\AppData\Local\Temp\vc_redist.zip.001
Removing ZIP file C:\Users\[redacted]\AppData\Local\Temp\vc_redist.zip
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\addon.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\aircraftid.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\areaWithObjects.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\audioManager.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\airlines.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\collisions.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\criticalsection.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\debugMarkers.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\debugUtils.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\digitalClock.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\dynamicShadows.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\engineNoiseEmitter.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\fsm.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\math_utils.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\line.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\messageQueue.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\mpmenu.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\multishape.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\namedtuple.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\preferences.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\rwsl.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\sceneryAddOn.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\simulatorModes.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\togglableDynamicObject.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\train.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\windsock.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\youcontrol.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\cities.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\__init__.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\ephem\stars.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\Datatypes.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\__init__.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\common\metar\Metar.pye
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Ding1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Jetway_Boarding.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Muffler_Idle.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Engine1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Idle1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\Truck_Idle2.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\seat_belt.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\xCarRev_01.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\xjet1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\baggage_loader\luggage_drop_1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\baggage_loader\luggage_grab_1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\catering\Truck_Crane.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\fueltruck\xTruckRPM1.wav
DOWNLOADING file D:\FlightSim\Addon Manager\couatl\GSX\sounds\fueltruck\xTruckRPM2.wav
DOWNLOADING file D:\FlightSim\Addon Manager\texture\rules_handling.cfg
DOWNLOADING file D:\FlightSim\Addon Manager\model\rules_fueltruck.cfg
Anything more I can try without uninstalling the entire FSDreamTeam Product line? Thanks
-
"Couatl64_MSFS.exe" is running elevated as the FlightSim. I have added the "logFile=couatl.log" to Couatl.ini in "%AppData%\Virtuali", however no log file is being written besides Couatl.err.
That's because for MSFS, the file must be named Couatl_MSFS.INI, to differentiate from P3D. It's important to get a log, to be sure if the problem is in fact caused by outdate files.
-
Sorry, my bad regarding the INI file. Created the correct one, fired up the sim again, tried to launch GSX via the Toolbar, same behavior as described above.
Log file, which has now been created, is attached with a screenshot from the SIM.
-
I see your log was created during cache rebuild, so it's not entirely unexpected it might not work the first launch. What if you just restart again ?
-
Tried again. Fresh Sim launch, same behavior as before. New log attached.
-
I fixed my problem thanks to help from someone on Avsim, hopefully it can help others. In the file CouatlAddons.ini the disable was set to 1. Changed to 0 and now when I click the GSX icon in the MSFS menu, it opens up GSX menu and everything works.
CouatlAddons.ini file
[gsx]
disable = 0
disable_on_airports = NONE
-
Same issue here also you did a restart.
Running in mode: Microsoft Flight Simulator
Python 2.7.16 Stackless 3.1b3 060516 (default, Mar 9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 4801)
log started on Fri Aug 19 20:25:46 2022
connecting to SimConnect...
connected to SimConnect
connected to bglmanx
Simulator version: 11 0 282174 999
RunningMode::pathToInstalledPackages D:\Program Files
Loading addons
Loading addon common
Addon common loaded
Loading addon LiveUpdate
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
host file found, checking it
createDefaultContainer
Current locale is Dutch_Netherlands.1252
Initializing audio...
Available devices:
No audio device available, continuing with no audio
bglmanx list contains 24 AddOn(s)
Loading addon LFSB
Addon LFSB not installed or missing one or more files, skipping.
Traceback (most recent call last):
File "<string>", line 97, in loadAddons
File "<string>", line 49, in importAndCreateInstance
ImportError: No module named LFSB
Loading addon GSX
Current sim directory is C:/Program Files (x86)/Addon Manager/couatl64
airportCacheOptimizeSearch enabled, excluding files larger than 4000000 bytes
Airport cache loaded successfully
Addon GSX loaded
Starting system monitors
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart
GSX SimStop
Loading aircraft.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Main Menu loaded
GSX flightLoaded flights\other\MainMenu.FLT
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for PH-XRY not found in D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for PH-XRY not found in C:\Users\Laurens Waasdorp\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
GSX SimStart
User collision geometries reloaded
Slew mode False
GSX SimStop
GSX SimStart
Loading aircraft.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for PH-XRY not found in D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for PH-XRY not found in C:\Users\Laurens Waasdorp\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
GSX SimStop
GSX flightLoaded C:\Users\Laurens Waasdorp\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
GSX SimStart
Loading aircraft.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for PH-XRY not found in D:\Program Files\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for PH-XRY not found in C:\Users\Laurens Waasdorp\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
-
From windows desktop I clicked Start Couatl for GSX MSFS icon to load it then the MSFS. On the way it appeared Couatl Debug Window that eventually started displaying several lines text. That CDW never closed. Should I close it before continuing with MFS? I clicked on the MFS and the CDW I guess became behind the MFS screen. Loaded the PMDG 737-700 in SCEL scenery (LatinVFR). From the top screen I select "GSX" and it pops up a message: Couatl scripting Engine hasn't started.
I can't use GSX for now even after reinstalled the FSDT GSX Pro.
I hope in a few days FSDT Live Update will resolve it.
Couatl reporting ...
Patricio Valdes
-
I fixed my problem thanks to help from someone on Avsim, hopefully it can help others. In the file CouatlAddons.ini the disable was set to 1. Changed to 0 and now when I click the GSX icon in the MSFS menu, it opens up GSX menu and everything works.
CouatlAddons.ini file
[gsx]
disable = 0
disable_on_airports = NONE
I had such settings and still the problem.
Patricio Valdes
-
Hi,
my opinion is that the MSFS and the P3d version of GSX cannot run on same machine at the same time.
I have just follow the instrucction to deactivate, uninstall and delete files and directories as it was mentioned earlier in this thread.
(GSX pro, KORD MSFS, KSDF MSFS, GSX, GSXL2, KMEM, KSDF, KORD, KLAX for P3Dv5) (no other P3D version on the machine).
When everything was clean from FSDT, starting fresh install of GSX pro. Starting up couatl and then MSFS and it works just fine.
Then reinstall the other addons including GSX and GSXL2 and nothing works anymore. MSFS give the same Traceback error as initially and quit to work. P3D works with some issues.
When you have a look on the update process of FSDT updater, you can see that GSXpro is first updated and then GSX/L2. What you can see is that some files have the same name. So in my opinion older files from GSX overwrite newer files from GSX pro and cause to malfunction when going to start MSFS with GSX pro again.
I would appriciate a user controlled update where I can skip manually all updates except gsx pro and I suppose it will work again.
BR
Andreas Hövel
EDDC/Germany
-
I mean being "installed" at the same time and not "running". Sorry.
-
my opinion is that the MSFS and the P3d version of GSX cannot run on same machine at the same time.
Of course they do, we designed them to run this way. As I've said in another post, we are rebuilding the P3D full installer now, so it should be less affected by issues with servers not updated.
-
Umberto, has this been tested fot the SU 10 beta to function? It installs fine but the GSX Menu won't come up for me in the sim. The GSX button is highlighted. but nothing happens when I click on it.
-
Umberto, has this been tested fot the SU 10 beta to function? It installs fine but the GSX Menu won't come up for me in the sim. The GSX button is highlighted. but nothing happens when I click on it.
Almost everyone at FSDT use SU10. If you search the forum, the are plenty of identical message, with many solution to try.
-
yeah, I tried all of them including full uninstall and re installation
. have you had any other addons that may cause issue with it., FSrealistic, Rex stuff?
-
From windows desktop I clicked Start Couatl for GSX MSFS icon to load it then the MSFS. On the way it appeared Couatl Debug Window that eventually started displaying several lines text. That CDW never closed. Should I close it before continuing with MFS? I clicked on the MFS and the CDW I guess became behind the MFS screen. Loaded the PMDG 737-700 in SCEL scenery (LatinVFR). From the top screen I select "GSX" and it pops up a message: Couatl scripting Engine hasn't started.
I can't use GSX for now even after reinstalled the FSDT GSX Pro.
I hope in a few days FSDT Live Update will resolve it.
Couatl reporting ...
Patricio Valdes
in the debugwindow open file and click restart gracefully it worked for me as workaround
-
I fixed my problem thanks to help from someone on Avsim, hopefully it can help others. In the file CouatlAddons.ini the disable was set to 1. Changed to 0 and now when I click the GSX icon in the MSFS menu, it opens up GSX menu and everything works.
CouatlAddons.ini file
[gsx]
disable = 0
disable_on_airports = NONE
This solved the problem for me too, as the 2 lines were absent in my %appdata%\Roaming\virtuali\CouatlAddons.ini file, by adding them, now GSX is usable within MSFS.
However, the new issue is that vehicles are spawned with the airline title (Aeromexico in my case) in pink. I think the issue is still the initial one: GSX is not updated due to cloudflare servers not fully synchronized yet.
Update: Problem not solved, as soon as I select stairs to operate or any other action, the menu closes and I'm back to the initial issue. :-X
-
1.- No GSX icon in MSFS,
2. Ran updater, which gave 37 fixes.
3. No icon.
4. Followed directions above to uninstall installer, etc.
5. Reinstalled installer, ran installer for GSX
6. Icon now appears but when pushing it, warning that scripting engine has not started,
7. Manually start scripting engine, warning goes away,
8. Menu does not appear.
What seems to be the problem?
FYI, P3d is now messed up after having to reinstall GSX there.
-
I uninstalled everything the 3rd time was the charm. all works now. it was missing files. My recommendation, uninstall everything including airport. install GSX Pro first before adding your airports back in again. the GSX World was missing the global jetways folder contents was my issue.
-
I too am getting the same issue with the "Couatl Scripting not starting". I do have the Icon in place and I have installed the .dat file and removed all the Visual C ++ files. No Joy!
-
I too am having the same problem. I have tried everything but I am can't find a fix. I am open to any suggestions.
-
From windows desktop I clicked Start Couatl for GSX MSFS icon to load it then the MSFS. On the way it appeared Couatl Debug Window that eventually started displaying several lines text. That CDW never closed. Should I close it before continuing with MFS? I clicked on the MFS and the CDW I guess became behind the MFS screen. Loaded the PMDG 737-700 in SCEL scenery (LatinVFR). From the top screen I select "GSX" and it pops up a message: Couatl scripting Engine hasn't started.
I can't use GSX for now even after reinstalled the FSDT GSX Pro.
I hope in a few days FSDT Live Update will resolve it.
Couatl reporting ...
Patricio Valdes
in the debugwindow open file and click restart gracefully it worked for me as workaround
It didn't work for me. I did restart gracefully and the Couatl Debuging window closed itself doing nothing else. I had to call CDW again, but the MFS GSX top window is doing nothing neither and no messages.
I wait for another time for another FSDT Live Update action.
Patricio Valdes
-
After following the previous instructions of uninstalling ALL FSDT products (To include deactivation) VIA the installer & Associated P3D uninstallers, removing the Addon Folder and reinstalling GSX Pro from scratch, I was able to run GSX Pro with MSFS upon first load.
I had to manually start Couatl as the sim didn't autostart this on my end (Quick fix on my side)
Once I reinstalled P3D - GSX & Airports I attempted to run MSFS again with the same traceback error mentioned on other posts.
"Starting system monitors
Traceback (most recent call last):
File ".\GSX\__init__.py", line 411, in onAppStart
AttributeError: 'module' object has no attribute 'emulateMenu_MSFS'
GSX SimStart"
The only solution I can think of for right now is to remove the P3D airports/GSX & leave MSFS airports/GSX in place.
**Side note, the Icon for starting Couatl for GSX did NOT appear on my desktop until I downloaded the universal installer from another FSDT product on the main page. The original one that was sent via email yesterday did not do this.
**2nd Update - Deleting MOST files in the Addon Manager folder (Except FSDreamteam Stuff from P3D and FlightBeam stuff) I ONLY installed FSDT's Universal Installer & GSX Pro. Upon MSFS first run the program works normally.
When I reinstalled GSX for P3D the same traceback 411 error message returned. The remaining P3D Airports have been untouched, but from what i've seen...something with the GSX installation for P3D is interfering with GSX Pro for MSFS. I did read on another post that the current P3D installers were being rebuilt. I'll wait before attempting to throw GSX back into P3D.
-
It is now the 3rd time I reinstalled the product, and still, couatl wont start automatically. How can I get this resolved?
-
:D I was finally able to get it working and I am pleased with the product!
Steps performed:
1. Deactivated and uninstalled all FSDT products within "FSDT Universal Installer".
2. Uninstalled the "FSDT Universal Installer" via the Windows "Apps & Features" or the old Control Panel.
3. Deleted the "Addon Manager" folder.
4. Deleted the "virtuali" folder at %appdata%
5. Reinstalled the "FSDT Universal Installer"
6. Installed and activated GSX, it took a while, this time I saw it installed 2 components: "fsdreamteam-gsx-pro" and "fsdreamteam-gsx-world-of-jetways" tha latter was missing previously.
As I developed some airports for Mexico sold at Simmarket and the MSFS Marketplace, I already compiled the AFCAD-BGL's to allow GSX to recognize my airports and they seem to work immediatly! 8)
-
My issue was solved by complete uninstall and reinstall.
Suggest this is pinned as it looks like it's causing (and solving) most of the problems.
-
I don't really feel like reinstalling all of my P3D add-ons and airport customizations in order to get this to work and risk also breaking GSX for P3D. I'd rather just shelve this until a patch is pushed out.
-
Hello,
A short feedback from my side:
I use nearly all FSDT Airports in P3Dv5, so Hawaiian Airports Vol. 1 and 2, KFLL, KMEM, CYVR etc. In addition, I have some FSDT Airports for MSFS like LSZH, LFSB and CVYR.
After installing GSX Pro, I had the same problem as everybody - COUATL scripting engine not starting in MSFS. I spent the whole afternoon yesterday with troubleshooting. What helped at the end was deinstalling all FSDT Airports, GSX and the Addon Manager folder and only install GSX Pro and the native FSDT Airports for MSFS. As soon as I installed an old FSDT Airport like KFLL, the scripting error was back again. So it seems, at least on my computer, that it is for the time being not possible to run GSX in P3D and GSX Pro in MSFS together. Luckily, my P3D was not messed up by the deinstallation.
I hope that there will be a solution soon because I still use P3D for longhaul flights and I don't want to miss GSX there.
Kind regards,
Daniel
-
I also get gsx on ms2020 menu but same message about scripting engine not started , has anyone got this workng on ms2020 ?
-
I too am having the same issue. I am NOT willing to uninstall my P3D version so Ill wait to see if a fix does appear for this.
-
now my p3d version is not working properly as well..
"All active jetways stopped due to Main Module (exe) Reset/Disconnection! (N=1)"
and the jetway disappears
-
Surely these issues would have been picked up during 'testing'.
-
Is it just a case of waiting until the files in your servers update then run an update?
Seems like it, because that's surely not what we have online here.
Quick post to let you know that this morning it worked for me - I used the installer to deactivate and uninstall GSX Pro, I used Add/Remove Programmes to uninstall the FSDT installer app, I deleted the Addon Manager Folder (C:\Program Files (x86)\Addon Manager), restarted my PC.
Now with a clean slate I opened the email from FSDT with the download link for the installer, redownloaded it, followed all the normal install steps and now it works fine :)
Looking forward to flying with it, it's the one thing we've all been missing in MSFS.
Good luck folks.
-
Why when I run the live update it stops half way through and then closes?
Same issue here, despite Couatl64_MSFS is running in the Task Manager.
If it's just stuck, it's 100% a server problem. As you might now, we use Cloudflare to prevent the usual "site going down the release day", which happened to every other major release. Because of the Cloudflare network of 260 nodes spread around the world, we don't risk having the server put down, so NOBODY could download anything.
The side effect of this, is that it takes a few hours for all nodes to get all the current files, and this time we updated A LOT of files so, if you run the FSDT Live Update again, all right files will eventually be up.
A crucial file that, it not updated, will stop the program from working, is this one:
http://update.virtualisoftware.com/setup/fsdtroot/couatl64/bglmanx_fsdt.dat
If you can't get the latest version through the updater, because your Cloudflare node still has the previous version, downloading it from here should fix the problem. The file you downloaded MUST be placed in the following folder:
Addon Manager\couatl64
And overwrite the file with the same name which is already there. This should get you going, until the servers catch up.
-
Is it just a case of waiting until the files in your servers update then run an update?
Seems like it, because that's surely not what we have online here.
Quick post to let you know that this morning it worked for me - I used the installer to deactivate and uninstall GSX Pro, I used Add/Remove Programmes to uninstall the FSDT installer app, I deleted the Addon Manager Folder (C:\Program Files (x86)\Addon Manager), restarted my PC.
Now with a clean slate I opened the email from FSDT with the download link for the installer, redownloaded it, followed all the normal install steps and now it works fine :)
Looking forward to flying with it, it's the one thing we've all been missing in MSFS.
Good luck folks.
Do you have GSX for P3D or for MSFS only?
-
With further research an install/uninstalling I can confirm that if you uninstall everything (GSX, FSDT installer, Add On folder) and then fresh reinstall it works. However the minute you install the P3D version it messes up. Hopefully there will be a fix although there are other issues coming to light so it's usual teething troubles for some new software it seems.
-
I also confirm that the moment I uninstalled everything INCLUDING all P3D stuff and reinstalled ONLY the MSFS variant, GSX was suddenly working. Well, for me it was the moment to cut the ends to P3D, which is now gone from my rig, but honestly, this is NOT the way it should have worked out...
-
Same here. Complete uninstall and installing only MSFS airports and GSX-Pro leads to a working GSX in MSFS.
Only adding GSX-L2 for P3D messed it up again. I use P3D a lot... so limiting to MSFS is NO option for me.
Looking forward for a solution..
Btw:
Complete reinstall with FSDT P3D products first, and adding MSFS products, leads to a non functioning GSX in MSFS and P3D as well.
-
Hello,
A short feedback from my side:
I use nearly all FSDT Airports in P3Dv5, so Hawaiian Airports Vol. 1 and 2, KFLL, KMEM, CYVR etc. In addition, I have some FSDT Airports for MSFS like LSZH, LFSB and CVYR.
After installing GSX Pro, I had the same problem as everybody - COUATL scripting engine not starting in MSFS. I spent the whole afternoon yesterday with troubleshooting. What helped at the end was deinstalling all FSDT Airports, GSX and the Addon Manager folder and only install GSX Pro and the native FSDT Airports for MSFS. As soon as I installed an old FSDT Airport like KFLL, the scripting error was back again. So it seems, at least on my computer, that it is for the time being not possible to run GSX in P3D and GSX Pro in MSFS together. Luckily, my P3D was not messed up by the deinstallation.
I hope that there will be a solution soon because I still use P3D for longhaul flights and I don't want to miss GSX there.
Kind regards,
Daniel
I can confirm that is not possible to run GSX in P3D and GSX Pro in MSFS together.
-
I can confirm that the below workflow worked....i now (after two days of work) can start GSX.
:D I was finally able to get it working and I am pleased with the product!
Steps performed:
1. Deactivated and uninstalled all FSDT products within "FSDT Universal Installer".
2. Uninstalled the "FSDT Universal Installer" via the Windows "Apps & Features" or the old Control Panel.
3. Deleted the "Addon Manager" folder.
4. Deleted the "virtuali" folder at %appdata%
5. Reinstalled the "FSDT Universal Installer"
6. Installed and activated GSX, it took a while, this time I saw it installed 2 components: "fsdreamteam-gsx-pro" and "fsdreamteam-gsx-world-of-jetways" tha latter was missing previously.
As I developed some airports for Mexico sold at Simmarket and the MSFS Marketplace, I already compiled the AFCAD-BGL's to allow GSX to recognize my airports and they seem to work immediatly! 8)
-
Just to add you don't have to delete the appdata/virtuali folders. They are just config files for custom airports or aircraft, nothing related to the actual GSX program.
-
Hello,
I have the same issue here ....
Coualt engine not started..
I have tried to replace the file like suggested on page one of this post , it didn't work and now my default jetways aren't replaced anymore by GSX ones as well..
I am really confused and dissapointed that nothing work correctely ..
I have also P3D ans GSX 2 but i don't want to uninstall everything to redo a complete clean installation as i fly on both sim.
Please help
Regards
-
At the moment having GSX installed for P3D AND MSFS is not working correctly for neither of it. You'll have to uninstall one of it for now.
-
At the moment having GSX installed for P3D AND MSFS is not working correctly for neither of it. You'll have to uninstall one of it for now.
yeah, it worked for me. By uninstalling the P3D version the MSFS version works. But now I'm experiencing CTD (never happened before in msfs).
-
At the moment having GSX installed for P3D AND MSFS is not working correctly for neither of it. You'll have to uninstall one of it for now.
yeah, it worked for me. By uninstalling the P3D version the MSFS version works. But now I'm experiencing CTD (never happened before in msfs).
See my post in the CTD thread and try the three solutions. Please report back if it still CTDs.
-
The issues regarding P3D MUST have been known to the developers and have decided to keep quiet.
I have absolutely no intention of deleting P3D from my system and feel it is an absolute disgrace the way this has been handled. If I had been aware of these issues, my bank balance would be £32 better off.
A JOKE
-
In P3D my GSX2 is working but in MSFS i can edit and now FSDT jetways replacing default one aren't there anymore ..
I don't know what to do
Regards
-
In P3D my GSX2 is working but in MSFS i can edit and now FSDT jetways replacing default one aren't there anymore ..
I don't know what to do
Regards
I guess you mean ...in MSFS i can not edit..., right?
Having also spend hours and hours with the initially faithful install into MSFS and then realizing it does not work to edit anything via the MSFS GSX menu PLUS !!! it has jeopardized my P3D GSX I would like to express my full faith - rather than stretch my disappointment too long here - into Umberto and his team that they will in short provide us P3D users and long time GSX supporters with an install process for GSX pro that will leave P3d in tact and untouched and will work off the cuff in MSFS2020.
Umberto and team, I want to patiently wait for that, pls do your best as we have enjoied over the past years so very fondly.
Andreas
-
Gone are the days when I sit here frustrated by software that is simply not fit for purpose and say nothing.
The developers knew of these issues and have chosen to say nothing. FSDT credibility has gone down the toilet.
-
In P3D my GSX2 is working but in MSFS i can edit and now FSDT jetways replacing default one aren't there anymore ..
I don't know what to do
Regards
I guess you mean ...in MSFS i can not edit..., right?
Having also spend hours and hours with the initially faithful install into MSFS and then realizing it does not work to edit anything via the MSFS GSX menu PLUS !!! it has jeopardized my P3D GSX I would like to express my full faith - rather than stretch my disappointment too long here - into Umberto and his team that they will in short provide us P3D users and long time GSX supporters with an install process for GSX pro that will leave P3d in tact and untouched and will work off the cuff in MSFS2020.
Umberto and team, I want to patiently wait for that, pls do your best as we have enjoied over the past years so very fondly.
Andreas
yes in MSFS ...
I try to uninstall everything in the PC and only install GSX pro to see what is happening..
-
Gone are the days when I sit here frustrated by software that is simply not fit for purpose and say nothing.
The developers knew of these issues and have chosen to say nothing. FSDT credibility has gone down the toilet.
agree
this reminds me of the high cpu with couatl64 in p3dv4 with gsx2 the issue went on for a while and we were told it was our machines turned out to be loading too much in the cruise that was being loaded etc
none of us have overly complex systems but most use gsx/gsx2 and im sorry Umberto you say they were designed to work together BUT THEY DONT look at this thread
instead of gaslighting us please please nip off and have a look at some of the code that could be causing these issues instead of forcing us all to play a blind guessing game of try this that like a game of whack a mole. Any other developer I know jusy says let me look into this when a thread gets to this many pages.
I updated again today and nothing new so is my node still not updating. I dont know of anyone that has a file dist system for updates that funtions like this and i work in IT have done for 4 decades.
question : what was the size (people) and duration of the beta period and what ratio of those machines had gsx/gsx2 and your other airports ?
the other strange thing is that normally beta participants are also long term forum members and chip in to help users on launch (MSfS/P3d/Lefterises mob etc) i dont see that here i cant find anything on this thread from someone saying i was in the beta and had prev versions of gsx and this is how i got it to work or this is whats different about my system that may be the issue for you. If anyone reading this was in the beta can you help can you give a quick rundown of your system etc.
I'll say again, regardless of if payware or freeware, there is nothing I use for MSFS that's like this. Nothing I do with GSO Pro works, uninstaling it all and re-installing turning off AV and firewall these are all just distractions that dont help and burn time.
lastlyI dont seem to have the desktop icon to start couatl_MSFS where can i find that ?
-
I'm so disappointed by this release of GSX. I was so excited about it, and now to find out that I have uninstall all my FSDT products for P3D in order to get the MSFS2020 ver. of GSX to run. How could the developers allow this to happen and there is no way they didn't know in advance that this was an issue. I guess I'll just uninstall GSX Pro until the developers get this all sorted out.
-
Hello
I AM ''happy'' to see that i am not the only one with that problem. I got this message too ''COUATL scripting engine not starting in MSFS''
Does anyone know whats going on
any solution thanks
-
Hello
I AM ''happy'' to see that i am not the only one with that problem. I got this message too ''COUATL scripting engine not starting in MSFS''
Does anyone know whats going on
any solution thanks
Uninstall all the FSDT airports, GSX for P3D, GSX Pro, addon manager, All FSDT programs and also the Virtuali directories you have on your system, then download FSDT installer again and only install GSX Pro (this is waht worked for me and a few others)
Don't forget to deregister your FSDT products before uninstalling !
-
Problem solved.
There is another long thread about this problem on this forum. I solved my issue with this by uninstalling all FSdreamteam products, and Virtuali on BOTH, P3rd and MSFS. then reinstalling on MSFS ONLY. That got it working.
Papagiorgio
-
No NOT solved!!
For previous owners of GSX within P3D this is not a solution. I and many other people are still using P3D and want GSX to work within that sim as well as FS2020. The developers need to get this problem sorted and quickly in my opinion.
Uninstalling a prefectly good working program within P3D is not what I and many others are prepared to do.
I have been a fan of FSDREAMTEAM products within P3D, but this product is dreadful and should not have been released without proper testing in BOTH sims. And THAT has not happened with this release.
-
No NOT solved!!
For previous owners of GSX within P3D this is not a solution. I and many other people are still using P3D and want GSX to work within that sim as well as FS2020. The developers need to get this problem sorted and quickly in my opinion.
Uninstalling a prefectly good working program within P3D is not what I and many others are prepared to do.
I have been a fan of FSDREAMTEAM products within P3D, but this product is dreadful and should not have been released without proper testing in BOTH sims. And THAT has not happened with this release.
Huh, you aren't happy with the solution of uninstalling a bunch of other products you bought and paid for to get one to work? Wow, so hard to please. /s
-
I Uninstalled GSX, GSX 2 and GSX Pro. I also deleted the whole Addon Manager folder and started from scratch. I uninstalled the FSDT installer too. I installed a new installer and installed GSX Pro for MSFS. It worked fine. I proceeded to install GSX & GSX 2 for P3Dv5. I launched P3D and everything worked fine. When I went back to MSFS I got the dreaded Couatl error... I will wait for a better patch from FSDT.
-
I also have the same problem.
After re-installing everything, I am now able to open the menu from the menubar but it will disappear after a short while.
Regards.
Michel
-
Only thing that may fix things for both sims is a working patch from FSDT. I can have either sim working by deleting one. I rather wait for a working patch.
-
Having the same problem here.
Uninstalled everything FSDT from my PC, manually removed the Addon Manager folder, the re-installed just the MSFS products. This worked, flew one flight with no problems.
Then, I re-installed my P3D FSDT products, and tried MSFS again, even after running auto-updater, etc. and no luck. COUATL engine couldn't start.
Quite disappointed since like many, I still use both P3D and MSFS.
edit: P3D GSX isn't working either, so back to step 0 I go!
-
I Uninstalled GSX, GSX 2 and GSX Pro. I also deleted the whole Addon Manager folder and started from scratch. I uninstalled the FSDT installer too. I installed a new installer and installed GSX Pro for MSFS. It worked fine. I proceeded to install GSX & GSX 2 for P3Dv5. I launched P3D and everything worked fine. When I went back to MSFS I got the dreaded Couatl error... I will wait for a better patch from FSDT.
As I understood, FSDT suggests NOT to install P3D *after* MSFS but before. So the order of installation should be after deinstalling the whole stuff as follows:
1. GSX
2. GSX Level 2 Expension
3. P3D airports
4. GSX Pro
5. MSFS airports
Kind regards,
Daniel
-
I Uninstalled GSX, GSX 2 and GSX Pro. I also deleted the whole Addon Manager folder and started from scratch. I uninstalled the FSDT installer too. I installed a new installer and installed GSX Pro for MSFS. It worked fine. I proceeded to install GSX & GSX 2 for P3Dv5. I launched P3D and everything worked fine. When I went back to MSFS I got the dreaded Couatl error... I will wait for a better patch from FSDT.
As I understood, FSDT suggests NOT to install P3D *after* MSFS but before. So the order of installation should be after deinstalling the whole stuff as follows:
1. GSX
2. GSX Level 2 Expension
3. P3D airports
4. GSX Pro
5. MSFS airports
Umberto, could you please confirm this? I don't know what happens if the Live Updater is run.
Kind regards,
Daniel
-
Yes, I said in many threads we know it's possible that having the P3D version previously installed might cause issue.
More precisely, is not SUPPOSED to cause issues because, the moment you install GSX Pro, the updater will download all the latest files, which are designed to be cross-compatible with both. The issue is, if your local cloudflare node is stuck with the old P3D-only version of a particular piece of code, the updater won't get the new one, and this surely cause issues.
Installing the P3D version before might fix the problem or not, depending if your local cloudflare node is fully updated or not. In fact, if we could be sure all cloudflare nodes are ready, the installation order won't even matter, because the Live update which is ran as the last step of every installer would surely update everything to the last version, no matter how old your P3D installer is. That's because even the updater program *ITSELF* is downloaded in realtime by the whatever old P3D installer you have.
However, since it seems that for some users the problems are still happening, it means the whole cloudflare network hasn't been fully updated yet so, IN THE MEANTIME, we can offer the following suggestions:
- Install GSX Pro after GSX and GSX L2. In fact, any other installation order can simply summarized as "install GSX Pro LAST"
- If that still doesn't work, and you have errors you are not normally supposed to have, like the one reported by so many users in line 411 of GSX (which is 100% sure it's a server problem, since that line doesn't contain that code anymore now, so it's coming from an old file), if you remove GSX for P3D, possibly also clean up the Addon manager\Couatl and Addon manager\Couatl64 folders as well, and install just GSX Pro, it should get you going in MSFS, at least. This while you wait an update for the P3D full installer, which will contain all the latest files, so it won't install old stuff in any case.
-
I only have MSFS installed and do not have any components installed for anything related to P3D and it still does not work for me. If it loads without the scripting engine error, the window simply does not open. I can click all day and nothing happens. Other times I switch airports and it will say scripting engine is not running and it is plainly seen in the taskbar.
I feel like the time for blaming out of date servers is past and it's time to start thinking of a new solution. Even the lowest of budget hosting providers should be able to replicate content by now.
-
I only have MSFS installed and do not have any components installed for anything related to P3D and it still does not work for me. If it loads without the scripting engine error, the window simply does not open. I can click all day and nothing happens. Other times I switch airports and it will say scripting engine is not running and it is plainly seen in the taskbar.
Which only means my previous answer might not apply TO YOU.
I feel like the time for blaming out of date servers is past and it's time to start thinking of a new solution. Even the lowest of budget hosting providers should be able to replicate content by now.
It's also wrong of you to imply that you are "sure" servers are unrelated to YOUR (likely different, but we'll see about that), without having any evidence of that. But that's besides the point. The point is I was replying to a VERY SPECIFIC question about installation order, which was a follow up to explain why installing only for MSFS DID FIX a problem some users with P3D were having.
And this is CLEARLY a server replication problem, because what we have online IS surely compatible with both. Which also means, regardless of what you might think of my explanation to be an "excuse", it clearly isn't, otherwise we wouldn't have users that fixed their problem by removing the P3D version ? Even assuming YOUR case is not related to server, which is something we haven't proved yet, the very existence of those other cases is a clear proof that *some* servers are still not fully updated.
It would have been useful if you posted your Couatl.LOG after a startup, instead.
-
It's also wrong of you to imply that you are "sure" servers are unrelated to YOUR (likely different, but we'll see about that), without having any evidence of that.
I wasn't trying to imply anything other than the response about the servers not having current copies yet is one that needs to be put to bed. If after two full days your servers don't have the most recent files then it is quite possibly the worst hosting service I've heard of. Even if that turns out to be true, perhaps it is time for you to find an alternate solution at this point is it not? Doesn't seem reasonable to ask customers to simply wait for an unknown time and run the updater an undetermined number of times hoping that someday it will work.
I'm a long time customer which is why I didn't think twice before clicking the buy button on this one, but this launch followed by the subsequent argumentative behavior when your customers are reaching out for help has really soured my view of FSDT as a whole.
By the way, I did look for that log file which does not appear anywhere on my drive, though I do see Couatl.err, not sure if that is the same thing. The manual says to enable I have to edit the %APPDATA%\virtuali\COUATL _ MSFS.INI file which does not exist. I have %APPDATA%\virtuali\Couatladdons.INI, is that what needs to be edited?
-
I wasn't trying to imply anything other than the response about the servers not having current copies yet is one that needs to be put to bed. If after two full days your servers don't have the most recent files then it is quite possibly the worst hosting service I've heard of.
And that's where you completely missed the whole explanation. OUR servers ARE perfectly updated, to the second. The issue is, you are NEVER connected directly to them!
If you could really connect directly, the server would have crashes in a couple of minutes, if not less, after release. In that case, the result would have been that *nobody* would be able to download *anything* and, the moment we restarted the server, it would crash again. And you wouldn't even be able to come here to get help, because also the forum would have been down with the server.
To make something like this working, we MUST use a CDN (Content Distribution Network), we use Cloudflare, which is by far the most popular. They have about 260 nodes worldwide, so users will connect to the one closer to their location. It's likely each node would have hundreds if not thousands of servers, so it's a fairly complex system. It also became very obliquus, to the point that when they have issues, millions of sites would be affected at the same time, like the sky is falling, the end of the world, last one happened very recently, in June:
https://www.theverge.com/2022/6/21/23176519/cloudflare-outage-june-2022-discord-shopify-fitbit-peleton
Cloudflare's job is to REPLICATE files from individual hosts on their own servers, but it's not as if they just "copy" the whole server at once, that would be highly inefficient. They download a file from our server as soon as the first user will ask a download for it. Cloudflare check if it has the file, and if it hasn't or it has an older version, it will download the current version from our site will serve *that* to users, and will store that file until it gets changed again. The next user asking for that file, Cloudflare will see the file hasn't changed, so it will just serve the file without downloading it again from us.
This happens automatically, we don't have much control over which node gets what, the only thing we can do is asking for a forced "purge" of a particular file, so Cloudflare will just remove it, resulting in the next user asking for it surely getting it from our server, because Cloudflare simply doesn't have it anymore.
Obviously, we have a fully automated and tested system that, as soon we change a file, will send a request to purge it from Cloudflare's cache so, the challenges are:
- The purge command *itself* must be replicated. If I sent a purge command to Cloudflare to remove a specific file from the cache, the command must be replicated on ALL Cloudflare servers, removing it from all of them, so regardless where the next users asking for that file is coming from, every node would behave the same way, and will download the file from our server, to be ready to be serve directly to the next user, and so on.
- When many users are downloading, the servers will likely perform the purge commands with some delay.
- GSX is very large, over 25000 files, and all of them, eventually, must arrive on all 260 nodes.
So yes, the server issues are real. Or should have said, the challenges of releasing a popular product with a big amount of files, over a CDN with 260 nodes, which is the only way to distribute such stuff, in a way that won't block a single access server, no matter how powerful it is.
-
I have a question. When updating now window it shows updating 2 out of 37 ands the bars are going up but after that the updater disappears. Is that normal? what happened to the rest of the update?
-
I have a question. When updating now window it shows updating 2 out of 37 ands the bars are going up but after that the updater disappears. Is that normal? what happened to the rest of the update?
The thing is you are probably assuming here the updater is only used for GSX. It used for all FSDT products and, put them together, they now require 37 steps to update them all. Unless you have everything from FSDT, you'll never see all steps performed.
And, since the Live Update, when started with the "Live Update" icon is supposed to be a "quick, update everything", which can possibly even be called in a batch file, since at the end of the process all products are updated and that interface can't do anything else, the only option you have at the end is to quit so...it just quits, saving you from an unnecessary extra click at the end, which will annoy those wanting to automate the whole process.
If you want to be "in control", reading messages, decide what to update, check thinks, don't use the Live Update icon, but the Installer icon, which does exactly the same thing, as updates are concerned, only it let's you be in control of the process.
-
Umberto, hello.
as outlined being also in the corner of running p3d and msfs and wanting of course to work both together yr sentence in one of your recent below text is the most interesting for me, guidance right now I have completely deinstalled and deactivated GSX pro after lots of too ans fro, and have P3D GSX and GSX2 working fine as they did for so long time, and wait for your GSX Pro installer solution leaving P3D untouched.
Yes, Umberto, I have surely read all, repeat all messages in this forum and know that the service provider servers should provide me with everything to have things working in parallel, but until now to no avail my end and many other ends….
now the the sentence of yours important for me was:
quote
This while you wait an update for the P3D full installer, which will contain all the latest files, so it won't install old stuff in any case.
unquote
So
1. do I understand correctly that you will publish a new installer.exe file on your shop downloadpage soon which will achieve things working paralell? That would be great
2. will you let all purchasers of GSX pro know that its ready by direct email providing the link to such workable installer?
tks for answer
Andreas
-
Umberto,
and 3.
can you provide with such new installer the exact order of steps to take for those who have both P3D and MsFs on the machine, so that we can before using such installer take the right steps.
tks
Andreas
-
And that's where you completely missed the whole explanation. OUR servers ARE perfectly updated, to the second. The issue is, you are NEVER connected directly to them!
As someone who has worked in the IT industry for nearly 30 years I can tell you that I as the customer do not want or need to make any distinction between "your" servers, and the distribution network you use to deliver your product. That is minutia that you as the vendor make choices to try and deliver the best experience possible and you take ownership of those choices regardless if you physically own those services or not. Do you think my users give two shakes that it is really M365 that is down when their email doesn't work? Not one little bit. We still get the tickets and we still have to own that outage without explaining to the user ad nauseum that it really isn't "our" servers that are down.
This stuff happens and as the provider you should be owning that and looking for alternatives when plan A fails, not shrugging your shoulders and pointing the finger to your partners.
-
here is a protkol from the /appdata/Virtuali Couatl.err
i have CDTs and couatl not strting
couatl v4.8 (build 4801)
panic log started on Sun Aug 21 09:54:23 2022
problem raised by engine or unspecified addon
{}
Simulator version (from MAIN.DLL) is 11.0.282174.999
isPBRAvailable returned False
isRTTAvailable returned False
GetSimObjectsFolder() returned C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
GetAdditionalSimObjectsFolder() returned C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
GetAdditionalSimObjectsFolderV5() returned
GSX SimStart
Error: exception UNRECOGNIZED_ID in call SetDataOnSimObject param #2 '1419435600'
{}
Error: exception UNRECOGNIZED_ID in call SetDataOnSimObject param #2 '1419434480'
{}
GSX SimStop
Loading aircraft.cfg from E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading engines.cfg from E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading flight_model.cfg from E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading gameplay.cfg from E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
Loading systems.cfg from E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320
this airplane has 10 exits
WASM timeout timeElapsed 0
Main Menu loaded
GSX flightLoaded flights\other\MainMenu.FLT
aircraftDb.py provides aircraft data with priority 2 baseName = FNX320
Using aircraft data from aircraftDb.py
Specific .cfg file for D-AIQS not found in E:\MSFS\Community\fnx-aircraft-320\SimObjects\Airplanes\fnx320, using standard GSX.CFG file
Specific .cfg file for D-AIQS not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\fnx320, using standard GSX.CFG file
User collision geometries reloaded
GSX SimStart
User collision geometries reloaded
Slew mode False
GSX SimStop
GSX SimStart
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
GSX SimStop
GSX flightLoaded C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
GSX SimStart
User collision geometries reloaded
Loading airport EDDS from \\?\E:\MSFS\Community\justsim-airport-edds-stuttgart\scenery\world\scenery\edds.bgl
Creating model cache...
Model cache created
Searching for jetways...
SharedMemInterface created
29 StaticObject found
onEnteredAirport EDDS
GSX SimStop
GSX SimStart
User collision geometries reloaded
GSX SimStop
Main Menu loaded
GSX flightLoaded flights\other\MainMenu.FLT
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
GSX SimStart
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
onExitedAirport EDDS
User collision geometries reloaded
GSX SimStop
GSX SimStart
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
GSX SimStop
GSX flightLoaded C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
GSX SimStart
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
User collision geometries reloaded
Searching for jetways...
29 StaticObject found
onEnteredAirport EDDS
GSX SimStop
GSX SimStart
User collision geometries reloaded
GSX SimStop
Main Menu loaded
GSX flightLoaded flights\other\MainMenu.FLT
Loading aircraft.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading engines.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading flight_model.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading gameplay.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
Loading systems.cfg from E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700
this airplane has 15 exits
Airplane major/minor version: 737 700
GSX SimStart
aircraftDb.py provides aircraft data with priority 2 baseName = PMDG 737-700
Using aircraft data from aircraftDb.py
Specific .cfg file for EL-SEV not found in E:\MSFS\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700, using standard GSX.CFG file
Specific .cfg file for EL-SEV not found in C:\Users\Peter\AppData\Roaming\Virtuali/Airplanes\PMDG 737-700, using standard GSX.CFG file
onExitedAirport EDDS
User collision geometries reloaded
GSX SimStop
Connection with Microsoft Flight Simulator lost (has it crashed?)
disconnected from SimConnect.
-
Hi
Tried to fix it according the steps, but still have the same issue as others.
pls see my coutal.log
brgds
Massimo
-
I have the same problem. I deleted all FSDT files on my computer and installed it new. butno change. I am very disappointed to have iinvested 37€ for nothing. Even the advises of the admin are not very helpful
-
So
1. do I understand correctly that you will publish a new installer.exe file on your shop downloadpage soon which will achieve things working paralell? That would be great
2. will you let all purchasers of GSX pro know that its ready by direct email providing the link to such workable installer?
Yes, at least it would be good if you could post a message and stick it on the top when the new installer is ready. As I understood, installer for MSFS is fine, there will be just a new installer for GSX and GSX L2 Expansion so that no newer files from GSX Pro are overwritten when installing GSX for P3D. I assume, we can then install P3D on the top of MSFS.
Kind regards,
Daniel
-
I got the same "couatl scripting engine not starting" message.
There iis an interesting contribution on AVSIM
https://www.avsim.com/forums/topic/623125-exexml-not-starting-programs/?tab=comments#comment-4827713
that helped me: change the encoding of exe.xml to ntf-8.
Regards Andreas
-
So
1. do I understand correctly that you will publish a new installer.exe file on your shop downloadpage soon which will achieve things working paralell? That would be great
2. will you let all purchasers of GSX pro know that its ready by direct email providing the link to such workable installer?
Yes, at least it would be good if you could post a message and stick it on the top when the new installer is ready. As I understood, installer for MSFS is fine, there will be just a new installer for GSX and GSX L2 Expansion so that no newer files from GSX Pro are overwritten when installing GSX for P3D. I assume, we can then install P3D on the top of MSFS.
Kind regards,
Daniel
Umberto,
supposing that my understanding as per my items 1. and 2. are correctly understood and there will be a new installer, then I would strongly suggest that such new installer is for MSFS GSX pro, making shure that such new install of GSX pro will not jeopardize existing P3d installs which are already working well on our machines, rather than as expressed above a new installer for P3d. Why a new installer for GSX pro rather than for P3D to coexist with GSX pro?
because such new Msfs installer wil also serve well for all future buyers of MsFS GSX pro who have already P3d Gsx running on their machines and avoid them to uninstall that, then install msfs Gsx pro and then P3D gsx again.
anyhow, looking forward to your way forward to solve this, thanks,
Andreas
-
I have this issue since I bought GSX Pro on Sat 20th August about 12:00am (Noon) and aft I installed GSX Pro the 1st time.
Latest try of install was at about 5pm. Before that I uninstalled GSX Pro and the universal installer several times, restarted the PC and downloaded the lastest universal installer, installed that and began to install GSX pro thru that.
Lockheed Martin's Prepar3D v4.5 HF3 is installed on the same system for years now. And so is GSX & GSX Level2 Expansion. All was running fine. Until I 1st installed GSX Pro.
Yes, I said in many threads we know it's possible that having the P3D version previously installed might cause issue.
More precisely, is not SUPPOSED to cause issues because, the moment you install GSX Pro, the updater will download all the latest files, which are designed to be cross-compatible with both. The issue is, if your local cloudflare node is stuck with the old P3D-only version of a particular piece of code, the updater won't get the new one, and this surely cause issues.
Sorry, if you update your products via the Live Update you surely know which revision of a file should be downloaded. If the CDN does deliver an older one, why don't you reject that file and reload that from your server(s) where the actual files are?
I always made Live Updates of the installed FSDT products when I got informed. Till today I thought my FSDT products are up-to-date. That doesn't seem so!
Regards
Hans
-
This stuff happens and as the provider you should be owning that and looking for alternatives when plan A fails, not shrugging your shoulders and pointing the finger to your partners.
Sure but, the issue is, the cloudflare issue will sort out automatically anyway, and our time is completely filled up with:
- replying to forum posts
- replying to email
- working on finding and removing issues that are NOT server-based
-
on finding and removing issues that are NOT server-based
Let's hope so, because from some of the videos I've seen on machines that it is apparently working on, there is a lot of that to fix. Until then it is sadly uninstalled from my machine because I can't even get that far.
-
I think the .zip file was broken, so another attemp)
Yes, your log has the exact same error as the previous ones, some files are not the current version. Try a complete removal:.
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
Did this sadly no fix :/
Also manually started "Start Couatl for GSX MSFS" on my desktop. Couatl starts up, but in the sim it still says that it has not started. (Ran as admin)
-
Also manually started "Start Couatl for GSX MSFS" on my desktop. Couatl starts up, but in the sim it still says that it has not started. (Ran as admin)
As discussed in all threads related in any way to Couatl not starting, you should always provide a log of the startup, which will help us to identify the problem and suggestion a solution.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar or start it from its icon on the Desktop
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
-
Hey, I am having similar issues as others have posted about above. Fresh install today, GSX Level 2 already installed. Attached is my .log file.
Thanks
-
How long ago you ran the Live Update ? Could you please try again now, and see if you got the correct files ? We asked for a refresh of files a couple of times today.
-
How long ago you ran the Live Update ? Could you please try again now, and see if you got the correct files ? We asked for a refresh of files a couple of times today.
Just ran live update through FSDT Live Update, reloaded sim, same issue.
-
How long ago you ran the Live Update ? Could you please try again now, and see if you got the correct files ? We asked for a refresh of files a couple of times today.
Just ran live update through FSDT Live Update, reloaded sim, same issue.
same here still broken with menu error in log file
couatl loads in taskbar and shows cache ok
pressing the GSX menu button in MSFS gives coutl not started
firewall and nod32 AV off
re-installed - same
Please post, manually, the updates we need if you think this will fix it bypass the currently broken distribution system being used. GSX pro again broke GSX and GSX2 for p3d and my machine is now restoring again to friday
This isnt a functioning product and I cant understand why you still havnt worked back from that menu error through your code to find the steps that need to be done to a) get this working in MSFS and b) stop the GSX Pro install breaking our P3d versions of GSX.
I would like a refund . How do I go about this ?
-
running MSFS with Couatl_MSFS.ini. No Couatl.log produced. but Couatl.err appended as ZIP.
-
I removed ambitiouspilots-toolbar-pushback and now I can see the characters in services cars but always dont see the GSX main menu when I click on GSX bouton in toolbar.
Here my log file
Im sure you will find solution soon. Good luck :)
-
hello,
I think I have same problem as other users.
Attached couatl.zip = case when couatl do not start automatically
Then I stay in the sim and made coutl start manually, wait a litlle and then when I click on GSX app it is working attached couatl1.zip
I hope it will help you find a solution
Ps: i did before the proposed procedure
Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again
-
Report attached
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If you run the FSDT Live Update, it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline and it's sure to contain the latest files, as of today.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
This offline installer will make do until we'll be reasonably sure almost all cloudlare nodes have been updated. You can recognize if YOUR node has, by simply noticing if the Live Update doesn't download anything if you run it after this offline installer. If this happens, it means your local cloudflare node is now fully updated, so you don't need to use this anymore, just the Live Update.
-
Also manually started "Start Couatl for GSX MSFS" on my desktop. Couatl starts up, but in the sim it still says that it has not started. (Ran as admin)
As discussed in all threads related in any way to Couatl not starting, you should always provide a log of the startup, which will help us to identify the problem and suggestion a solution.
- open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl_MSFS.ini in the %APPDATA%\Virtuali folder
- Restart Couatl from the Tray Bar or start it from its icon on the Desktop
- Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content
For some reason I cannot attach my couatl log because an error will occur when trying to post. I have uploaded my log on wetransfer: https://we.tl/t-87Xnr45TFG
Thanks in advance
-
Ps: i did before the proposed procedure
Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again
Thanks
This work for me 😁
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
Seems to work Umberto. I was just about to post, that my copy still doesn't work after running the Live Updater. (Log file from *BEFORE* installing the new installer you just posted is attached, if it is of any interest).
After using the new "quick and dirty" Installer and firing up the SIM again, GSX Pro is now finally working :)
-
This fixed it for me aswell!! Like magic
-
Do I just run this installer? Nothing more is required (no need to uninstall anything)?
GSX is terrific and it makes one feels like he is in a real-world environment (jetways attached, boarding/deboarding, refueling, push-back)
PS => Does this work with P3Dv5 or it needs another installer?
Tks
-
Yes, the file updates all the Addon Manager, so it can be used for P3D as well
-
This fixed for me also- Just wanted to add to the list of fixed people!
-
I ran the provided Addon Manager installer and I still have disappearing jetways after calling GSX Jetways service with FSX, P4D and P5D.
Is this an MSFS question ? Is the MSFS version working for you ? If you have FSX/P3D question, post them in the relevant forum.
-
I ran the provided Addon Manager installer and I still have disappearing jetways after calling GSX Jetways service with FSX, P4D and P5D.
Is this an MSFS question ? Is the MSFS version working for you ? If you have FSX/P3D question, post them in the relevant forum.
Oops! so sorry Umberto, my mistake posting here. I apologize about.
Patricio Valdes
-
Yes, the file updates all the Addon Manager, so it can be used for P3D as well
Umberto, are you sure that can be used for P3D as well? It didn't work for my P3D sims.
Patricio Valdes
-
Yes, people are saying that, but I cannot reproduce any problem. Tried it with P3D 4.5 and 5.3.
-
Yes, people are saying that, but I cannot reproduce any problem. Tried it with P3D 4.5 and 5.3.
All users from GSX FSX/P3D thread said not working for P3D sims.
Yes, it worked for MSFS.
Patricio Valdes
-
All users from GSX FSX/P3D thread said not working for P3D sims.
Which is why we should discuss about it *there*.
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
Thank you this worked. I have P3D GSX installed prior to release of MSFS version. Cloudflare in HKG was still pushing out the old version till now so would get the "Line 411" error, preventing the menu from popping up in MSFS.
After downloading from GDrive, running the .exe, works fine on MSFS. Tried 3 different airports and sim launches.
This was incredibly frustrating as users, and I'm sure for you as a developer too not having control over what files were getting pushed out via Cloudflare. In any case, glad to have it sorted for now. All the best and look forward to future updates!
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
Just please fix your product instead of asking us to do your work for you. I have been a long time customer, never had problems like this, please fix your updater!!!
-
Checking now for p3d v4.5 and then for msfs 2020 , so far looks ok ?
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
with the provided installet it works
thanks
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
Like I already said in
http://www.fsdreamteam.com/forum/index.php/topic,26738.msg175358.html#msg175358
The Universal Installer and Live Update will still download files again and again after using this Auto Manager.
-
I have all ways to make it work, ok
its time you get your act together ,
refund or repair
-
Hi,
my opinion is that the MSFS and the P3d version of GSX cannot run on same machine at the same time.
I have just follow the instrucction to deactivate, uninstall and delete files and directories as it was mentioned earlier in this thread.
(GSX pro, KORD MSFS, KSDF MSFS, GSX, GSXL2, KMEM, KSDF, KORD, KLAX for P3Dv5) (no other P3D version on the machine).
When everything was clean from FSDT, starting fresh install of GSX pro. Starting up couatl and then MSFS and it works just fine.
Then reinstall the other addons including GSX and GSXL2 and nothing works anymore. MSFS give the same Traceback error as initially and quit to work. P3D works with some issues.
When you have a look on the update process of FSDT updater, you can see that GSXpro is first updated and then GSX/L2. What you can see is that some files have the same name. So in my opinion older files from GSX overwrite newer files from GSX pro and cause to malfunction when going to start MSFS with GSX pro again.
I would appriciate a user controlled update where I can skip manually all updates except gsx pro and I suppose it will work again.
BR
Andreas Hövel
EDDC/Germany
Hi,
I made the same procedure and GSX Pro work fine, but if I reinstall GSX2 for P3DV5, GSX Pro do not work; Now I have only installed GSX Pro.
Customer of FSDT for many years, and FSDT is one of the few, very few, houses of trusted products.
I hope a solution for the problem; I do not thing to unistall P3DV5 for now.
Emilio Casalduero
Madrid / España
-
I did as stated here: http://www.fsdreamteam.com/forum/index.php/topic,26480.msg175191.html#msg175191 (http://www.fsdreamteam.com/forum/index.php/topic,26480.msg175191.html#msg175191).
Couatl Engine is now started but no GSX Menu appears.
-
I have all ways to make it work, ok
its time you get your act together ,
refund or repair
[/quote
Do you really think he's doing nothing?
-
By chance I made a "check update" in the universal installer.
Now I have the GSX Menu for the 1st time! Puh!
-
I have all ways to make it work, ok
its time you get your act together ,
refund or repair
[/quote
Do you really think he's doing nothing?
yes, nothing to help get it working. How many hours has this imposed on all of us that just wanted to use the product? Here the issues
1) Using an archaic file distribution system that needs poking with a stick or speaking to people to get things updated. Took 4 days for me to pick up the new couatl_MSFS. Don't blame cloudflare dont use them. Use github, do what flybywire a320, do a folder sync, it's immediate and no cost; and a modern distributed file and folder sync.
2) Not fully tested with FSDT existing products I have also seen in this thread people doing just a clean install and it's ok. But, on top of GSX/GSX2 there are issues. As the code base is split couatl and config files have to become couatl_MSFS and_P3D. This means making sure all the legacy code and installers now reference one of the two and some have obv been missed. How this got past beta testing I really don't know.
3) Beta testers , where are they, usually you get some on the forums after something is released helping/chipping in what to try. Hello any beta testers there that can help us get this working ? If no beta testers chip in here what can we start to assume ?
-
now working but buggy needs work .
-
This latest workaround enable installation of GSX for MSFS, correct? Does it enable the P3d GSX apps as well or are they still broken? Will there be a new installer that allows full installation to both platforms? When will that be available?
Please answer this, do not refer me to other threads. This is not the way to run a business, but it seems to be the normal for FSTD.
-
The Universal Installer and Live Update will still download files again and again after using this Auto Manager.
From this sentence, it doesn't seem you understand what is happening and what this installer does.
The WHOLE issue with the Live Update downloading the files over and over, doesn't mean the Live Update is "bugged". In fact, it's exactly the opposite, it IS working correctly and it correctly detects some files are outdated so, it correctly download them. However, the local cloudflare node in your area, is NOT serving the latest version we have online, because it still hasn't replicated the files, because of too much traffic due to the release, they have been slower than normal.
So, on the next try, the Live Update correctly detects your file is STILL outdated, and it tries to download it again, and again it doesn't get the file it should have.
The Live Update is doing its job. In fact, it would have been a bug if it did *not* tried to redownload it again!.
So, what this installer does ? It doesn't download *anything*, it simply includes all the important files that make all of GSX code ( = programs without objects or textures ), which are the exact copy of what's online now, that you were supposed to get.
So you only need to install this, and don't worry about Live Udpate, that's what the fix was about, to allow users affected by a local Cloudflare node being too slow getting the files, to get the files IN ANOTHER WAY.
-
The Universal Installer and Live Update will still download files again and again after using this Auto Manager.
From this sentence, it doesn't seem you understand what is happening and what this installer does.
I totally am aware about what the Auto Manager did and what the problem with the files on the node are.
I only wanted to confirm that:
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
It did downgrade MY local files. So files on the node are still out of date which means YOU still have a problem and I as your customer don't care where the issue is located.
It's fine, I'm up to date for the moment because of the Auto Manager.
BTW A table of content for the manual would be a good idea, just saying ...
-
All of you have exactly the same problem, and it's caused by not getting the latest files from cloudflare. I'll probably need to reach out to cloudflare support tomorrow but, in the meantime, we can try a completely different solution.
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
If this works, we might post it as a Sticky until the issue is really solved on Cloudflare side. IF you run the FSDT Live Update, the it shouldn't download anything, but if it does, it might have "downgraded" something with an outdated version stored on Cloudflare. In that case, just run this again, since it's completely offline.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing (https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing)
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file (https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file)
Umberto,
can confirm that with the above workaround now I got both MSFS GSX pro working and have my P3DV5 GSX2 also still working!
At the stage when I downloaded the above Addon_Manager.exe file I had my P3DV5 GSX fully working and had MSFS GSX pro not installed and fully deactivated. Steps after the download of the Addon_Manager exe I took:
1. Activated GSXPro in the installer
2. Installed GSXPro via the installer and let the installer routine do all its tasks incl. downloading, installing.
3. Once GSXPro was installed and relinked, I pushed again the update button for GSX Pro in the installer
4. once that was done and before starting any of my Flightsim applications I executed the Addon_Manager.Exe workaround as admin
5. started P3D5 after that 1st, which was in the days before somehow always "disturbed" and behaving strange once I had installed GSX Pro. Thsi time-> all fine and GSX2 in P3DV5 working
6. finally started MSFS, and found GSX pro working fine.
7. having closed MSFS I restarted P3DV5 -> still all fine with GSX
So to conclude: finally with the work around and my proceedings above I have now both Sims running with GSX.
Now for me the only thing left is that I will NOT for the time being push and FSDT update button, being afarid that I would have to re-do things....
Umberto, is there the possibility that as soon as possible you inform us all once you have the confirmation from cloudflare that they are fully updated with the latest files, so that we can be safe to run updates?
Please advise, tks,
Andreas
-
It did downgrade MY local files. So files on the node are still out of date which means YOU still have a problem and I as your customer don't care where the issue is located.
It's fine, I'm up to date for the moment because of the Auto Manager.
I'm not sure what is your point here. I said a downgrade would possibly happen, and you only had to reinstall this offline installer, to get you back to the correct version. You said the installer did fix it in fact so, what else is there to say ?
I said "possibly downgrade", because there's no telling *exactly* when *your* local cloudflare node will get the correct files, so you won't have to use this temporary installer. But YOU can tell when the server is fine because...the Live Updater will STOP trying to download the same files over and over, because finally the files the Live Updater *expects* to get arrived.
UNTIL THEN, just run this temporary installer after the Live Update.
-
I've been watching this post for a solution and all I can get out of it is al lot of bickering back and forth.
I got GSX Pro to work by uninstalling everything and not installing anything on P3D.
I too, use both, but I can wait.
I am a long time customer of FSdreamream and have nothing but respect for Umberto.
Like I said, I'll wait for a final solution which I am confident it will come.
Papagiorgio
-
Here's two links ( they are the same, no need to download both, I just uploaded two copies, just in case ) of a very quick and dirty installer for the whole Addon Manager root as it should be. It's nothing fancy, but should work until we'll clarify why cloudflare doesn't seem to get our updates. It should detect the previous installed Addon Manager folder, and overwrite everything there with what you were supposed to get.
Running FSDT Updater still results in the following after installing from this .exe:
Start checking for MSFS updates
DOWNLOADING file D:\Addon Manager\model\rules_fueltruck.cfg
DOWNLOADING file D:\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\menu
DOWNLOADING file D:\Addon Manager\MSFS\fsdreamteam-gsx-pro\html_ui\InGamePanels\FSDT_GSX_Panel\tooltip
So, partially yes, only those three things are still constantly downloaded each time I run the Updater. As of today, it suddenly also always downloads the LSZH and Quiberon layout.json files, dont ask me why...
-
Ok, this might be an interesting find for Umberto: the reason why in my case Couatl is never starting with MSFS is the strange fact that none of the .exe files defined in the exe.xml file are executed when firing up MSFS. Neither Couatl, nor Fenix or Aerosofts VDGS. There is also a thread over in the official forums, no idea why the exe.xml seems to stop working, the sim also does not recreate the exe.xml file anymore when deleted (which I did due to some unknown idiotic thought of mine).
-
Followed the steps in #266. Scripting engine did not start. Had to start Couati64_MSFS manually. Finally to the GSX menu after airports refreshed.
-
the reason why in my case Couatl is never starting with MSFS is the strange fact that none of the .exe files defined in the exe.xml file are executed when firing up MSFS. Neither Couatl, nor Fenix or Aerosofts VDGS.
Surely I know about that, because I am affected too, my exe.xml starts randomly, like 1 times out of 5. I reported it to Asobo, they are aware of it, and are looking for a fix.
It seems to be a buggy "licensing" problem and, in my case, I SUSPECT it happens because I have two separate copies of MSFS installed, one is the Microsoft Store version running SU10 Beta, the other is the Steam version running SU9, they are completely separate installations with separate licenses. However, since even on Steam you are required to log into MSFS with a Microsoft account, and that's clearly the same, I think this confuses the licensing system, because each time I switch from using one version to the other one, it thinks I'm logging from "another device", so it asks for confirmation. This is likely triggering some kind of bug, because the failed XML startup is in fact triggering a Windows error code that is related to a licensing problem. If I enable the Simconnect diagnostic log, it tells me I don't even have the *license* to run the Diagnostic log!
Asobo replied to me about this, saying the issue is likely the MSFS is trying for some reason to validate the license of child process started from the EXE.XML, which it obviously can't (MSFS can't possibly know anything about 3rd party licenses) so, the failure result in the .EXE not being started.
-
Dear Virtuali,
Being my self a satisfied user of GSX (FSX), I immediately bought your GSX Pro for MSFS.
Unfortunately I found the same problems as many other users here in the forum with download servers, with GSX menu not showing, with GSX showing but not working and finally with GSX working with issues.
The GSX working only occur after I use one of your download links bellow.
Download from GDrive
https://drive.google.com/file/d/1NU20pW0twKl_KptypNFZre9nO5h0Q8F2/view?usp=sharing
Download from Mediafire
https://www.mediafire.com/file/rcjygudgvbccu2w/Addon_Manager.exe/file
I love your product and I would like to see all the GSX capabilites working without issues, I really thrust FSDT will provide that soon.
Please continue the good work
PedroSMP
-
The GSX working only occur after I use one of your download links bellow.
Well, that at least indicates GSX *does* work, because that installer just copies the same exact files we have online now, but couldn't reach you because your local cloudflare node was still outdated.
I love your product and I would like to see all the GSX capabilites working without issues, I really thrust FSDT will provide that soon.
If you mean GSX still have bugs that need to be fixed, then yes, we'll of course work at them. If you mean the server issue, it will sort out itself automatically in the next days, at least yours is yet another confirmation that files on our servers are find and work, the only issue was you couldn't reach them.
-
Hello,
I can confirm that after installing Umberto's latest link, GSX works now in P3D as well as in MSFS. I have installed P3D on top of MSFS - first GSX/GSX L2 and then a lot of FSDT airports - and run the link. GSX Pro was already installed before.
Thanks a lot for the hotfix FSDT. It isn't a big issue for me to run the link after Live Update. It's just great to know that there is now a possibility to run GSX on both sims together and I am sure that the problem will be solved anyway soon when all download/update servers are up-to-date.
Kind regards,
Daniel
-
Same here, I tried to do a full clean install then I tried by updating that new installed GSX Pro and nothing...
The couatl.exe is running, I can see the logo at the bottom and GSX on the top menu of my simulator. When I hit the GSX in the menu it gives me the "Couatl.exe script hasnt start" so I go also at the bottom and try to "Restart" the Couatl.exe and nothing still.
I ran out of knowledge to keep trying new solutions so I am posting here like many others from what I can see.
-
the reason why in my case Couatl is never starting with MSFS is the strange fact that none of the .exe files defined in the exe.xml file are executed when firing up MSFS. Neither Couatl, nor Fenix or Aerosofts VDGS.
Surely I know about that, because I am affected too, my exe.xml starts randomly, like 1 times out of 5. I reported it to Asobo, they are aware of it, and are looking for a fix.
It seems to be a buggy "licensing" problem and, in my case, I SUSPECT it happens because I have two separate copies of MSFS installed, one is the Microsoft Store version running SU10 Beta, the other is the Steam version running SU9, they are completely separate installations with separate licenses. However, since even on Steam you are required to log into MSFS with a Microsoft account, and that's clearly the same, I think this confuses the licensing system, because each time I switch from using one version to the other one, it thinks I'm logging from "another device", so it asks for confirmation. This is likely triggering some kind of bug, because the failed XML startup is in fact triggering a Windows error code that is related to a licensing problem. If I enable the Simconnect diagnostic log, it tells me I don't even have the *license* to run the Diagnostic log!
Asobo replied to me about this, saying the issue is likely the MSFS is trying for some reason to validate the license of child process started from the EXE.XML, which it obviously can't (MSFS can't possibly know anything about 3rd party licenses) so, the failure result in the .EXE not being started.
Well, I checked again and I still have the exe.xml and now it IS starting couatl, but no VDGS or Fenix. Am at a loss, no idea what is going on here... and I never had another instance of MSFS installed...
-
I ran out of knowledge to keep trying new solutions so I am posting here like many others from what I can see.
Are you sure you ran this installer LAST ?
http://www.fsdreamteam.com/forum/index.php/topic,26826.0.html
As explained there, if you run the Live Updater again after it, it's possible that, because your cloudflare node is still updated, so it will downgrade some files which were corrected by the offline installer, so you need to run it again.
If that still doesn't fix it, post your log as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,26759.0.html
-
I have been trying everything in the forums to get GSXPro fixed since release. The latest attempt is as follows:
1. Unistall GSXPro from the installer
2. Uninstall The installer using the Win apps uninstall
3. Deleting the addons directory. Just a note I sewe it has moved to Programs(x86) from P3dV5 Addon files)
4. I did not remove my P3D FADT airports
5 Reinstall GXXPro using fresh download of the intaller.
6. Rebooted the machine
7. Started msfs...Coatil scripting not starting error still remains.
8. Installed the "Patch addon manager" file
9. Did not run the updater
10. Ran MSFS Coatl error still there
Attached is the .err file. I noticed that there is a different error this time Any help would be appreciated
-
It did downgrade MY local files. So files on the node are still out of date which means YOU still have a problem and I as your customer don't care where the issue is located.
It's fine, I'm up to date for the moment because of the Auto Manager.
I'm not sure what is your point here. I said a downgrade would possibly happen, and you only had to reinstall this offline installer, to get you back to the correct version. You said the installer did fix it in fact so, what else is there to say ?
I said "possibly downgrade", because there's no telling *exactly* when *your* local cloudflare node will get the correct files, so you won't have to use this temporary installer. But YOU can tell when the server is fine because...the Live Updater will STOP trying to download the same files over and over, because finally the files the Live Updater *expects* to get arrived.
UNTIL THEN, just run this temporary installer after the Live Update.
What my point is ? I just stated facts.
And I never said it fixed it, not sure where you got that from, maybe you mixxed me up with someone else. I said:
Have you tried the installer discussed in this thread ?
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg175191.html#msg175191
No, had not seen it. It seems to have worked, albeit the Universal Installer and Live Updater still downloads the same files over and over again after I used the Addon Manager from that tread.
BTW How do I know or can check which are the latest file versions ?
But it's okay, no need to reply anymore. Some day it all will work out and I'm to tired of another post from you telling me it's all fine on your end, I'm doing something wrong or interpreting something wrong or cloudflares nodes aren't up to date yet (which is exactly what i reported).
Also I guess you have more important things to fix then to reply to my post.
-
8. Installed the "Patch addon manager" file
Your log shows you still have the outdated version (4801, the one OFFLINE installer is 4811), so something must have gone wrong here. Try to configure the antivirus to add the whole Addon Manager folder to its Exclusion, because there's no other explanation why you don't have the version that is there.
-
I finally got it working in both P3D and MSFS2020. I downloaded the file from Mediafire. I first uninstalled the P3D and the MSFS version of GSX. I installed the new file. Then I installed the P3D version and than the MSFS version and restarted my computer to my surprise GSX is working in both versions of GSX.
-
Has the issue being corrected? I tried everything posted here without any success by having both GSX Pro and GSX on the P3D V5 at the same time.
-
The procedure indicated in the previous post should work. But please, for any issues specific to P3D, use the relevant section of the forum.
-
The procedure indicated in the previous post should work. But please, for any issues specific to P3D, use the relevant section of the forum.
No, it still does not work, I did exactly what stated in the last post but still got the message COUATL scripting engine not starting, I attach my Log File.
-
19 th of this month, i paid for a working copy . i have tryed all way of getting it to work, im had my computer checked, it not my compuer. so you need get sum ball and sent a repair patch to all people who have the same problems
-
Hi, I was one of those who tried using the new link, uninstall and reinstall without success, and for a while only had the MSFS version working.... BUT... now both my GSX are working in P3dv5 and MSFS. Just wanna share here what I did differently. Hopefully it will be of help to anyone who is still stuck.
1 - Open "Addon Manager" folder in C:\Program Files (x86)\Addon Manager(or wherever you installed)
2 - Look for "Couatl_Updater" and "Couatl_Updater2" application icon.
3 - Right click on each files above, select Properties, go to Compatibility tab, Check "Run this program as an administrator"
4 - Now right clcik on "Addon Manager" folder, select Properties, under Security Tab, Click edit, check the "Full control" and "Modify" box.
5 - Right click FSDT Installer icon at Desktop, select "Run as administrator"
6 - Once the program loaded, press "Update All"
7 - Restart PC.
8 - Run MSFS, Load your flight, then right click "Start Couatl for GSX MSFS" icon (at Desktop) select "Run as administrator"
9 - Press the GSX button in the ingame menu, wait for the airport cache to complete. GSX menu will appear when all is completed.
For P3dv5 no further steps after step 7.
Hope this helps.
-
No Chance on any of the suggestions, not even the offline installer is working. Not setting everything to admin rights, a dozen clean reinstalls, nothing! An absolute mess, disgusting. Thx Umberto for this great tips! Better look for a solution of your cloudfare …your nodes, your broken files… but …of course,it’s all the users fault. Since years I had products of FSDT, up to now! Not worth a cent this GSX pro
-
! Better look for a solution of your cloudfare …your nodes, your broken files… but …of course,it’s all the users fault.
Cloudflare is not obviously mine, neither the nodes are, and I never, ever said it's "user's fault" where, exactly, have you read this in any of my replies ?
Our files are not "broken", don't you find a bit unusual you posted about "nothing is working" precisely after a post confirming it does ? Shouldn't that raise a bit of suspicions that, maybe, the file are not really "broken" ?
Of course, if instead you posted more precisely what is your problem, perhaps following the instruction how to create a log in the Sticky thread named "How to report and error", I might have a chance to see what's wrong with your system (this doesn't mean it's "your fault"!! ), something that it's quite difficult to understand with just a "not working" comment.
-
Paid close attention to attempted installs, and noticed a file was not being downloaded. It was the, Coualtl_64_MSFS.exe. So, I tried disabling anti virus, and followed instruction below, by uninstalling program, uninstalling the installer, and deleting the addon manager folder. Then reinstall. With antivirus disabled, everything downloaded, including the 64_MSFS.exe. file. Back in business.
-
@sumnersd: where is the .exe file located? Try to locate it, maybe its missing with me as well... everything else I did as you did, not working, the couatl is showing up in the system tray for a few seconds, than closing again.
-
Ok, I have it, even with admin rights... no chance on my system
-
Ok, I have it, even with admin rights... no chance on my system
Please post your log, as instructed here:
https://www.fsdreamteam.com/forum/index.php/topic,26759.msg175111.html#msg175111
-
I'm having the same problem. Tried almost everything posted here. There's my log error.
Thanks' for your help.
-
I'm having the same problem. Tried almost everything posted here. There's my log error.
That's not your LOG file, it's your ERR file which is the one that comes out if you don't have logging enabled, so it's not detailed enough for us to check all possible issues so, if you have enabled logging as instructed, you should also have a Couatl.LOG file that is more recent.
-
Sorry about that. My mistake. Yesterday after posting I got into this problem and I realized my antivirus was sending the file that appears in the image "bglmanx65.dll"to quarantine. Put it back and exclude the file from the real time scanning. 3 of 3 attempts ok, starting couatl outside msfs once running or running it before starting msfs. Don't know if this is my specific problem but so far its working for me.
-
I have uninstsalled and reinstalled it several times and followed all other suggestions but the scripting engine still inst running. I'm attaching my log for your review.
-
I have uninstsalled and reinstalled it several times and followed all other suggestions but the scripting engine still inst running. I'm attaching my log for your review.
You have the same problem discussed here:
https://www.fsdreamteam.com/forum/index.php/topic,26759.msg180410.html#msg180410
-
The post below is DEFINITELY more than worth a try. Especially the part of:
Right-click the ADDON MANAGER folder, select properties, and give FULL control permission to your user name.
Run "Couatl_Updater" and finish the process then run "Couatl_Updater2" and let it finish again.
Restart your sim or restart Couatl for GSX MSFS with Admin rights and test if working now.
Hi, I was one of those who tried using the new link, uninstall and reinstall without success, and for a while only had the MSFS version working.... BUT... now both my GSX are working in P3dv5 and MSFS. Just wanna share here what I did differently. Hopefully it will be of help to anyone who is still stuck.
1 - Open "Addon Manager" folder in C:\Program Files (x86)\Addon Manager(or wherever you installed)
2 - Look for "Couatl_Updater" and "Couatl_Updater2" application icon.
3 - Right click on each files above, select Properties, go to Compatibility tab, Check "Run this program as an administrator"
4 - Now right clcik on "Addon Manager" folder, select Properties, under Security Tab, Click edit, check the "Full control" and "Modify" box.
5 - Right click FSDT Installer icon at Desktop, select "Run as administrator"
6 - Once the program loaded, press "Update All"
7 - Restart PC.
8 - Run MSFS, Load your flight, then right click "Start Couatl for GSX MSFS" icon (at Desktop) select "Run as administrator"
9 - Press the GSX button in the ingame menu, wait for the airport cache to complete. GSX menu will appear when all is completed.
For P3dv5 no further steps after step 7.
Hope this helps.
-
Right-click the ADDON MANAGER folder, select properties, and give FULL control permission to your user name. Run "Couatl_Updater" and finish the process then run "Couatl_Updater2" and let it finish again.
That's exactly what the installer does: it gives explicit permission to ALL members or the "Users" group to the whole Addon Manager folder so, normally it shouldn't be required. But of course, if it works for some, it won't do any harm.
-
For me the COUATL scripting engine doesn't start when I start the sim. I have to manually start it each time
-
For me the COUATL scripting engine doesn't start when I start the sim. I have to manually start it each time
That's a known MSFS issue:
https://www.fsdreamteam.com/forum/index.php/topic,26924.0.html
It seems to have been a bit improved in the SU11 Beta, but it's not completely solved.