Products Support > GSX Support FSX/P3D

Error AFCAD

<< < (2/2)

edwardpat:
I had this same error today after the latest FSDT Live Update:

couatl v4.0 (build 4459)
panic log started on Sat Sep 26 20:23:18 2020

problem raised by addon __init__.py
Traceback (most recent call last):
  File ".\GSX\DLC\Jetways\__init__.py", line 50, in onPurchased
  File ".\GSX\DLC\Jetways\__init__.py", line 29, in tryActivate
  File ".\GSX\__init__.py", line 765, in showErrorMessage
  File ".\GSX\__init__.py", line 748, in showMessage
AttributeError: 'GSX' object has no attribute 'uiVerbosity'
{}

Got several messages too about Activation of the FSDT products along with messages about activation errors in Esellerate. Had to run the Live Update twice and the Re-start Couatl and rebuild the airport cache inside P3D once, and now it seems GSX is working Ok. Haven't gone to the different FSDT airports to check if each of them are properly usable/shown, no time for all that.

virtuali:

--- Quote from: edwardpat on September 27, 2020, 02:50:11 am ---Got several messages too about Activation of the FSDT products along with messages about activation errors in Esellerate.
--- End quote ---

After updating to the 64 bit version of the problem, it's entirely normal you had to reactivate all the activations which were obtained by Esellerate, as explained here:

http://www.fsdreamteam.com/forum/index.php/topic,24267.msg161303.html#msg161303


--- Quote ---Had to run the Live Update twice and the Re-start Couatl and rebuild the airport cache inside P3D once, and now it seems GSX is working Ok. Haven't gone to the different FSDT airports to check if each of them are properly usable/shown, no time for all that.
--- End quote ---

There wasn't any need to run the updater twice, and surely not to rebuild the cache because, one of the things the updater does ( even when it's run once and, of course, it wouldn't be any different if it was run once ), is to automatically remove all the airport cache files.

Because of this, the first startup after the update, the cache is being rebuilt automatically, so it takes longer than usual to start, so you might think GSX hasn't started ( it was still rebuilding the cache, instead ), so you force a cache rebuild manually, you now expects it to take longer so you let it run, and when you see it's working, you think it was because you had to rebuild the cache. It's not, the cache was already removed ( so a rebuild already started ) by the updater.

Navigation

[0] Message Index

[*] Previous page