Products Support > GSX Support FSX/P3D

Airport cache regeneration with failure

(1/2) > >>

pesz:
Hi there,
I have a problem with GSX for P3D v3. I'm pressing shift+f12 but nothing happens. When I try to reboot airport cache it says "Airport cache regeneration completed with failure in 5 seconds". Tried to download SODE, GSX and addon manager already and reinstall all products but no change. It happens on either default and payware airports, all used to work properly before. Any tip?
Thanks,
Piotr.

virtuali:
the most likely cause for a crash while regenerating the cache, is a corrupted .BGL. If you enable error logging in GSX, you might be able to get a diagnostic of the related file.

You can enable logging without being able to access the GSX interface, this way:

open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case l and a capital F )

Save the file as couatl.ini in the %APPDATA%\Virtuali folder, run the sim and then exit after it finished loading. Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content.

pesz:
https://image.ibb.co/iLmana/addons.jpg


Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.1 (build 3625)
log started on Sat Jun 10 10:21:10 2017

Found gsx.cfg file at C:\Users\szmig\AppData\Roaming\Virtuali/Airplanes\Aerosoft Airbus A319 CFM\gsx.cfg
Traceback (most recent call last):
  File "couatl\common\fsm.py", line 73, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\__init__.py", line 826, in do
AttributeError: 'module' object has no attribute 'gsx'
{}
User collision geometries reloaded
Changed AVATAR id (3)

virtuali:
You are using an outdated version of the program, and the error was caused because you disabled GSX. Update to the current version.

pesz:
Thanks for your support.
Ok, followed all steps and now I'm getting this issue with SODE 1.5.2



It's going through with v4 but it refuses to work with v3. All works fine on 1.4.2

Navigation

[0] Message Index

[#] Next page