FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: melssim2 on March 28, 2023, 08:18:52 pm
-
Hi,
Every time, I get the error that <unknown> is causing the Couatl Scripting Engine to restart. I re-installed GSX level 2 but nothing works.
I attached the latest log-file. What could cause this and how to solve it?
Ps: I did these steps already: https://www.fsdreamteam.com/forum/index.php/topic,15483.msg111712.html#msg111712
-
I've been getting a similar issue after last update. my error is below. Different airports, different aircraft. I'm on P3d 5.2
couatl v4.8 (build 5086)
panic log started on Mon Apr 3 21:38:13 2023
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\__init__.py", line 1271, in onSimStart
File ".\GSX\__init__.py", line 1213, in checkOnGroundState
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\common\sceneryAddOnMulti.py", line 1247, in CheckIcingConditions
TypeError: CheckIcingConditionsSimple() takes exactly 2 arguments (1 given)
{'Airport': 'YBBN', 'User Pos': (-27.40283533924958, 153.1181962508708, 6.51318 m, 2.55118 m, 27.497919424839463, 0.011344640515744686, 0.011344640515744686, 0.00021574892599270318, 2.5511759651184085, 1.0)}
GSX SimStop
-
Every time, I get the error that <unknown> is causing the Couatl Scripting Engine to restart. I re-installed GSX level 2 but nothing works.
The problem seems to be caused by your airport profile. Whoever made it, as called for a Jetway that doesn't normally exists in GSX, but it's only include in another FSDT airports, maybe he had those, and shared a profile assuming everybody has it, but instead it came in an FSDT airport you don't have.
Removing the custom profile will fix this.
-
I've been getting a similar issue after last update. my error is below.
Your problem is completely different, and it's caused by GSX having received an invalid Metar string ( are you using a 3rd party weather app ? ), so it switched to a simpler method to check icing, based only on the outside temperature instead of the Metar ( which would allow to check for Dew point too ), which is the normal method.
This backup procedure has in fact a bug, related to having it changed to work with MSFS ( that has a new variable for the runway surface condition ), so the P3D version of the backup procedure is causing this error, which will be fixed in the next update, of course.
-
Umberto thanks for that. I will wait for the new update. btw I use ActiveSky for weather.
Cheers.
-
ps looks like working for me after update, thank you.