Products Support > GSX Support FSX/P3D

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

(1/5) > >>

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.

Navigation

[0] Message Index

[#] Next page