Author Topic: GSX Couatl Scripting engine error **SOLVED**  (Read 11225 times)

billkhaled

  • Newbie
  • *
  • Posts: 19
GSX Couatl Scripting engine error **SOLVED**
« on: October 22, 2017, 05:07:00 pm »
Hi,

I purchuased GSX from you guys earlier today and I have ran into an issue after installation. I am getting and error by the Couatl scripting engine about it crashing

At first GSX will be regenerating airport cache and will be able to get me to a suitable parking and tell me to shut engines and set parking brake, after doing so I will immediately get a Couatl Scripting Engine Error. This last time I was able to get as far as selecting my handling operator when the issue occured. I have read other threads about this and have reinstalled GSX, ran the live update and also installed the latest version of the Addon Manager. Any idea why i have this issue, thanks very much. This issue has occurred at every airport I have tried.  ;D

Here is the error log:

couatl v3.2 (build 3852)
panic log started on Sun Oct 22 16:13:14 2017

problem raised by engine or unspecified addon
{'Airport': 'KVPS', 'Requested assistance services at': 'Parking 15', 'User Pos': (30.48896389828307, -86.50150056845435, 27.754 m, 1.237 m, 2.767441325048919)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_BaggageTractor_AA'
{'Airport': 'KVPS', 'Requested assistance services at': 'Parking 15', 'User Pos': (30.48896389828307, -86.50150056845435, 27.754 m, 1.237 m, 2.767441325048919)}



Kind Regards.
« Last Edit: October 27, 2017, 10:37:57 am by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #1 on: October 23, 2017, 12:31:00 am »
This error is NOT a "Couatl crash".

It's proper error message, handled gracefully, which is indicating that something went wrong (because of a problem of your sim configuration, not related to GSX in this case), so nothing has crashed, and your sim is still running perfectly safe.

The reason why GSX cannot find an object which is surely is installed with it (so the file is there), it's because your sim cannot find the Simobject folder our installer added to the sim configuration when you ran it.

You haven't said which sim you use so, depending on the sim used, the way to configure the Simobjects folder changes a lot and the files to check are different and, if you use FSX, it's even different depending if you have FSX, FSX:SE, or both.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #2 on: October 23, 2017, 10:28:37 am »
I use Prepar3d v3.4

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #3 on: October 23, 2017, 02:36:39 pm »
I use Prepar3d v3.4

Under P3D 3.4, we use the add-on.xml method to add our Simobjects folders to the sim. But, it's possible that 3.4 might have the same bug that 4.0 had on release (which was fixed by the first Hotfix), that if your DLL/EXE.XML files are corrupted (that we don't use in 3.4), the add-on.xml might not be read as well.

It's likely 3.4 had the same bug that was fixed in the 4.0 first Hotfix so, check if both your DLL/EXE files are syntactically correct. The easiest way to do this, is to open them with Internet Explorer.

P3D 3 has the XML files at these locations:


%APPDATA%\Lockheed Martin\Prepar3d v3\EXE.XML
%APPDATA%\Lockheed Martin\Prepar3d v3\DLL.XML

%PROGRAMDATA%\Lockheed Martin\Prepar3d v3\EXE.XML
%PROGRAMDATA%\Lockheed Martin\Prepar3d v3\DLL.XML

You should check all four of them.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #4 on: October 23, 2017, 02:57:04 pm »
So what exactly am I looking for here in these files, can you provide an example if you don't mind thanks.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #5 on: October 23, 2017, 02:57:36 pm »
So what exactly am I looking for here in these files, can you provide an example if you don't mind thanks.

You should only verify that none of them has an error. The easiest way to do this, is to open them with Internet Explorer.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #6 on: October 24, 2017, 11:04:54 pm »
So what exactly am I looking for here in these files, can you provide an example if you don't mind thanks.

You should only verify that none of them has an error. The easiest way to do this, is to open them with Internet Explorer.

I'm sorry for asking so many questions but by verifying that none of them has an error am I looking for the word error? and if that is what I was supposed to be looking for there is no 'error written in text' in all 4 files

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #7 on: October 25, 2017, 10:17:38 am »
I'm sorry for asking so many questions but by verifying that none of them has an error am I looking for the word error? and if that is what I was supposed to be looking for there is no 'error written in text' in all 4 files

You will never find the word "error" written in any of them. As I've said, the easiest way to check for an error in an XML file, is to OPEN it with Internet Explorer. And yes, it MUST be Internet Explorer, not just any other browser (not even MS Edge), because IE has a feature that, when opening an XML file, it will check it for being syntactically correct so, it will be IE that, if the file has a problem, will issue an error message.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #8 on: October 25, 2017, 10:54:45 am »
I'm sorry for asking so many questions but by verifying that none of them has an error am I looking for the word error? and if that is what I was supposed to be looking for there is no 'error written in text' in all 4 files

You will never find the word "error" written in any of them. As I've said, the easiest way to check for an error in an XML file, is to OPEN it with Internet Explorer. And yes, it MUST be Internet Explorer, not just any other browser (not even MS Edge), because IE has a feature that, when opening an XML file, it will check it for being syntactically correct so, it will be IE that, if the file has a problem, will issue an error message.

