Couatl crashes in KSEA, CYVR disappears

[Tozzifan]

Hello,
on my maiden trip to the newly purchased CYVR, I had GSX's Couatl crashing in (T2G) KSEA during pushback with Majestic Dash; I continued my taxi and flight to CYVR, just to find ...only blurred runways

CYVR works perfectly on my system, my non-expert question is:

can some way Couatl be restarted in-game without restarting a flight from beginning? (to have the airport restored)

thanks

[virtuali]

Was it a Couatl panic message, with the message from the program asking if you wanted to open the error log ? If you missed it, you can check it here:

%APPDATA%\Virtuali\Couatl.ERR


Or, was the program just crashing, like a standard Windows crash ?

[Tozzifan]

if I remember correctly, not sure 100%, a windows dialog opened telling the usual something like "application has stopped working"

my Couatl.err file indeed looks like  a very old log ....

couatl v3.2 (build 3829)
panic log started on Sat Sep  2 10:22:29 2017

problem raised by addon <unknown>
Traceback (most recent call last):
  File "couatl\GSX\__init__.py", line 214, in prepareGate
  File "couatl\GSX\parkingServices\__init__.py", line 114, in setGate
  File "couatl\GSX\parkingServices\followMe.py", line 163, in __init__
  File "couatl\GSX\__init__.py", line 926, in findSuitableParking
AssertionError
{'Requested FollowMe to': 'Runway 24 Start', 'Airport': 'PAFB', 'User Pos': (64.83847527271699, -147.6059630702435, 140.876 m, 2.49675 m, 6.450246249764197)}

[virtuali]

If you have logging enabled in the settings, the error report would be in the Couatl.LOG file, not the .ERR file. See if you have anything there.

[Tozzifan]

I'm sorry, to me the content of this file is almost chinese language  when trying to translate it into action

[Tozzifan]

again, about flying from KDEN (FlightBeam) to KIAH, this time I was prompted to restart Coautl

the .log file (this time I think I've got the right one that I was asked to save and view) is just renamed to zip

[virtuali]

First, you posted the Couatl.LOG file at the wrong time, clearly not immediately after the error but, most likely, in another session where no error appeared, or you quit the sim before the error appeared, so it wasn't logged.

In any case, I can see from your log you haven't updated the program, which is normally not possible, since the Live Update would update all files when it runs.

A most common reason for the Live Update not updating everything, is that your antivirus is mistakenly blocking the download of some files, but not all of them, which will cause a mixup between new and old files.

Configure the antivirus to exclude the whole Addon Manager folder, and run the FSDT Live Update again, when the sim is NOT RUNNING: