FSDreamTeam forum

Products Support => GSX Support MSFS => Topic started by: follettj on June 26, 2025, 12:00:05 am

Title: Couatk scripting error message **SOLVED**
Post by: follettj on June 26, 2025, 12:00:05 am
Just got a new PC and installed MSFS 2020.

Everytime I load into the sim I am getting the following error in the log

couatl v5.0 (build 5974)
panic log started on Wed Jun 25 22:56:36 2025

problem raised by addon <unknown>
[00:02:16.094] Traceback (most recent call last):
[00:02:16.094]   File ".\GSX\__init__.py", line 1800, in flightLoaded
[00:02:16.094] NameError: name 'self' is not defined
{'User Pos': (0.00040731374047469184, 0.01397450300629543, 4.38039 m, 4.38039 m, 0.00011184760628954488, -0.0035274196155395477, -0.0, -7.191334974139871e-06, 4.572, 1.0)}

I have tried to reinstall GSX pro fully and run the live update to no avail any help appreciated
Title: Re: Couatk scripting error message **SOLVED**
Post by: sgeneslaw on June 26, 2025, 12:20:24 am
Same with me, just after the new update
Title: Re: Couatk scripting error message **SOLVED**
Post by: Seth2413 on June 26, 2025, 01:35:26 am
Same here, thought it was just me.   Issue is the error comes up on loading and you cant shut it off as couatl script engine continues to want to start.  GSX Pro is unusable for me at the moment and have to turn it off all togther.  Have done 'live update' which didnt heklp. 

Here is bottom of couatl.log file

[00:02:47.985] Using EFX 1.0 extension, with 4 auxiliary send(s)
[00:02:47.985] Using EAX reverb
[00:02:47.985] resetVars() with Simconnect
[00:02:47.985] GSX is starting
[00:02:47.985] [GSX] Simulator version is 11.0.282174.999
[00:02:47.985] isPBRAvailable returned  False
[00:02:47.985] isRTTAvailable returned  False
[00:02:47.985] GetSimObjectsFolder() returned  C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-pro/SimObjects
[00:02:47.985] GetAdditionalSimObjectsFolder() returned  C:\Program Files (x86)\Addon Manager/MSFS/fsdreamteam-gsx-world-of-jetways/SimObjects
[00:02:47.985] GetAdditionalSimObjectsFolderV5() returned 
[00:02:47.985] gateDistanceThreshold = 25 m
[00:02:48.000] [KIAH2] started
[00:02:48.375] Preloading pyglet image library...
[00:02:48.907] GSX started
[00:02:49.079] Start searching for add-on Packages
[00:02:49.094] Packages that contain manifest.json with gsx-pro in dependencies:
[00:02:49.094] Creating model cache...
[00:02:50.000] Model cache loaded
[00:02:50.000] Preload operators thumbnails...
[00:02:50.719] Preload operators thumbnails DONE
[00:02:51.657] GSX SimStart
[00:03:00.532] GSX SimStop
[00:03:02.000] GSX SimStart
[00:03:02.938] GSX SimStop
[00:03:03.094] Traceback (most recent call last):
[00:03:03.094]   File ".\GSX\__init__.py", line 1800, in flightLoaded
[00:03:03.094] NameError: name 'self' is not defined
{'User Pos': (0.0004074026672999015, 0.013974465469621914, 2.35303 m, 2.35303 m, 0.0010729553819766712, 0.018738475819736464, 0.04014257341623306, -0.00020782870180650916, 1.6459200290679932, 1.0)}
Title: Re: Couatk scripting error message **SOLVED**
Post by: Alex871 on June 26, 2025, 01:49:29 am
Switching to beta release solves it in the mean time.
Title: Re: Couatk scripting error message **SOLVED**
Post by: gilcon on June 26, 2025, 02:05:32 am
Same thing and same message as follettj.  Reinstall and Live Update doesn't fix it.  Started today.
Title: Re: Couatk scripting error message **SOLVED**
Post by: Ferradini on June 26, 2025, 02:17:45 am
Switching to beta release solves it in the mean time.
Thanks, this actually works. Did a full MSFS re-installed this morning and Couatl stopped working. After switching to beta, works now like a charm.
Thanks
Title: Re: Couatk scripting error message **SOLVED**
Post by: gilcon on June 26, 2025, 02:35:17 am
Switching to beta release solves it in the mean time.
Where do I find the Beta?
Title: Re: Couatk scripting error message **SOLVED**
Post by: Ferradini on June 26, 2025, 02:46:50 am
Switching to beta release solves it in the mean time.
Where do I find the Beta?
On the FSDT installer left side in a small box. Change it to BETA and click update.
Title: Re: Couatk scripting error message **SOLVED**
Post by: gilcon on June 26, 2025, 04:03:10 am
Right in front of me!  Thanks.
Title: Re: Couatk scripting error message **SOLVED**
Post by: Arnason on June 26, 2025, 08:24:39 am
What could be causing this?
Title: Re: Couatk scripting error message **SOLVED**
Post by: Ahmed_rady on June 26, 2025, 09:09:37 am
Same thing and same message
Title: Re: Couatk scripting error message **SOLVED**
Post by: Seth2413 on June 26, 2025, 10:27:30 am
Changed it to beta which it now works but all the ground crew are pink.  Why do I bother. 
Title: Re: Couatk scripting error message **SOLVED**
Post by: Seth2413 on June 26, 2025, 10:31:53 am
What could be causing this?

