Products Support > GSX Support FSX/P3D

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

<< < (3/5) > >>

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

virtuali:

--- Quote from: Beech_Air on November 30, 2024, 03:30:57 pm ---Same problem here. Not fixed with version 3.3.0 from November 26th, 2024.
--- End quote ---

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:

--- Quote from: Beech_Air on November 30, 2024, 03:50:30 pm ---If I delete intelliscene.cfg everything works fine.
--- End quote ---

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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version