GSX does not work at airports with AES and intelliscene.cfg

[HardyZ]

I know that this error has already been discussed in other threads. However, I haven't found a solution yet.
I noticed this error about 2 weeks ago.
FSX 10.0.61637.0
On AES airports and with aircrafts that have an intelliscene.cfg, GSX (couatl v3.2 (build 5318)) crashes when loading the airport cache. All aircrafts have a correct gsx.cfg in \AppData\Roaming\Virtuali.
This is always the last entry in the couatl.log (example):

Loading aircraft data from Airplanes\Airbus A320 FD_CFM
this airplane has 4 exits
Added Menu SubItem "Show GSX Menu by-passing YouControl Ctrl+F12" (parentId 83, id 94)
ATC_ID_SIM read from Simconnect is F-GJVB
intelliscene.cfg provides aircraft data with priority 1
Using aircraft data from intelliscene.cfg
Traceback (most recent call last):
  File ".\common\__init__.py", line 616, in onSimStart
  File ".\common\collisions.py", line 55, in reloadGeometries
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\aircraftData.py", line 2381, in getAircraftData
  File ".\common\aircraftData.py", line 1019, in __init__
ValueError: need more than 31 values ​​to unpack
{}
Preload operators thumbnails...

The last line is different every time.
If you delete or deactivate intelliscene.cfg, the GSX Airport cache will be loaded correctly and the error will no longer exist. However, this is not a solution because it means that all AES functions and AES jetways that cannot be replaced by GSX jetways no longer work.
From my information GSX should ignore intelliscene.cfg if a gsx.cfg exists.
Do you have a solution?

I observed the error on 2 different systems (win7 64-bit). I have already reinstalled GSX and updated it with Live Update.

Thanks for Your answer
Hardy

[TheCaptain3618]

Remove the intelliscene.cfg file from the aircraft folder. It seems you don't need AES anymore as it is outdated and no longer supported.

[HardyZ]

Does this mean that AES Airports with jetways are no longer usable even though a correct gsx.cfg exists?
If intelliscene.cfg is deleted and the jetways cannot be replaced, only duplicate jetways can be inserted. Shouldn't intelliscene.cfg be ignored if a correct gsx.cfg exists?
What irritates me is the line in the log file:
intelliscene.cfg provides aircraft data with priority 1

[virtuali]

Run the FSDT Updater now, it should be fixed, even with an intelliscene.cfg file.

[HardyZ]

WOW - it seams (!!!) that the error is solved with the latest gsx live update. I hope so.... I will test it

Edit February 29, 2024:
All works fine - problem is solved. Thank You for Your fast and good support.

[HardyZ]

Sorry -
same error since latest Update yesterday. What to do?


Reminder: Last time it took less than 3 hours to fix the problem (see above). What is wrong with your support this time?

April 06: The error appears to be solved with latest update of today. Thank you.

[HardyZ]

Apart from the fact that GSX L2 for FSX no longer starts at all since the last update 3.2.9 from November 23rd, 2024 (see http://www.fsdreamteam.com/forum/index.php/topic,32512.0.html):

In 3.2.7 GSX L2 for FSX at least still started. But not without errors - the same error as above, but not with a crash, but without visible passengers and crew at airports with AES and with aircraft with intelliscene.cfg.
I know: AES is outdated. Nevertheless, there are many (expensively paid) Aerosoft airports with AES that cannot be used without intelliscene.cfg because the jetways cannot be removed. This error was quickly corrected twice at the time.

[virtuali]

Your posts has been removed, don't you even dare to question my "seriousneed", just because you were pissed off how wrong you were when you tried to imply the boarding delay won't be fixed, and in fact it has.

We can only dedicate to P3D a percentage of time in proportion to the user base. Anything different will be unfair to the vast majority (today more than 99%) of users using MSFS, which would rightly complain if we spent too much time supporting a dying platform.

Of course, the extremely minor ( AES died YEARS before P3D ) issue with intelliscene files, will be fixed, just as everything else.

[HardyZ]

Hello Umberto,
I will doubt your seriousness as long as you cannot provide working software that I paid for. o matter how long ago it was.

The boarding delay has been resolved. However, other errors were regenerated. GSX L2 doesn't work at all at the moment.

We paid for GSX L2 for FSX and we can expect it to work.

By the way: don't remove my posts. Your reaction shows that I'm right.

[virtuali]

The boarding delay has been resolved

Proving you wrong.

However, other errors were regenerated. GSX L2 doesn't work at all at the moment.

And it will work again, obviously.

[Beech_Air]

Same problem here. Not fixed with version 3.3.0 from November 26th, 2024.

[virtuali]

Same problem here. Not fixed with version 3.3.0 from November 26th, 2024.

Of course, because it's NOT the same problem.

Nothing to do with intelliscene files in your error, this is a completely new issue but, it's just cosmetic, it won't affect anything, since if you are seeing that message it's because you quit FSX so the error is not causing any issues but of course, will be fixed in the next update as well.

[Beech_Air]

What does this mean:"but, it's just cosmetic, it won't affect anything,"?
GSX does not start on airports with AES and airplanes with intelliscene.cfg. The error message is: The addon <unknown> is causing Couatl Scripting Engine to restart. A restart does not work.
If I delete intelliscene.cfg everything works fine.

Edit: Except the AES airport...
Yes, I closed FSX because GSX crashed when I selected another airplane

[virtuali]

If I delete intelliscene.cfg everything works fine.

The error log you posted didn't show anything related to intelliscene, which is completely different error that would happen start, and it's fixed. See the OP log:

Traceback (most recent call last):
  File ".\common\__init__.py", line 616, in onSimStart
  File ".\common\collisions.py", line 55, in reloadGeometries
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\aircraftData.py", line 2381, in getAircraftData
  File ".\common\aircraftData.py", line 1019, in __init__
ValueError: need more than 31 values ​​to unpack

The error you posted shows a completely different error that is unrelated to that, and would happen only on exit, see your log:

GSX SimStop
Restarting Couatl...
Traceback (most recent call last):
  File "<string>", line 28, in OnExit
  File ".\common\__init__.py", line 716, in onAppQuit
AttributeError: type object 'Application' has no attribute 'simCrashed'

Completely different issues and again, the error in your log won't affect anything, because it's happening on exit.

As I've said, this NEW error completely unrelated to the previous one, will be fixed in the next update.

[Beech_Air]

Maybe it would be good if you would provide a version without errors?
i think that it should also be in your interest that your software works. How many more updates do I have to wait for?