FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: KojbanCZ on May 18, 2020, 11:11:11 am
-
Good morning to everyone,
I have struggles with GSX for almost one week. The problem is simple - whenever I install (reinstall) GSX, and start P3Dv4, everything is all right. However, any next time I start P3D, I have only FSUIPC and SODE in Add-ons folder in ALT menu in-game.
Antivirus disabled, clean GSX (+ AddonManager) installation.
Does anybody know the solution?
Thanks,
kojban
-
What happens if you run the FSDT Live Update first ?
Also, as explained so many times on the forum, the antivirus should NOT be disabled. It should be CONFIGURED to add the Addon Manager folder to the antivirus Exclusion list. This because some antivirus still work in the background even if they "seem" disabled, because they really aren't ( their system service is still running ), that's why we never suggested to disabled it, but configure it properly by adding the Addon Manager folder to the antivirus Exclusion list.
- Configure the antivirus to exclude the whole Addon Manager folder from scanning
- Run the FSDT Live Update
- Reboot Windows. If some of your system libraries ( usually VC++ ) are outdated, sometimes they require a Windows reboot to complete the installation.
-
Yes, my bad - the whole Addon Manager folder is in exceptions in AV.
It downloads and scans C++ libraries, but does not install imo.
After rebooting, same state... :(
-
It downloads and scans C++ libraries, but does not install imo.
What do you mean with "does not install" ? Do you mean:
- It skips the installation because you already had the runtimes installed ?
OR
- It doesn't install, because of some error ? If yes, which error ?
-
It skips the installation, they are installed already.
-
Then some of them must have a problem, one the official MS installer we start is not detecting so, it thinks the runtime is ok, so it's not reinstalling it or fixing it.
- Uninstall the MS VC++ Universal Runtime from the Control Panel
- Uninstall the MS VC++ 2013 too
- REBOOT Windows
- Run the FSDT Updater again, to let them install again.
-
Uninstalled all of the VC++, rebooted, started Updater and waited until it does its things. After that I have C++ 2005 installed, C++ 2015-2019 (64 and 86).
Is it enough - just 3 of them?
(Still no change in sim - still missing.)
-
After that I have C++ 2005 installed, C++ 2015-2019 (64 and 86).
You should have MS VC++ 2013 as well.
-
2013 updated from https://www.microsoft.com/en-us/download/details.aspx?id=40784.
Still same... :(
-
The thread named "Addon Manager not showing up in P3Dv4 **SOLVED**" thread lists all the known solutions for missing menu entries from the "Addons" menu:
http://www.fsdreamteam.com/forum/index.php/topic,17484.msg122656.html#msg122656
-
Thanks. All steps are done, but no change... :(
LogFile:
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 4336)
log started on Thu May 21 17:47:51 2020
connecting to SimConnect...
connected to SimConnect
bglmanx non ready yet, waiting.
Connection with FSX lost (has it crashed?)
(Connection lost appeared after P3D shutdown.)
-
Your log shows something is VERY wrong with your simulator installation, because it says "Connection to FSX lost", but you said you use P3D4.
It should have said connection to "Prepar3d4", so it seems it's running in FSX mode, which of course won't work. Have you ever used those very dangerous "Migration Tools", that allows to install things made for FSX into P3D ? Even in the past ?
-
I have got just FSX registry due to some sceneries. However, no migration tools.
-
I have got just FSX registry due to some sceneries. However, no migration tools.
If with "just FSX registry", you mean you create a fake FSX registry entry pointing to P3D to install sceneries without a proper P3D installer, you made exactly the same damage the migration tool did, because proper P3D products that supports both FSX and P3D separately cannot work with a registry hack.
Remove all the FSX keys if you don't have FSX, otherwise nothing will work.
-
Removed... I hope so.
No change. Should I reinstall the GSX?
-
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.
-
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. :(
-
Check again the log and see if GSX started in FSX mode as in your previous log.
-
Still looks like this:
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, ...".
-
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.
-
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...
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... :-[
-
Here is the log...
That' still your old log from May 22th, are you sure you re-enable logging after reinstalling everything ?
-
It is not.
See "log started on Sat Jun 27 14:42:06 2020" in the beggining.
-
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.
-
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.
-
What should be in dll.xml or exe.xml in APPDATA? I have nothing connected with GSX there...
-
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.