This is lots of people apparently - just started today, you'll see another thread on it.  Short term fix is to switch to beta if you want to risk it even more bugs!!!  Fancy GSX pro having a beta and a 'stable' version.  ha!
Title: Re: Couatk scripting error message **SOLVED**
Post by: virtuali on June 26, 2025, 10:50:12 am
Fixed by running an update CHECK now.
Title: Re: Couatk scripting error message **SOLVED**
Post by: radzio2 on June 26, 2025, 12:23:49 pm
Fixed by running an update CHECK now.
For me running an update didn't solve the problem. Switching now to beta version.
Title: Re: Couatk scripting error message **SOLVED**
Post by: jltellez on June 26, 2025, 12:25:21 pm
Hello, ever since I bought the GSX Pro a while ago, it's been working perfectly. 10 out of 10, but today I'm getting this error and I don't know how to fix it. If anyone could give me any ideas, I'd appreciate it. Thank you very much. The error is:

couatl v5.0 (build 5974)
panic log started on Thu Jun 26 12:13:47 2025

problem raised by addon <unknown>
[00:00:58.422] Traceback (most recent call last):
[00:00:58.422] File ".\GSX\__init__.py", line 1800, in flightLoaded
[00:00:58.422] NameError: name 'self' is not defined
{'User Pos': (0.00040735172687712226, 0.01397450300629543, 2.50096 m, 2.50096 m, 359.9999837783006, 0.017684280542879207, 0.024434609338641167, -0.00011015882039688728, 2.553919111633301, 1.0)}
Title: Re: Couatk scripting error message **SOLVED**
Post by: jadolfo on June 26, 2025, 12:26:47 pm
+1
Title: Re: Couatk scripting error message **SOLVED**
Post by: virtuali on June 26, 2025, 12:34:41 pm
For me running an update didn't solve the problem. Switching now to beta version.

The Beta channel doesn't exist anymore, so even if you switch to it, you'll get exactly the same file as the release version. If your local cloudflare node hasn't got the fixed file yet, the solution is use the OFFLINE installer instead.
Title: Re: Couatk scripting error message **SOLVED**
Post by: virtuali on June 26, 2025, 12:42:34 pm
Please don't open new threads when another one discussing exactly the same issue is already opened and answered.

- The problem has been fixed and the fix can be obtained by clicking the CHECK button in the FSDT Installer

- If you have still the same error, indicating your local cloudflare node still haven't received the fix, use the OFFLINE Installer, linked in the Sticky thread of this section of the forum.
Title: Re: Couatk scripting error message **SOLVED**
Post by: jadolfo on June 26, 2025, 01:24:24 pm
Hello,

After update GSX, I recive this error and is not posiblle to run Couatl. The error is recurrent.

couatl v5.0 (build 5974)
panic log started on Thu Jun 26 13:21:37 2025

problem raised by addon <unknown>
[00:00:02.500] Traceback (most recent call last):
[00:00:02.500]   File ".\GSX\__init__.py", line 1800, in flightLoaded
[00:00:02.500] NameError: name 'self' is not defined
{}

Anybody help me?
Title: Re: Couatk scripting error message **SOLVED**
Post by: virtuali on June 26, 2025, 03:21:27 pm
Please don't open new threads when another one discussing exactly the same issue is already opened and answered.

- The problem has been fixed and the fix can be obtained by clicking the CHECK button in the FSDT Installer

- If you have still the same error, indicating your local cloudflare node still haven't received the fix, use the OFFLINE Installer, linked in the Sticky thread of this section of the forum.