Products Support > GSX Support FSX/P3D
GSX Couatl scripting engine hasn't started **SOLVED**
virtuali:
--- Quote from: Sandbag01 on February 17, 2022, 11:19:35 am ---I got the same problem here! I have tried several times to uninstall and install GSX withOUT antivirus.
--- End quote ---
The reason why this thread is marked **SOLVED** is because many users confirmed this problem has been fixed by running the new FSDT Universal Installer.
You haven't said anything if you tried it or not.
antoros:
Hello, I still need support please.
1.) Installed Windows 11 Home fresh with all Updates
2.) Installed P3dV4 latest version
3.) tryed to install GSX with https://www.fsdreamteam.com/update/gsx_p3d4_setup.exe this link is posted on your main site
4.) I get the same error (Couatl scripting engine hastn started)
5.) I excluded the directory mentioned from Windows Defender -> no success
6.) When I try to launch Universal installer it says, GSX is not supported yet... please use the standard installer (/update/gsx_p3d4_setup.exe...)
Please help!
Regards
Stefan
virtuali:
--- Quote from: antoros on February 19, 2022, 11:09:12 pm ---6.) When I try to launch Universal installer it says, GSX is not supported yet... please use the standard installer (/update/gsx_p3d4_setup.exe...)
--- End quote ---
As already explained in this thread, you should just install the Universal installer and use it to UPDATE GSX, not to install it. It's supposed you already installed and failed to get the update.
mcdonnell123:
hello. i am getting this problem on p3dv4 even though i turn off anti virus (mine is mcafee LiveSafe) during download and installation.
also i manage to turn on couatl scripting engine by just clicking on the icon in file explorer. but everytime i put in my serial number for gsx and gsx level 2 and press the ok button in the addon manager, it does not make gsx appear. how can i solve this? anyone got any suggestions?
virtuali:
You don't say if you installed the new Universal installed and did the update from there, which is the thing that has been suggested, over and over, and multiple users who had this problem, confirmed it was fixed this way.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version