Author Topic: Error AFCAD  (Read 2414 times)

franciscomv

  • Newbie
  • *
  • Posts: 7
Error AFCAD
« on: December 03, 2019, 05:45:35 pm »
When I try to enter in the menu GSX I get an error saying that not found a valid ASCAD data in this position.
This occurs in every airport and position.
Some help?

Thanks in advance

Francisco Mateos

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50700
    • VIRTUALI Sagl
Re: Error AFCAD
« Reply #1 on: December 04, 2019, 01:14:04 pm »
Be sure you have the latest Live Update installed.

anthonybarthur999@gmail.c

  • Newbie
  • *
  • Posts: 1
Re: Error AFCAD
« Reply #2 on: September 24, 2020, 03:28:06 am »
Have the same problem.
This morning I ran live update and when I ran P3d after the update GSX comes up with a missing afcad for all airports warning
Now gsx does not work because of this

dwbluez

  • Newbie
  • *
  • Posts: 1
Re: Error AFCAD
« Reply #3 on: September 24, 2020, 05:13:47 am »
Same here! I just updated to the latest. Something told me not to. As usual, I didn't listen...

I'm not sure if this fixed it, but I re-ran makerwys. then reran the updater. Got the following error:

couatl v4.0 (build 4459)
panic log started on Wed Sep 23 20:27:19 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'
{}
User collision geometries reloaded
Changed AVATAR id (0)
I then restarted Couatl. Everythng seems okay for now.
« Last Edit: September 24, 2020, 05:46:36 am by dwbluez »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50700
    • VIRTUALI Sagl
Re: Error AFCAD
« Reply #4 on: September 24, 2020, 08:21:15 am »
This morning I ran live update and when I ran P3d after the update GSX comes up with a missing afcad for all airports warning Now gsx does not work because of this

Try a "Restart and rebuild the airport cache" command from the "Couatl settings menu".

edwardpat

  • Full Member
  • ***
  • Posts: 125
Re: Error AFCAD
« Reply #5 on: September 27, 2020, 02:50:11 am »
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.
« Last Edit: September 30, 2020, 03:46:35 am by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50700
    • VIRTUALI Sagl
Re: Error AFCAD
« Reply #6 on: September 30, 2020, 03:51:23 am »
Got several messages too about Activation of the FSDT products along with messages about activation errors in Esellerate.

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.

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.