FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: trening on September 23, 2020, 07:05:27 pm
-
Hi.
I am missing GSX after FSDT live update today. Probely all Fsdt airports too.
In the addon manager it says trial modus.
Any suggestion ?
Thor
-
- Configure the antivirus to add the whole Addon Manager folder to antivirus exclusions
- Run the FSDT Live Update again
- If that doesn't work, check if you have the VC++ 2008 runtimes installed. If you don't, download them from here:
https://www.microsoft.com/en-us/download/details.aspx?id=15336
- Install the runtime, reboot Windows and try the update again.
-
Thanks.
I did the first, will try the next step.
Thor
-
Hi.
No luck , i had the VC ++ 2008 installed, reinstalled but no sucsess. The same with antivirus exclusions.
-
I'm sorry but, I cannot reproduce the problem, but keep in mind nobody at FSDT ever uses 4.4 anymore. You must expect the next updates will only support ONE version of V4, the latest one, that is 4.5 HF3.
You can TRY to switch to the 32 bit version, as explained in the release notes:
https://www.fsdreamteam.com/couatl_liveupdate_notes.html
If you have issues with the 64 bit version, and would like to go back to use the previous 32 bit version in P3D4/5, change the Path tag in the Documents\Prepar3d Addons\ADD-ON.XML file:
Addon Manager\couatl64\couatl64_P3D.exe
change it to:
Addon Manager\couatl\couatl.exe
-
The same problem with the couatl64, but running on V4.5HF3.
I attached the couatl.log when using the 64-bit of couatl and wondering about line 15 (RunningMode::pathtoinstalledpackages) logs the path of the MSFS2020 installed on this system.
After applying the workaround with the 32-bit in the XML the menuentries are shown.
Hoping this helps for further investigations.
Joerg
-
wondering about line 15 (RunningMode::pathtoinstalledpackages) logs the path of the MSFS2020 installed on this system.
Not a problem, it's just a log message.
After applying the workaround with the 32-bit in the XML the menuentries are shown.
Hoping this helps for further investigations.
Yes, it helps a lot, because I can see why it doesn't load. Can you please check the Digital Signature for this file ?
Addon Manager\couatl64\couatl64_P3D.exe
Right-click on it, select Properties->Digital signature, and check if it's valid, and its date/time.
-
Virtuali sagl - SHA1 TUESDAY 22. SEPTEMBER is the signature on my pc.
Thor
-
That seems right. Could you please run the Live Update once again ?
-
Yes, i did, but still no luck.
-
I'm sure the problem is related to your cloudflare node: you are not getting all the files for some reason. Place the attached file in this folder ( when the sim is NOT running )
Addon Manager\couatl\common
overwrite the one that is already there and start the sim.
-
Sorry for reporting it did not help.
-
I managed to shift Addon Manager\couatl64\couatl64_P3D.exe
to Addon Manager\couatl\couatl.exe, now it`s working :)
Thor
-
I managed to shift Addon Manager\couatl64\couatl64_P3D.exe
to Addon Manager\couatl\couatl.exe, now it`s working :)
Do you mean you edited the add-on.xml file to point to the 32 bit version ? That could work of course, that's why we suggested to do that in the release notes in case of problems. But, the thing is, now we never know what your problem really was. Were you still gettin that SAME error, even after using the .PYE file I attached ?
-
Hello Umberto,
now I've changed the _init_.pye with your perviously attached version.
Additionally I've changed the addon.xml back to the 64-bit couatl executable.
The menu entries of couatl and gsx are now shown and obviously working.
Thanks,
Joerg
-
now I've changed the _init_.pye with your perviously attached version.
That seems to indicate your problem must have been caused by your local Cloudflare node ( there are more than 200 ) wasn't updated with the latest file, because the file I posted is exactly the same we uploaded with the update, so it should have been replicated automatically over the cloudflare network and, for some reason, your local node didn't get it, sometimes it happens after an update, we tried to report it to Cloudflare but, usually, by the time they reply, the file gets eventually updated anyway.
The problem is, if we didn't use Cloudflare caching, it would be impossible to get updates on release day, because of thousands of users downloading from a single server at the same time so, with slowdowns and timeouts, the chance to get the wrong files would be even higher, and everything would be much slower, assuming it will even work.
Instead, with Cloudflare we have very fast downloads for everybody, since users will download from their own local node, but we must live with some nodes not getting the latest file at the same time as the majority. It's likely the correct file should be online everywhere now.
-
Yes, i edited the add-on.xml file to point to the 32 bit version (didn`t manage the first time i tried).
I did use the pty file from you, but it didn`t make any difference.
Thanks for helping.
Thor
-
Hello Thorn, can you please give me a simple instructions how to change directory path? I’m not a computer wizard. I’m using Wins 10 and P3DV4. Thanks.