FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: pixxel on September 02, 2025, 01:20:59 pm
-
After updating GSX to 3.7.1 (Latest version as of now), it still shows as not updated.
It seems that the culprit is manifest.json located in FSDT\Addon Manager\MSFS\fsdreamteam-gsx-pro\ in which it still says 3.7.0 after updating.
Manually changing to 3.7.1 inside of manifest.json solves the issue.
This is probably a small bug, but nonetheless, i tried updating with installer first, then with live update until i realized what was going on...
-
Hi,
I can confirm this issue. Tried several times to update, GSXPro stayed at 3.7.0!
Edited the manifest.json to 3.7.1 and made a CHECK. Result: set back to 3.7.0!
-
For me the version shown in the manifest.json is 3.7.1.
-
checking today and 3.7.1 stays installed!
-
Seems that they fixed the bug. It would be nice if they confirmed it being fixed here... Anyways, this can be closed now.
-
It will be to do with the CDN. Umberto doesn't wait for all the CDN's to populate before making the update available which is the equivalent of sending a Dropbox link before your large files have finished uploading. The solution is wait 24 hours and then download the update again.
Umberto thinks it is "unfair" to make people wait for an update after he uploads it so that everyone has a good download experience with the CDN he uses but instead download an update that hasn't been uploaded to the server they are downloading it off of yet.
it is an odd problem. I'm experiencing issues where (just these past few days) that 3.7.1 is installed, and the universal installer is telling me 3.7.0 is the latest and I should update. I'm aware of the issue, and just do nothing because I have 3.7.1. A day later, UI reports 3.7.1 is latest and I don't need an update. Then just yesterday, UI reports that 3.7.0 is then the latest. So my question is, if indeed the CDN is taking a while to update, why after a few days does it revert back to an older version?
-
Seems that they fixed the bug. It would be nice if they confirmed it being fixed here... Anyways, this can be closed now.
We haven't fixed anything. Your local cloudflare node was outdated, the one from another user was, the one for a different user was updated slightly after he initially said it wasn't. It was enough waiting, then your local node got the updated file after the previous users, that's it.