Developer's Backdoor > GSX Backdoor

No GSX Menu

<< < (3/3)

mroschk:
i added the file: Couatl.ini in the Directory :C:\Users\username\AppData\Roaming\Virtuali

and now i have a log file: Couatl.log


--- Code: ---Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.1 (build 3536)
log started on Mon Sep 05 23:48:41 2016

connecting to SimConnect...
connected to SimConnect
bglmanx non ready yet, waiting.
Connection with FSX lost (has it crashed?)
disconnected from SimConnect.

--- End code ---

bglmanx non ready yet, waiting. ... ?? maybe here is the error?

virtuali:

--- Quote from: mroschk on September 05, 2016, 10:59:11 pm ---i really wonder why there is no error file ?
--- End quote ---

Because there hasn't been any error. The Couatl.err file, as the name says, only lists errors happened in Couatl, and there are none.

virtuali:

--- Quote from: mroschk on September 05, 2016, 11:39:10 pm ---bglmanx non ready yet, waiting. ... ?? maybe here is the error?
--- End quote ---

Well, it seems that bglmanx.dll hasn't started for some reason. The possible reason why it hasn't started are:

- The antivirus blocking it

- The P3D version wrong. But according to your report, you have the only 1.4 version that is supported...

- A problem with missing libraries.

You might try to use the Depends utility over fsdreamteam\bglmanx.dll

http://www.dependencywalker.com/

Use the x86 version and open the P3D\bglmanx.dll file. It will likely tell you which system libraries are missing/corrupted on your system. This won't FIX your problem automatically, but you should at least know WHAT's causing it.

mroschk:
Hi,

i gave up with P3D v1.4, deinstalled all and reinstalled FSX now.
And juhu...it works.

But i wonder why?

After the last try with P3D v1.4 i did not Change any runtime lib !
So it can not really be a Problem of the runtime lib`s.

Also i wonder why you say GSX Needs VC++ 2005 runtimes, but GSX installs VC++ 2013 runtimes ??
It is a bit curios, why did GSX not install all what GSX Needs to run after installing?

virtuali:

--- Quote from: mroschk on September 06, 2016, 11:00:06 pm ---Also i wonder why you say GSX Needs VC++ 2005 runtimes, but GSX installs VC++ 2013 runtimes ??
--- End quote ---

GSX needs the VC+2013 runtimes for ITSELF, because this is in line to LM suggestions to use those runtimes to minimize the chance of conflicts between addons, and it's also the same runtime used by FSX:SE, so it makes sense that we would use that one as well.

However, GSX (like any other addon), needs Simconnect to talk with the sim, and it uses the FSX/SP2/Xpack version, which is why it installs the client when you run under P3D. So, it's the Simconnect CLIENT, which needs the VC++ 2005 SP1 runtime libraries because, even if GSX could theoretically work just with the 2013 ones, without the Simconnect client working correctly, it won't be able to talk with any version of the sim, so you need to install also the libraries needed  by the Simconnect client.

Navigation

[0] Message Index

[*] Previous page