Author Topic: GSX error scripting engine restarting solved (Read 18669 times)

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

virtuali · « **Reply #1 on:** April 18, 2012, 10:52:03 pm »

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.

ETNWHVAC · « **Reply #2 on:** April 18, 2012, 11:07:24 pm »

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

Hodge001 · « **Reply #3 on:** April 18, 2012, 11:07:46 pm »

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

virtuali · « **Reply #4 on:** April 18, 2012, 11:19:05 pm »

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.

Hodge001 · « **Reply #5 on:** April 18, 2012, 11:26:12 pm »

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

ETNWHVAC · « **Reply #6 on:** April 18, 2012, 11:42:21 pm »

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.

virtuali · « **Reply #7 on:** April 19, 2012, 12:53:30 am »

Quote from: Hodge001 on April 18, 2012, 11:26:12 pm

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.

Cristiano Mueller · « **Reply #8 on:** April 19, 2012, 12:56:54 am »

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

colang · « **Reply #9 on:** April 19, 2012, 12:57:46 am »

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.

virtuali · « **Reply #10 on:** April 19, 2012, 01:01:38 am »

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.

colang · « **Reply #11 on:** April 19, 2012, 01:25:17 am »

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!!

virtuali · « **Reply #12 on:** April 19, 2012, 01:28:28 am »

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.

colang · « **Reply #13 on:** April 19, 2012, 01:40:47 am »

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.

ETNWHVAC · « **Reply #14 on:** April 19, 2012, 01:49:23 am »

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.

News: