FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Cativo on February 21, 2012, 04:39:53 am
-
I haven't bought GSX yet, but I've tried using it in KORD but I'm getting an error message: "The addon <unknown> is causing the Couatl Scripting Engine to restart..."
this is what's in the Couatl.err:
couatl v2.0 (build 2179)
panic log started on Mon Sep 19 18:50:53 2011
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "wx\__init__.py", line 45, in <module>
File "wx\_core.py", line 5, in <module>
File "C:\Python26\Lib\new.py", line 6, in <module>
from warnings import warnpy3k
File "C:\Python26\Lib\warnings.py", line 394, in <module>
bytes_warning = sys.flags.bytes_warning
AttributeError: 'module' object has no attribute 'flags'
Application aborted because of a Python error
I should mention that I'm using FSPassengersX, would that cause any type of conflict?
-
Hello;
I'm using FS Passenger,and I haven't had any problem with it.
mark
-
That log you posted is from last September, so it's not relevant here.
"The addon <unknown> is causing the Couatl Scripting Engine to restart..."
It does't say just that. It also says to download and install the latest Stand-Alone Addon Manager. Try to do that first.
-
That log you posted is from last September, so it's not relevant here.
"The addon <unknown> is causing the Couatl Scripting Engine to restart..."
It does't say just that. It also says to download and install the latest Stand-Alone Addon Manager. Try to do that first.
Done that twice already, will try again tonight.
-
I still get the same error with the latest version.
-
I still get the same error with the latest version.
If you are getting that error, it must be recorded in the log. But the log shows the last time you got the error was in September, you should have a newer log, and maybe the error is different.
-
I still get the same error with the latest version.
If you are getting that error, it must be recorded in the log. But the log shows the last time you got the error was in September, you should have a newer log, and maybe the error is different.
I didn't even noticed, I just checked and that is the last entry. The error is the same. If I erase the log, will a new one be made if there's an error?
-
I didn't even noticed, I just checked and that is the last entry. The error is the same. If I erase the log, will a new one be made if there's an error?[/quote]
If there's an error, it should have been appended to the existing log without the need to create a new one, but you might try removing it, maybe is not possible to write to that file for some reason.
-
I deleted the original couatl.err file, got the same error but no new couatl.err was created. I run FSX with admin rights btw.
-
Sorry, but that's just not possible, the only possible explanation is that you are still running an old version of the Couatl program, that didn't generate a log automatically.
Since the installers automatically gets the current version online, the only possible explanation, is that an antivirus has blocked the download of the current version, so you are stuck with the old one, which explains both why you don't see a log, and the error itself.
-
Thank you, it was the anti-virus!
-
I'm having the same problem after installing KLAX, latest version. I don't have any antivirus right running, and this is the error I keep getting:
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:45:46 2012
Traceback (most recent call last):
File "couatl\GSX\__init__.py", line 425, in onSimStart
File "couatl\common\aircraftData.py", line 778, in getAircraftData
File "couatl\common\aircraftData.py", line 438, in __init__
File "couatl\common\aircraftData.py", line 331, in _exitsFromSimConnect
File "couatl\common\aircraftData.py", line 261, in _exitsFromFsxData
ValueError: need more than 2 values to unpack
Any thoughts?
EDIT-Never mind, I just read that you found the problem, and will be releasing an update later. Thanks.
Chris
-
Problem has been fixed with the current Live Update.