GSX does not start

[virtuali]

No change. Should I reinstall the GSX?

Yes, of course, the installer must run when all the registry entries for all supported simulators are correct, and no keys for simulators that are not really installed are present.

[KojbanCZ]

All registry deleted, reinstalled (I have P3Dv4 only available when installing). Still the same - first start of the sim - running. After restart, no Addon-Manager nor Coutl nor GSX in Addon Menu.

[virtuali]

Check again the log and see if GSX started in FSX mode as in your previous log.

[KojbanCZ]

Still looks like this:

Code: [Select]

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

When P3D is running, the last thing in log is "bglmanx non ready yet, ...".

[virtuali]

Connection with FSX lost (has it crashed?)

So, is still running in FSX mode, meaning you haven't fixed the registry keys you changed to install non-compatible sceneries in P3D. You must Undo all the damage you made, otherwise nothing properly made for P3D that recognizes FSX as a different sim ( as it should ), will never work correctly.

[KojbanCZ]

Hello again.

After an complete wipe of all drives, I have done an complete installation of P3Dv4.

However, the problem still persists.

Here is the log...

Code: [Select]

Python 2.7.13 Stackless 3.1b3 060516 (default, May 22 2017, 13:45:26) [MSC v.1900 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.2 (build 4376)
log started on Sat Jun 27 14:42:06 2020

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

I really do not know what to do... 

[virtuali]

Here is the log...

That' still your old log from May 22th, are you sure you re-enable logging after reinstalling everything ?

[KojbanCZ]

It is not.

See "log started on Sat Jun 27 14:42:06 2020" in the beggining.

[virtuali]

See "log started on Sat Jun 27 14:42:06 2020" in the beggining.

Sorry, you are right, I was looking the build date of the program, not the log's date.

So, nothing has changed, your P3D4 registry keys are still wrong. Or, possibly, you still have FSX registry keys pointing to the P3D4 folder, which reinstalling just P3D won't fix.

[KojbanCZ]

Hmm, I kinda do not understand, how can I have wrong P3D registry or even FSX registry. I have done an complete new installation of Windows with complete deletion of all hard drives.

[KojbanCZ]

What should be in dll.xml or exe.xml in APPDATA? I have nothing connected with GSX there...

[virtuali]

What should be in dll.xml or exe.xml in APPDATA? I have nothing connected with GSX there...

Nothing, of course. GSX in P3D uses the native add-on.xml method. I'm sorry but, if the log says it's connecting to FSX, the only possible reason for that is your P3D is for some reason acting as FSX, as if the exe had a wrong version number.