Products Support > GSX Support FSX/P3D

Problem with GSX 2.9.4 | Only works once after LiveUpdate

<< < (18/20) > >>

F4RIO:

--- Quote from: virtuali on September 09, 2021, 06:20:41 pm ---
--- Quote from: F4RIO on September 09, 2021, 06:02:34 pm ---Installed the Sept 9 update and now all my FSDT scenery software is running in Trial Mode. The Add-On Manager is present but the Couatl scripting engine is not running, and so the Register Serial function does not work, and of course I cannot update the scenery cache.
--- End quote ---

There has been two updates today so, please be sure you run the updater again, to get the very latest version, which always automatically recreates the cache at each start.

--- End quote ---

I ran FSDT Updater twice and Couatl Settings, Couatl Live Update and the GSX add-on menu items are now available. The are still a number of significant problems.

I have KORD/KJFK/KLAX/GSX2 installed with status installed and active.

None of them work correctly: scenery partially/completely missing, GSX2 just doesn't work, Couatl will not restart/rebuild.

I also get messages saying products are not activated (on P3DV5 startup) when they show as activated within the add-on manager.

I have no idea what to do.

Again, prior to the September updates all were working perfectly.

virtuali:

--- Quote from: F4RIO on September 09, 2021, 09:12:03 pm ---I have KORD/KJFK/KLAX/GSX2 installed with status installed and active.
--- End quote ---

If they are flagged as Active, it means everything is working from the software side.


--- Quote ---None of them work correctly: scenery partially/completely missing, GSX2 just doesn't work, Couatl will not restart/rebuild.
--- End quote ---

Couatl will always restart and rebuild, if you have the latest update installed.


--- Quote ---I also get messages saying products are not activated (on P3DV5 startup) when they show as activated within the add-on manager.
--- End quote ---

Do they showed as Activated in a PREVIOUS session, but you are getting those messages on another startup of the sim ? This is consistent with the problems which were happening on our *first* release of this update, because Couatl couldn't read an already made airport cache and in that case, it didn't closed correctly, so it didn't work on the next startup of the sim.

Even when we HAD this problem, it was always fixed by removing the airport cache before each start but now, with the current update, is no longer required, since the cache will always be rebuild in any case.

So, again, from your description of the problem, it really seems you don't have the latest update. As I've said in previous posts you can check the timestamp of digital signature of the bglmanx65.dll, to be sure you have the latest version. It must be today, because that's what refresh the cache rebuilding at each start.

F4RIO:
The problem appears resolved. Two successive starts of P3DV5 with normal FSDT scenery behavior. Puzzling.

1. You were correct when you asked about active on startup and not on the next startup.
2. The timestamp on bglmanx65.dll is Sept 9 on my machine (after 4 FSDT update runs).
3. After a computer restart, the problem is fixed.

Thank you

virtuali:

--- Quote from: F4RIO on September 09, 2021, 10:02:16 pm ---2. The timestamp on bglmanx65.dll is Sept 9 on my machine (after 4 FSDT update [runs).
--- End quote ---

You mean you tried 3 times, and you were always getting the older version ? That seems to indicate a delay of your local Cloudflare node getting the latest files. There are 260+ nodes so, I guess it might take some time to propagate all changes through all nodes, surely is not immediate.

If that's the problem, getting the latest file was the thing that fixed it, because with the previous version, you had to manually remove the airport cache before each start, which was the temporary fix that was suggested in this thread, before this latest fix.

jiequinn:
I am now faced with yet another error, this time when trying to amend my aircraft config or by selecting reset position its causing the error message pictured below.

I have attached the log also. Any help would be greatly appreciated I've spent all day trying to fix this doing various restarts and updates but nothing seems to work.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version