Author Topic: couatl scripting engine has encountered when calling the gsx service **SOLVED**  (Read 3479 times)

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: couatl scripting engine has encountered when calling the gsx service
« Reply #15 on: February 03, 2022, 09:43:18 pm »
Your log shows no error.

Please post an error log immediately after the error appears and don't reply YES to the question if you want to restart Couatl because, if you do that, the log containing the error will be overwritten.

In any case, the very fact you DO have a log, even with an error, shows the program is working normally, if it was an antivirus problem, it wouldn't even started. Instead, it's working, but couldn't find its objects, which is not normal, since our installer surely installs them and add their path to the add-on.xml.

Which is why, I posted several suggestions to check, about the add-on.xml not being updated, or being reverted to a previous version because you are using a 3rd party utility to manage the various add-on.xml files.

You might try REMOVING this folder:

Documents\Prepar3D v5 Add-ons\FsDreamTeam Addon Manager

Then reinstall GSX and don't run anything else. If you haven't got any errors while installing, the installer WILL surely create a correct add-on.xml containing all paths to find all the objects required.
« Last Edit: February 03, 2022, 09:48:00 pm by virtuali »

ska133

  • Newbie
  • *
  • Posts: 3
Re: couatl scripting engine has encountered when calling the gsx service
« Reply #16 on: February 04, 2022, 11:25:02 am »
Allright I'll do this and keep you posted

ska133

  • Newbie
  • *
  • Posts: 3
Re: couatl scripting engine has encountered when calling the gsx service
« Reply #17 on: February 04, 2022, 05:14:23 pm »

You might try REMOVING this folder:

Documents\Prepar3D v5 Add-ons\FsDreamTeam Addon Manager

Then reinstall GSX and don't run anything else. If you haven't got any errors while installing, the installer WILL surely create a correct add-on.xml containing all paths to find all the objects required.

It worked  ;D