FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Pirateinparadise on November 06, 2023, 02:08:06 pm
-
Most GSX updates take no longer than a couple of minutes. 2.8.3 has been running for over 30 minutes and the progress bar is only at 23%.
Is 2.8.3 a gigantic update or am I just connected to a slow Cloudfare node?
-
I have to agree, painfully slow at this time, updating for over an hour, and a long way to go.
-
As already discussed, other times, each time there's an update, we use the Release Notes as signal to users it's safe to update. If you don't see the Release Notes yet, it means it's not safe to update, because we are still uploading and, if you do that, you'll end up with a mix-match of old and new files, causing all sort of issues, and you'll have to update again.
So, always wait for the Release notes before updating.
The reason why it's taking a long time, is precisely because you started the update before it was safe to do so.
It's quite complex to explain but, in brief, it's caused by the fact in order to speed up the update of many small files, those are grouped into .ZIP files, but they must match the small files they are related to, which can only happen after the upload is completed so, what is taking so long in your case, is not the update itself, but the small files being "downgraded" to the previous version, because they are not coherent with their grouped and ZIPed version, because the upload is not completed.
It's not a matter of "just" uploading, all updated files must be individually purged from the Cloudflare cache as well.
And if you do it in the middle of an upload, not even all of them would be downgraded so, I really can't tell you which problems you might have, most likely missing textures and/or pink objects, but I guess stopping now or waiting won't make much difference.
Just wait for the release notes to come out, and then update again, that's the only thing that is really safe to do.
-
I never knew that.
I fire up the installer before I fly every time. If I see a higher version as "the latest", I click update. THEN I read the release notes...
Now I know better.
-
I'm sorry but that isn't really a good thing!
How about your software not show a later version until it is ready go! Why on earth should we be hunting down Release notes when the software says there is an update! What kind of madness is this? Yes but no but.... Come on! Do better than this. Its not right. Imagine if Windows Update did this!
You must be able to tell your updater not to show updates until it is ready to download?
-
Every release i read before the changelog.
Today i press update before read the changlog.
After some time i stop the installation. the installation was not ready.
is now my gsx chrashed or is a start from the installer help me
to repair all bad things. The version 2.8.3 is shown in the top of gsx. the installation is stopt by me. :'(
Thanks Frank
-
I was just about to post about the same thing but realize I'm late to the party.
Like someone else suggested, having FSDT Live Update announce there's a new version and offer you to update before the update is ready...seriously...
Have that madness addressed sooner rather than later and luckily I have a proper system image backup I'll be able to restore. Since I like others did the "mistake" to trust the update notification I was given.
-
Why is there no OFFLINE installer for the latest updates - 06 Nov 2.8.3
-
too long update also for me...seems it can't download some files
-
well, its 8:33 am PT 11/6/2023 and its still very slow to update . I keep getting timeouts . And the whole website is very slow.
-
I noticed the same thing, how also this website is very slow responding.
I just went back to my last backup before I messed up my GSX by trying to apply the latest version and will stay on this version until we have a green light in here from Umberto.
-
Why is there no OFFLINE installer for the latest updates - 06 Nov 2.8.3
I tried to uninstall and use the install the offline version from 10/23 to get back to where I started but it did not work. I somehow ended up with version 2.7.6 installed. No idea why...
I'm gonna uninstall again and wait for the release notes to change.
-
Mine has been running for 6 hours and still hasn't finished. I'm re-running it. Brutal slow. It's extremely irritating as now GSX is broken as some files aren't on the server or the mirror. 🙄
-
Yeah and now server is closed down due to service.
-
Why are you still reporting the server being slow? I already explained why it is like that, I'll repeat it again:
As already discussed, other times, each time there's an update, we use the Release Notes as signal to users it's safe to update. If you don't see the Release Notes yet, it means it's not safe to update, because we are still uploading and, if you do that, you'll end up with a mix-match of old and new files, causing all sort of issues, and you'll have to update again.
So, always wait for the Release notes before updating.
The reason it's taking a long time is precisely because you started the update before it was safe to do so.
It's quite complex to explain but, in brief, it's caused by the fact in order to speed up the update of many small files, those are grouped into .ZIP files, but they must match the small files they are related to, which can only happen after the upload is completed so, what is taking so long in your case, is not the update itself, but the small files being "downgraded" to the previous version, because they are not coherent with their grouped and ZIPed version, because the upload is not completed.
It's not a matter of "just" uploading, all updated files must be individually purged from the Cloudflare cache as well.
And if you do it in the middle of an upload, not even all of them would be downgraded so, I really can't tell you which problems you might have, missing textures and/or pink objects, but I guess stopping now or waiting won't make much difference.
In addition to that, if you start the Update now, a new Updater is online, which will prevent updates if an update is still being deployed, with a clear message alerting that and suggesting coming back later, so it won't happen again that you could start an update before it's ready, with no need to know you had to check the Release Notes first.
-
Been running the update since 7 AM EDT. Just saw this and now understand why its taking a long time. So, I stopped the update. The release notes still indicate the .2 as the latest so, thanks to your explaination, I'll check tomorrow and see if the .3 is ready.
I have a morning routine where I run all my MSFS add-on apps (PMDG, iniBuilds, Contrail, ORBX, FBW, Aerosoft, etc. as well as FSDT installer) so I was not aware of this process. I'll know better now so thanks for the enlightenment. :)
-
This is unexpected. I get a message that says the server is down for maintenance please check later. Doesn't make sense that an update 2.8.3 appears as available AND the UPDATE button is active if there is neither an update nor a server to deliver it. It's 06/2215Z and I've been checking back later every couple of hours since maybe 1600Z.
Nah... it's broke.
-
This is unexpected. I get a message that says the server is down for maintenance please check later. Doesn't make sense that an update 2.8.3 appears as available AND the UPDATE button is active if there is neither an update nor a server to deliver it. It's 06/2215Z and I've been checking back later every couple of hours since maybe 1600Z.
Nah... it's broke.
nah iit ant broke no issues at my end
-
This is unexpected. I get a message that says the server is down for maintenance please check later. Doesn't make sense that an update 2.8.3 appears as available AND the UPDATE button is active if there is neither an update nor a server to deliver it. It's 06/2215Z and I've been checking back later every couple of hours since maybe 1600Z.
Nah... it's broke.
Nothing is "broke", of course and, the message is there precisely to indicate that.
The reason for the message is to prevent users from starting an update when it's not safe to do so (while a new one is still being uploaded), which is an obvious improvement to the previous version, where you were supposed to check the release notes and don't update until you see the updated ones.
NOW, the updater itself is taking care of that, so you are no longer supposed to know that, and you won't risk starting an update when it's not safe to do it.
-
Great you took care of this so quickly!
-
2.8.3 is out now.
-
Worked like a charm 👍
-
Seems like a pretty backward updating system if you release updates in the installer and then we have to go and manually check the release notes (wherever they are) before we can update without breaking GSX.
This is not made very clear in the purchase/install process. Perhaps adding a note to the installer with a link to the release notes to make it clearer would be better as it seems to have affected a lot of others.
Never come across an installer that makes patches available before they're "safe" to download.
-
2.8.3 is out now.
In future, I think your customer base will appreciate a more streamlined update service. When the Installer says there is an update, the vast majority are going to update the software there and then, and then maybe go and look at the release notes. I've have never seen an update release on software in which you need to refer to the changelog to see if its stable before actually downloading the update. However, it's nice to see that users will now be informed that the update is meant to be downloaded at this time!
-
My understanding is Umberto already addressed this odd behavior so shouldn't be a problem going forward.
-
Seems like a pretty backward updating system if you release updates in the installer and then we have to go and manually check the release notes
the vast majority are going to update the software there and then, and then maybe go and look at the release notes.
None of these comments applies to the current version because, quoting from the 2.8.3 release notes:
https://www.fsdreamteam.com/couatl_liveupdate_notes.html
FSDT Installer/Updater Change: When the update server is in maintenance, updates won't be performed, and a message will alert users about this, suggesting to come back later when the update has been completely deployed.
And from my last post as well:
NOW, the updater itself is taking care of that, so you are no longer supposed to know that, and you won't risk starting an update when it's not safe to do it.
-
well..the website is faster...:)
-
well..the website is faster...:)
Noticed this too 🙂
-
It works...now....