General Category > General Discussion

Prepar3D v3.2 - another Couatl Problem ***SOLVED***

<< < (3/3)

virtuali:

--- Quote from: Mickeyj on May 10, 2016, 07:35:23 pm ---Hmmm, i dont use the Avatar nor do i fly MP.
--- End quote ---

These are just two examples that we KNOW of. There might be other possible reason we still don't or and/or, don't have the mean to test, because we don't have the affected addons.

An user reported it happened with ASN, and it was fixed by switching to Opus.

Mickeyj:
Hello Umberto,

i solved the problem. As you expected it had something to do with my system. I reinstalled v3.2 but this time in its default folder structure E:\program files(x86)\Lockheed Martin\Prepar3D v3

Last night i tried nearly every solution i could find about Couatl and v3.x. Even clearing the dll and exe.xml didnt help. So my guess about the installation folder structure was right.

I had v3.1 installed E:\program files(x86)\Prepar3D v3 after an previous uninstall of v3.0. As all FSDT and FB sceneries were working in v3.0 in it default installation folder structure it must had something to do with the installation folder structure. Guess that the add on manager was a bit confused. If time permits you guys could try sometime to reproduce the error.

virtuali:

--- Quote from: Mickeyj on May 11, 2016, 10:27:20 am ---Guess that the add on manager was a bit confused. If time permits you guys could try sometime to reproduce the error.
--- End quote ---

The Addon Manager doesn't have anything to do with this. You are getting errors in the Couatl.log. If there was a problem with the installation folders, like registry entries pointing to the wrong version of the sim, the programs wouldn't even start.

Again, the error you are getting are happening inside our software. You should really try to understand how Simconnect works: it's a client-server application. What you are looking at, are NOT "Couatl errors", but messages FROM Simconnect, saying "you sent me the wrong parameter for this call", so we print them for troubleshooting.

The issue is, the parameter Simconnect says it's receiving from us, are NOT what we are sending! If we were really sending "wrong" parameters, it will happen everytime and we could have fixed it long ago, since from the diagnostic message it would be obvious for us what the error would be.

But instead, the value of the parameters looks entirely bogus, and are not what we sent to the sim, which seems to indicate that some kind of internal corruption happens in the sim, triggered by some conditions.

Yes, a mix-up of files from old and new versions of the sim might cause this.

Just as a check, are you SURE your API.DLL file is the correct one ? That's the file which interprets Simconnect calls...

Mickeyj:
Just to make it sure, i do not blame FSDT´s software. I do understand that simconnect sometime can do weird things. Most of all it runs on a MS windows based system. And i just wanted to offer a possible solution which in the end worked out at least for me. Im now happy that everything is in the right place and works as intended.

I did an upgrade from v3.1 to 3.2 few dys ago. Maybe the installer mwssed up things however there were no errors during patching. I cant tell you if the api.dll was the correct one. I asume yes as every other payware add ons were running fine. The test with v2.5 showed me AND prooved your theory that it had something to do with some simconnect/api.dll gizzmos.

Anyhow i also installed ASN again and the add on manager as well as FB KDEN works as intended and fluid. No errors anymore.

Many thanks for your support.

Navigation

[0] Message Index

[*] Previous page