FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Hodge001 on April 18, 2012, 10:41:39 pm
-
Hi
I have just had my first ever error with GSX after accepting the latest live update, the error was a pop-up window with the following information in it..
The addon <unknown> is causing the Coutal Scripting Engine to restart. Details can be found……. Then the location of the error file and an instruction to download the latest addon manager, which I did and now FSX crashes on start up after several of these pop-up warnings have appeared along with a similar amount of Microsoft Visual C++ warning / error windows, which unfortunately have no text in them at all not even on what I assume is the close button.
The GSX error file contains the following information…
Coutal
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:06: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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:07:02 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:07:13 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:07:24 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:20:16 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:20:32 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:20:41 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:20:47 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:20:55 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:21:02 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:21:15 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:21:23 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
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 21:21:45 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
At this point FSX will crash with a fatal error.
The aircraft is the Carenado C185F on runway 28 at FSDreamteams KORD, I have been flying this and several other aircraft most of today without any problems at all until I accepted today's GSX update roughly forty five minutes ago.
As I say this is the first ever error I have experienced with GSX, and I hope that I have provided enough information to enable you to diagnose the possible problem.
Thank you in advance for any and all assistance.
Jim Hodkinson
-
Are you using a custom GSX.CFG file for that airplane ? Does it happen with every airplane or just that one ? It would be useful if you posted the [Exits] section of the aircraft.cfg file for that airplane.
-
Today I also Got the latest Coualt Engine Update and also I start getting the error described above.
Here is the log for the Virtuali Addon manager
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 13:34:35 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
The error occurs with any aircraft I use. Hope this can be fixed or atleast reversed to the previous state.
Also forgot to mention that I don't need to be on the airport to get the error. I do get it also with the default Flight on the Ultralight in mid air
-
Hi
Thank you for the prompt reply, as for the aircraft I have no custom config files for any of my installed aircraft except for the CS737 config file posted in the sub section of this forum.
The aircraft.cfg file entry for the exits of the C185F are as follows..
[exits]
number_of_exits=3
exit_rate.0=1
exit_rate.1=1
exit_rate.2=1
As for the error occurring with any other aircraft I can not say as FSX crashes at start up without getting to the free flight screen, but it has been OK with several other aircraft since I last installed FSX about six months ago.
Once again thanks for the prompt response to my request, I hope some of the above helps.
Jim Hodkinson
-
Ok, now that you posted the [exits] section the problem is clear: the airplane is using a non-standard command for the exits: exit_rate.X instead of exit.X with rate as the first parameter, I believe the exit_rate command is a leftover from FS9, but it's not mentioned in the FSX SDK anymore.
The problem happens at start, because that airplane is loaded in your startup flight, but I'm quite sure it doesn't happen with another airplane.
We should probably add some safety checks against those non-compliant airplanes but, as a temporary solution, you can probably fix it by changing the section as follows:
[exits]
number_of_exits=3
exit.0=1
exit.1=1
exit.2=1
Don't know if it will work (the exits will still be missing coordinates, so GSX services won't work without customizing the GSX.CFG ) but it might at least stop the crash at start.
-
Hi again
Unfortunately that aircraft is not my start up aircraft, that is the default C172 parked at exactly the same location, and the start up flight was made using Flight1's safe start up for the Mustang.
Jim Hodkinson
-
In my case I'm able to load FSX, select any aircraft and Load the simulation the problem ocurs seconds after. There is another detail that perhaps could be of any help, I have an aircraft called BOB from the makers of FTX this aircraft emulates a person but this aircraft doesn't have textures, I mean by that that nothing can be seen from it. This last aircraft I mention is the only one I can use that won't give me the script error.
-
Unfortunately that aircraft is not my start up aircraft, that is the default C172 parked at exactly the same location, and the start up flight was made using Flight1's safe start up for the Mustang.
That the problem is caused by the non-complaint Exits of that airplane is sure. I don't know what the "safe startup" does but, it's possible the final effect would be the same as having the C185F as a startup. FSX is not so straightforward when startup sequence are involved, an airplane is loaded/unloaded then reloaded again so that startup utility might cause a similar problem as if the C185F was the startup airplane, but the end result is the same: the problem IS the C185F having exits in the FS9 format.
-
Here is the same thing, guys. Seconds after load the aircraft, the message appears. It happens with any airplane at any airport. I can start at the end of the runway or on the patio, whatever, messages are appearing. I'm not using the exits editor in any aircraft. Have I downloaded the addon manager, installed it, restarted the system, and the messages continue.
In the error log, which appears repeatedly, always the same, is as follows:
couatl v2.0 (build 2307)
panic log started on Wed Apr 18 19:43:58 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
If anyone can tell me where I am wrong, I appreciate it.
Best regards
Cristiano Mueller
-
I have the same behaviour, starting from tonight, and with a lot of planes (Aerosfot Katana, Realair 260, and others).
What's happened?
Is it possible uninstall the last update or rollback it in some way?
Thanks for any help.
-
The problem surely doesn't happen with "any airplane", but only those that have non-compliant or entirely missing Exits. Like the default Ultralight, or the C185F in the previous example.
Before saying you are having the problem with "any airplane", try first an airplane that is usually associated with ground services.
-
Made some other test.
OK with default 737, NGX 737, default planes.
KO with Carenado Arrow, Carenado C172, Aerosoft twin Otter, and may others.
Help!!
-
So, more precisely, the problem happens with a plane that is BOTH unrecognized by GSX AND with non-standard or missing Exits in its aircraft.cfg
We can surely fix the message from *appearing* but, those airplanes will never work in GSX without a configuration file in any case, because there's no data source (no internal database, no gsx.cfg or intelliscene.cfg and no Exits in the aircraft.cfg) for their Exits.
-
Good for me.
No problem if they will not work, I understand there is a subset of planes working with GSX and others not (also I guess nobody would require baggage service or pushback for a Katana :-)
Only need is to be able to use them anyway without requiring ground services, as was up to few hours ago.
At the moment couatl crash continuously with them.
So if the problem is identified I'll wait some time for some patch or rollback.
Thanks for assistance, see you tomorrow.
-
Thanks Virtuali for your input indeed the issue applies to aircraft that ether don't have any [exits] or have the FS9 sintax I went ahead and changed all the "exit_rate.0" and replace it with "exit.0" and added the entry to the aircraft.cfg's that did not had it. it all works good now. I must admit it was a little scared will all that happened.
-
Mr. Umberto.
Please forgive me for using the phrase "this happens with any aircraft." My default aircraft is the Trike, and after the error appears, I was testing on other aircraft, and other, and other, coincidentally that signaled the error. Namely:
Trike
Extra 300S
Douglas DC3
DG808S
Piper Cub
Grumman Goose
Carenado C172N
Carenado T210
Eaglesoft Citation X 2.0
I tested these aircraft, because they were the fastest to load. As presented error, I made the flippant comment that "all aircraft have error".
But I admit I was wrong. The following aircraft have NO error:
Embraer Feelthere 175
Embraer Feelthere 195
Embraer Feelthere ERJ 135
Embraer Feelthere ERJ 145
Carenado C337
PMDG 737 NGX (600 700 800 900)
PMDG 747-8
PMDG MD11
Default aircrafts: NO error too.
CRJ 700
Cessna 172
King Air
Learjet 45
Bell Helicopter
Cessna 208B
Baron 58
Robinson R22
Maule
Mooney Bravo
de Havilland Beaver
Airbus A321
Boeing 737-800
Boeing 747-400
Again I apologize for the superficial comment , and I will be waiting instructions for how to use the aircrafts that present the message.
By the way, GSX is, no doubt, one of the best addons for FSX. Thanks for your assistance.
-
Yes, we already found where the problem is, will be surely fixed before tomorrow (it's 1:49 AM now, and it's not a very good idea to work on a fix now).
If you want to fly with these airplanes without being bothered by the message, you can add an [Exits] section like this:
[exits]
number_of_exits=1
exit.0=0,0,0,0,0
OR, edit the exiting one, to have the format expressed as exit.N and then 5 parameters, what it's usually missing are the coordinates and the door's type, they might be all 0, it's not a problem, since that airplane wouldn't have worked anyway, but will at least prevent the error message.
-
Thank you Mr. Umberto;
I will wait until tomorrow, don't worry. Here in Brazil is almost 10:00 PM, and I came tired of work, just wanted to clear my mind a bit in FSX. If there is a fix, I wait.
Good night, and thank you.
Best regards
Cristiano Mueller
-
> (it's 1:49 AM now, and it's not a very good idea to work on a fix now).
Agree !! :-) :-)
Thanks a lot for such immediate support at theese hours!!
Going to sleep me too.
-
Ok so this is what you have to do.
1) Determine which aircraft gives you the error.
2) Open the "aircraft.cfg"
3) Find the [exits] tag
4) If found change any of the "exit_rate.x" (.x being the exit number) for "exit.x" (.x being the exit number)
5) If not found procede to add the following
[exits]
number_of_exits = x (x being the number of exits the aircraft has)
exit.x = 0.4 (.x being the exit number starting with "zero")
Repeat until the number of exits has being reached.
Hope this is clear enough.
-
5) If not found procede to add the following
[exits]
number_of_exits = x (x being the number of exits the aircraft has)
exit.x = 0.4 (.x being the exit number starting with "zero")
Repeat until the number of exits has being reached.
If the aircraft.cfg never had an [exits] section to begin with (like the default Ultralight), it would be easier to simply use this one:
[exits]
number_of_exits=1
exit.0=0,0,0,0,0
In any case, editing the aircraft.cfg is needed only if you urgently need to fly that specific airplane now, because we'll surely fix the issue very shortly.
-
Hi
Firstly my apologies for the delayed response to your suggestion on the C185 exits syntax, I edited the aircraft.cfg file with your exits entry and I am happy to say that FSX now starts without any warnings or crashes, so it would seem to be the exits entry as you rightly suggested, thank you for your help on this one.
In addition I would also like to say thank you for the outstanding support given on this issue, especially at the time of day that I put the request in at, I really do appreciate the extra effort you have put into resolving the error and the information on how to fix it.
Jim Hodkinson
-
Problem has been fixed with the current Live Update.
-
Works great!
Thanks for outstanding support of a great product.
-
Same problem here as well. My Couatl.err file looks identical to the first posting by "Hodge001". Most recently I was flying the Carenado 152II with FSFlightSchool Pro, Actrive Sky 2012, TrackIR v5 and A2A's "Accu-Feel". Everything was working fine just 24 hours ago. Now... constant "The addon <unknown> is causing the Couatl Scripting Engine to restart..." pop-ups. I hope there's an answer to this mystery ASAP. Looks like I'll need to uninstall GSX until one's found.
-
Same problem here as well.
The problem has been found and fixed since a couple of days already, if you are still seeing it, it's because you haven't applied the latest Live Update.
-
Same problem here, after having downloaded the last GSX version and the latest addon manager from your site. The problem occurs with any FSX aircraft, including the trike, Microsoft 737, Airbus, 737NGX, Captain Sim 757, etc.
The warning message which appears is exactly the same as for the other users.
The problem seems cured when I revert to version 1.3 of GSX (uninstall everything, reinstall v1.3 AND addon manager which I had downloaded at the same time than v1.3), replace "false" bglmanx file (0 k) with a good one).
For now, I'll stay with GSX version 1.3 which is rock solid on my specific system : I'd rather be flying, as they say...
Thanks for your support
-
Sorry, but it's not possible you are still having the problem after the most current Live Update. If you are still seeing it, it's because you haven't applied the latest Live Update.
The problem occurs with any FSX aircraft, including the trike, Microsoft 737, Airbus, 737NGX, Captain Sim 757, etc.
No. That problem (before it was fixed) occurred ONLY with airplanes with NO EXITS section in the aircraft.cfg. Unless you are having a DIFFERENT error. In this case, please post the Couatl.err report, because your problem might be entirely different.
The problem seems cured when I revert to version 1.3 of GSX (uninstall everything, reinstall v1.3 AND addon manager which I had downloaded at the same time than v1.3), replace "false" bglmanx file (0 k) with a good one).
Fact you had a 0k bglmanx.dll, seems to indicate your internet connection is not working, or another program (a firewall?) is blocking online access to the installer, which explains why you haven't got the most current Live Update.
-
Sorry Umberto, but when I tell you this error happens with any aircraft I choose, I mean "every" aircraft, not just the ones with no exits.
Anyway, please don't bother with this if I'm the only one with this kind of problem : as I said in another post, for technical reasons, my flight sim PC has no speed connection, just a prediluvian 56k modem. The simple fact of downloading Live updates on my machine takes ages.
For now on, I'll stick with version 1.3 and I'll do a complete reinstall when the next generic update will be available...
Thank you for your support and congratulations for GSX, which I guess is a terrific coding work !
Henri R
-
Sorry Umberto, but when I tell you this error happens with any aircraft I choose, I mean "every" aircraft, not just the ones with no exits.
Then it must be ANOTHER error because, as I've said, the error mentioned in the post happens ONLY with airplanes with no exits.
Anyway, please don't bother with this if I'm the only one with this kind of problem : as I said in another post, for technical reasons, my flight sim PC has no speed connection, just a prediluvian 56k modem. The simple fact of downloading Live updates on my machine takes ages.
Just download the most current Full installer from another PC, and install it on the flight sim one, then apply the last Live Update, which should be fairly small (about 1MB) if you started with a full installer using the most current installer.