Right Ok, thanks very much, I was able to open all 4 files without any error message

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #9 on: October 25, 2017, 12:09:56 pm »
Right Ok, thanks very much, I was able to open all 4 files without any error message

Is the Addon Manager listed in the Options->Add-ons menu in the sim ? Note, this is NOT the "Addons" menu, it's the  Options->Add-ons menu.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #10 on: October 25, 2017, 12:35:09 pm »
Right Ok, thanks very much, I was able to open all 4 files without any error message

Is the Addon Manager listed in the Options->Add-ons menu in the sim ? Note, this is NOT the "Addons" menu, it's the  Options->Add-ons menu.

In the menu along the top of my screen I see an Add ons scetion where I see things like GSX and Addon Manager and RAAS Professional but in the options section I only see options to pause, slew, change sim rate etc. I do not see an addons menu and therefore can not check if Addon manager is listed.

It is found in the Add Ons tab. However below the Options tab there is no Add Ons Menu
« Last Edit: October 25, 2017, 12:46:18 pm by billkhaled »

crauds

  • Sr. Member
  • ****
  • Posts: 259
Re: GSX Couatl Scripting engine error
« Reply #11 on: October 26, 2017, 02:55:52 am »
I had exactly the same error in FXS SP2 and after it came up I was no longer able to select any PMDG aircraft and when I attempted to invoke an option from GSX in a default aircraft, the sim instantly crashed and all scenery disappeared.  I have been using GSX on my new computer install for the past week without issue  but today I changed the aircraft configuration in the settings menu while I was in the air with the PMDG B744.  Within a few seconds FSX crashed.  All attempts to reload my last saved position crashed every time I tried to load it.

I reinstalled the latest "addon manager" freshly downloaded from the website and Viola! everything returned to normal and so far I have had no more Couatl error messages or crashes.  I intend to do more testing tomorrow.  Hopefully the issue has been resolved in my case. 
Craig Williams
I7 7700K OC to 4.8Ghz 16GB DDR4 2666Mhz SD RAM GTX1060 6GB LIQ Cooled Win10 Home 64

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #12 on: October 26, 2017, 11:06:53 am »
I had exactly the same error in FXS SP2 and after it came up I was no longer able to select any PMDG aircraft and when I attempted to invoke an option from GSX in a default aircraft, the sim instantly crashed and all scenery disappeared.  I have been using GSX on my new computer install for the past week without issue  but today I changed the aircraft configuration in the settings menu while I was in the air with the PMDG B744.  Within a few seconds FSX crashed.  All attempts to reload my last saved position crashed every time I tried to load it.

I reinstalled the latest "addon manager" freshly downloaded from the website and Viola! everything returned to normal and so far I have had no more Couatl error messages or crashes.  I intend to do more testing tomorrow.  Hopefully the issue has been resolved in my case. 

I tried the same thing but completely removed all Addon manager files and FSDT files and reinstalled but when I loaded up the sim I recieved the same error. As Umberto has said the problem is wihin the sim I think.

billkhaled

  • Newbie
  • *
  • Posts: 19
Re: GSX Couatl Scripting engine error
« Reply #13 on: October 26, 2017, 04:28:48 pm »
Right Ok, thanks very much, I was able to open all 4 files without any error message

Is the Addon Manager listed in the Options->Add-ons menu in the sim ? Note, this is NOT the "Addons" menu, it's the  Options->Add-ons menu.

New error log:
couatl v3.2 (build 3852)
panic log started on Thu Oct 26 15:25:46 2017

problem raised by engine or unspecified addon
{'User Pos': (30.499336607832557, -86.51128737596294, 28.9229 m, 2.40588 m, 192.17779584991519)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336607832557, -86.51128737596294, 28.9229 m, 2.40588 m, 192.17779584991519)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336607832557, -86.51128737596294, 28.9229 m, 2.40588 m, 192.17779584991519)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336607832557, -86.51128737596294, 28.9229 m, 2.40588 m, 192.17779584991519)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336540549844, -86.51128739278583, 28.9229 m, 2.40589 m, 192.1777975003865)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336540549844, -86.51128739278583, 28.9229 m, 2.40589 m, 192.1777975003865)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336540549844, -86.51128739278583, 28.9229 m, 2.40589 m, 192.1777975003865)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'
{2:, }
{'User Pos': (30.499336540549844, -86.51128739278583, 28.9229 m, 2.40589 m, 192.1777975003865)}
« Last Edit: October 26, 2017, 05:32:39 pm by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51229
    • VIRTUALI Sagl
Re: GSX Couatl Scripting engine error
« Reply #14 on: October 26, 2017, 05:33:49 pm »
17779584991519)}
Error: exception UNRECOGNIZED_ID in call Text param #3 '258'

Be sure you use the latest P3D V3 Hotfix, because from your log, it seems you are affected by the very well known P3D bug of fake exceptions caused by other clients leaking into the wrong client, given the user the wrong impression an addon is faulty, when in fact it's another one.