Couatl Scripting Engine had stopped working

[gavinprice02]

Hi all,

I've recently just done a full re-install of FSX.  I downloaded all my FSDT products from the website last weekend and have installed them to my pc. I am now receiving the message  "Couatl Scripting Engine for FSX/ESP has stopped working" when I load up my flight.

I removed and re-installed all the VS2005 Redistributables and also told Microsofr Security Essentials not to scan FSX.exe and Couatl.exe.

I've checked the Event Viewer and this is what it came up with

Faulting application name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856
Faulting module name: couatl.exe, version: 2.0.0.2356, time stamp: 0x52702856
Exception code: 0xc0000005
Fault offset: 0x00010218
Faulting process id: 0x8d0
Faulting application start time: 0x01cf0e33ee6ed4e8
Faulting application path: E:\FSX\fsdreamteam\couatl\couatl.exe
Faulting module path: E:\FSX\fsdreamteam\couatl\couatl.exe
Report Id: 7006560a-7a27-11e3-8a1f-90e6ba603c15

Any help would be much appreciated.

Thanks

Gavin Price

[virtuali]

Maybe you have a permissions problem in your user account, or your preferences files might have been corrupted. Try to remove the following files/folders:

%APPDATA%\Virtuali\Couatladdons.ini
%APPDATA%\Virtuali\Keymapping.ini

C:\ProgramData\Virtuali\Couatl

Then reinstall GSX again with the full installer.

If that doesn't work, try to remove your %APPDATA%\Microsoft\FSX.CFG file, so FSX will rebuild a new one with default settings.

[gavinprice02]

Hi Umberto

I've tried all you have suggested but I'm still getting the same error message.
Any idea's of what I could try next, or any other information you require from me?

Thanks

Gavin

[virtuali]

I've tried all you have suggested but I'm still getting the same error message.
Any idea's of what I could try next, or any other information you require from me?

Another file that might cause this, is a corrupted scenery.cfg, try to post it here, I'll check for any errors. The correct file is located here:

C:\ProgramData\Microsoft\FSX\Scenery.cfg

[gavinprice02]

Ok here is my scenery.cfg

Thanks

Gavin

[August78]

Could you look through mine as well?
I have the same problem with coatl engine stops working. I have deleted my old fsx.cfg but still the problem persists. I have no installed any new software lately except upgrading Synapse 2.0 when installing my Razor Kraken headset.
I have an nvidia card (so no ATI software). I dont use chat programs.

[virtuali]

I have the same problem with coatl engine stops working. I have deleted my old fsx.cfg but still the problem persists. I have no installed any new software lately except upgrading Synapse 2.0 when installing my Razor Kraken headset.

No, you don't have the same problem. Your problem is very clear, and it's the "unspecified addonExecutable integrity compromised", which is caused by another software attaching to the executable in some way. The problem reported here it's just a generic crash, likely due to a corrupted file in FSX.

[August78]

Ok. I am at the end of what I can find out. The problem still persists. I need your help to make this work.

[virtuali]

Ok. I am at the end of what I can find out. The problem still persists. I need your help to make this work.

It's best if you continue to post about your problem, which is different than the one discussed here, on the thread you opened about it.

[gavinprice02]

Hi Umberto,

Just wandered whether or not you'd had the time to look at my scenery.cfg?

Gavin

[virtuali]

Just wandered whether or not you'd had the time to look at my scenery.cfg?

Yes, and it doesn't cause any problems here. However, that's not really a definite test, because it only shows your scenery.cfg is not corrupted or contains errors, but it doesn't say anything about each scenery are you have, which I can't obviously test without having exactly the same set of files you have so, there's no way to check if one of your areas contains, for example, a corrupted/invalid .BGL

Just to be sure the problem is/isn't related to the Scenery Library, try the following:

- Keep a backup of that scenery.cfg (well, it's here on the forum now...)

- Copy the scenery.cfg from your FSX root folder to the C:\ProgramData\Microsoft\FSX folder. This will reset it to default areas only.

Start FSX and, If there's no crash, you would know it IS something in your Scenery Library (like a corrputed .BGL somewhere). If the crash still happens, it means the cause is something else that we'll have to find.

[gavinprice02]

Hi Umberto

I've just replaced the scenery.cfg with the one from the FSX root folder and Couatl seemed to work fine. Is there any easy way I can fnd this corrupted bgl file?

Thanks

Gavin


--------
Update.

I just began by removing my addon scenery's to a temporary loacation elsewhere on my computer. I have discovered the problem only stops when I remove Orbx FTX Global Vector from FSX, specifically the folder FTX_VECTOR. This folder has so many bgl's and I really wouldn't know where to begin to look for the culprit file.

Gavin

[gavinprice02]

Hi again.

Just to let you know that I solved the issue by re-installing FTX Vector. Now all my FSDT scenery's and GSX are working perfextly.

Many thanks for your assistance Umberto.

Gavin

[virtuali]

Just to let you know that I solved the issue by re-installing FTX Vector. Now all my FSDT scenery's and GSX are working perfextly.

It was probably one of that many files which was corrupted.