FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: edwardsja on December 30, 2019, 08:32:56 pm
-
couatl v3.2 (build 4281)
panic log started on Mon Dec 30 11:15:55 2019
I have tried everything suggested but still GSX fails to load , please help. I am not a computer whiz.
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\GSX\__init__.py", line 783, in checkAirplane
File ".\GSX\__init__.py", line 932, in onEnteredAirport
File ".\GSX\parkingServices\__init__.py", line 41, in onEnteredAirport
AttributeError: type object 'FollowMe' has no attribute 'setClassVarRequestable'
{'Airport': 'CYV2', 'User Pos': (49.18475556254982, -123.16126672815301, 5.42602 m, 1.15902 m, 279.9254408816466)}
Creating model cache...
reset FSDT_GSX_AIRCRAFT_EXIT_1_TOGGLE to 0
-
The problem doesn't happen here and, the only possible reason for this error, is that you haven't all the files updated to the latest version, which dates Dec. 12th.
A common reason for not all files being updated is:
- Your firewall is blocking the Live Udpate, preventing to update all files. Disable the firewall or configure it to be sure is not blocking the Live Updater
- Your antivirus doing the same thing, blocking the Live Udpate, preventing to update all files. Disable the antivirus or configure it to exclude the whole Addon Manager folder.
-
I've attached my error log on this topic as well.
Umberto, I know, we discussed that on a previous topic when some sceneries haven't been activated correctly, which was than resolved by reformatting the PC completely.
As part of the fresh installation I configured my Windows AV as well as the firewall the way you described in many posts before and GSX ran completely fine until the latest update that you mentioned above. I've changed absolutely nothing and get the same error as well when I try to request a follow me car to the runway.
Any suggestions?
-
You don't say if you ran the FSDT Live Update now, after my reply.
-
Yep I did:
Releasdate : December 13th 2019 and that's when the error showed up.
-
I can only repeat and confirm that error cannot happen with the current update. Do it again, please.
-
Ok I will and report back later. Thanks.