Several problems after installing FSDT sceneries

[ajcbakker]

Dear all,

We got some serious problems with installing sceneries of FSDT. After installation of a particular scenery (we got more than one) we tried to startup FSX. We only see the startup screen of FSX and than the program hangs! So we have to kill the proccess through the taskmanager of windows. After a second start of FSX we see the following message (see att 1). When, despite the given advise, we approve the execution FSX will start in the end and runs normally.

Thus far we installed 4 FSDT sceneries (PHNL, CYVR, KLAX, KIAH) with the same problem mentioned above.

Now we installed KORD v2.0. we still have the same problem mentioned above. But after the second start FSX stops immediately (see 2nd att.) and we are not able to enter FSX anymore. What is going wrong here?

Please can anyone help us out?

Kind regards,
Alje Bakker

[virtuali]

After a second start of FSX we see the following message (see att 1). When, despite the given advise, we approve the execution FSX will start in the end and runs normally.

Yes, because that message is not real, the file doesn't have any problems, it's just a generic message that FSX issues when there's some kind of conflict between addons, or if the antivirus is interfering.

Try all the following:

- Restart Windows

- Always allow the module to run

- Configure the antivirus to exclude the following files from scanning:

YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\couatl.exe

YourFSXFolder it's usually C:\Program Files\Microsoft Games\Microsoft Flight Simulator X, if you installed it in the default folder.

[ajcbakker]

Many thanks for your reply.

All the things you mentioned we already did. But still the problem occurs!
Our main problem is the fact that FSX won't start after installing KORD v2.0 (see att no.2 of our first post).

Please help.

Regards
Alje Bakker

[virtuali]

Our main problem is the fact that FSX won't start after installing KORD v2.0 (see att no.2 of our first post).

It's not very clear what installer you used. First, be sure all your installers are the current version. And, try to install the current Stand-Alone Addon Manager AFTER all the sceneries, as the last thing you do.

[ajcbakker]

Dear sir,

Many thanks for your reply.

All the things you mentioned before we did (restart Windows, add all the exclusions to the antivirus).

We have installed subsequently the sceneries of CYVR, KLAX, KIAH and PHNL. After these installations we installed the latest version of the Addon Manager. So far, everything went ok except one thing; we still got the message "FSX has detected a problem......". See attachment.
At last we downloaded the latest installer of KORD. The installation and actvation went very well. After exiting FSX and again a restart of the program FSX hangs (we need to kill the process). So again a restart of Windows and startup FSX. FSX normally starts up and yes, here comes the same message again "FSX has detected a problem......". See the same attachment. When we click "yes" FSX runs normally.

Conclusion: we have the sceneries installed; FSX starts up and works but still the message above appears.

Is there something we can do about it? Or do we have to live with this issue?

Many thanks in advance and kind regards,

Alje Bakker

[virtuali]

Conclusion: we have the sceneries installed; FSX starts up and works but still the message above appears. Is there something we can do about it? Or do we have to live with this issue?

That message is a bogus message that comes out randomly from FSX, and it's usually caused by a Windows libraries conflict, usually caused by too many addons using different version of the VC++ runtimes libraries, which confuse the Windows subsystem that is supposed to allow all them running together in the same memory address space.

The solution is usually as follows:

- Always ALLOW the module to run, EVEN IF FSX CRASHES

- Try a couple of times

- Try after a Windows reboot.

- Be sure you turn off ALL compatibility modes for FSX.EXE and, eventually, try running FSX as Administrator instead, but with every compatibility option turned off.

[ajcbakker]

Dear sir,

Thank you for your quick response.
We give it a try and we keep you posted of the results.
Many thanks and kind regards,

Alje Bakker