ERROR

[LeeCley]

couatl v3.2 (build 3894)
panic log started on Sat Mar 31 15:48:52 2018

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\__init__.py", line 400, in <lambda>
  File ".\common\youcontrol.py", line 231, in showMenusWithSameTag
  File ".\common\youcontrol.py", line 86, in showContainer
  File ".\common\youcontrol.py", line 210, in show
IndexError: list index out of range
{'Airport': 'SBGR', 'Requested assistance services at': 'Gate H 304', 'User Pos': (-23.428185490924296, -46.48239220073586, 751.921 m, 2.41823 m, 264.64264020650717)}

[virtuali]

Already discussed and answered here:

http://www.fsdreamteam.com/forum/index.php/topic,17400.0.html

[ATCRC]

I am having the same issue, I Have the FX steam edition, This started happening after the latest update.
Any suggestions?
 

[virtuali]

I am having the same issue, I Have the FX steam edition, This started happening after the latest update.

Sorry, but you cannot possibly have exactly the same error with FSX, since it's specific to P3D 4.2. Please post your error log.

[ATCRC]

Here is the error log

[virtuali]

Here is the error log

Just as I thought, your error it's totally different, and it shows you haven't updated the software:

couatl v3.2 (build 3894)

Your couatl.exe program is still the old version, while the python scripts that runs GSX have been updated but, since they require the latest couatl.exe, they won't work.

Since it's not normally possibly to launch the FSDT Live Update and getting a mixup of files and we surely have the latest couatl.exe online, the only possible reason I can think of, is your antivirus blocking the executable, because of a false positive bug.

- Configure the antivirus to exclude the Addon Manager folder from scanning.

- Run the FSDT Live Update again, and notice if it downloads the latest couatl.exe, which as of today it's version 3985.

[ATCRC]

THank you that was it; the antivirus was keeping the upgrade to be completed.

[virtuali]

THank you that was it; the antivirus was keeping the upgrade to be completed.

It's always the antivirus...and when we complain to antivirus makers (something we used to do in the past, but we have lost faith in, at this time), their usual reply is their antivirus doesn't catch our software and this would be "fixed" in the next update.

They suggest that, in order to prevent false positives, developers should digitally sign executables. Which we obviously do, not just with one, but with TWO signatures, one which is the one which identify us as developers (authenticode), and another one, which is the supposed industry standard to prevent false positive, which is called "Software Taggant".

The issue is, some antivirus trust more their flawed heuristics rather than proper and industry accepted digital signatures, like the dreaded "reputation" system used by some (like Norton) so, as file is *assumed* to be dangerous, until it has built enough reputation to be considered safe. Which basically defeats the purpose of constantly updated software.