You should seriously consider reversing this version back to beta, since this update does not work fully.
We have been in Beta 6 months, and this version is way more stable than the previous version ever was. See here for another user that fixed it:
http://www.fsdreamteam.com/forum/index.php/topic,12371.msg93963.html#msg93963The problem was the antivirus, and was fixed by following what has always been our suggestion in this specific case, which is to exclude the whole simulator folder from scanning.
For example, during airport cache regeneration, if the addon does crash, even after turning Prepar3D off, couatl.exe is still active and does something.
What do you mean with "the addon crash" ? You mean the SIM crashes, or another addon cause the sim to crash ?
Whatever the reason, if the sim crashes, it's normal that Couatl couldn't close normally, because it's the SIM that has the responsibility to close it, not Couatl that is supposed to "close itself" so, of course, if the sim crashes for any reason, it will not have a chance to close the executables IT has launched and is supposed to close. This was the same for any reason.
According to Task Manager, it uses up around 30% of CPU's power.
Couatl doesn't normally use that much CPU power, but if your sim crashed while it was regenerating the cache, that's seem to be normal. As I've said, the problem is that it's the sim which is supposed to send a message to Couatl to close it, via Simconnect. However, if the sim crashed, the communication is broken, and Couatl cannot receive that message anymore, so it's likely got stuck.
I've attached the log for any reference.
