FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: smx55 on October 13, 2017, 06:12:58 pm
-
GSX has been disable on this airport by user setting....I keep getting this after p3d 4.1 update
-
The update cannot cause this. You must have selected the "Disable" option from the GSX menu (the one under the "Addons" menu ). Just select "Enable" to re-enable it.
-
It is not disable, I disable it and re-enable with no luck. This is a new install after update no setting where touched
-
I saw the same thing earlier today after running Live Update. Running Live Update a second time has cured the issue for me.
-
The Live Update re-enable GSX exactly as if you were doing it from the menu. It resets the disable = 1 flag in the [GSX] section of the Couatladdons.ini file, back to 0, which is the default.
-
There was no option in the menu to enable, only to disable. In fact, all the GSX menu options were present except for "Customize airport positions." Disabling and re-enabling didn't fix it. During the second Live Update, a large number of files was updated, which for whichever reason did not occur during my first Live Update earlier today.
-
I saw the same thing earlier today after running Live Update. Running Live Update a second time has cured the issue for me.
Thanks that was the only resolution to work here.
-
During the second Live Update, a large number of files was updated, which for whichever reason did not occur during my first Live Update earlier today.
It's normal that you would see a large number of updated GSX files that didn't arrive earlier: we just updated it about an hour ago, to support the newly released KSDF.
What's not normal is that you didn't had the "Enable" option. The only possible explanation for this, is that you installed something exactly in the middle of the update *while* we were uploading, so you might have had a mix-up of old/new files for a while, which the 2nd Live Update fixed, when the server was updated completely.
-
What's not normal is that you didn't had the "Enable" option. The only possible explanation for this, is that you installed something exactly in the middle of the update *while* we were uploading, so you might have had a mix-up of old/new files for a while, which the 2nd Live Update fixed, when the server was updated completely.
That was my guess: that the first Live Update was incomplete because you were still in the process of uploading files. In any event, all's well now. :)
-
I saw the same thing earlier today after running Live Update. Running Live Update a second time has cured the issue for me.
That did the trick! Thanks
-
I just got this, had to run auto update twice also
-
Yep, same here as well, and I was not doing anything else during the update process. Running Live Update a second time resolved the issue.
So, clearly there's something wrong with Live Update.
-
So, clearly there's something wrong with Live Update.
There's nothing "wrong" with the Live Update. It's just a matter of how such server-based system works.
In order to make it as fast as possible, it originally sourced on Amazon AWS, but that's just the start.
To make it even faster for everybody, we have the Cloudflare Distribution Network on top of it, which is a large array of servers, all automatically cloned, distributed all over the world, in order to be sure that every user will always get the fastest download possible, from the Cloudflare node closest to him:
https://www.cloudflare.com/network/
Counting all our products, we have ten of thousands of files (our Simobjects folder contains more than 10.000 files...), so it's really not possible that, when some file changes, it could be *immediately* replicated over a network of 118 servers, and at the same time for everybody.
Because of the large update we had with GSX and KSDF, it's possible that someone might have gotten mixed-up files, because his own Cloudflare node was still replicating the "master" server on Amazon.
That explains why running the Live Update again, fixed the issue, because that node eventually got synced completely, so the Live Update was able to realize there were still files that had to be updated.
If we tried to run on a single server, file updates would be immediate, but it will just crash each time we would make a big release, exactly as it happened when we released KMEM, which brought down our old server to its knees, so people got corrupted files, which resulted in crashes in the sim.
So, we changed everything for KCLT, and used a way more powerful infrastructure, simply because we outgrew the old one.
-
How do you explain that I experienced the exact same problem, but I didn't run live updater until 10/15/17 after about 7:30 p.m. US EDT? I think the posts above are correct, something about the structure of your current updates REQUIRES a second pass of live update... after first pass of live update I got "GSX is not available at this airport because of user settings."
-
How do you explain that I experienced the exact same problem, but I didn't run live updater until 10/15/17 after about 7:30 p.m. US EDT?
That your local Cloudflare node, of the 118, was later than others getting the latest files.
I think the posts above are correct, something about the structure of your current updates REQUIRES a second pass of live update...
No, it doesn't. If it did, we would have hundreds of reports of this by now. Instead, we have only very few of them, so it's clearly just those getting a less frequently updated server.
-
You mean to tell me that 2 days after the update was posted, the server network was still not completely updated...wow, is it a dial-up server network?
Are you implying all the files weren't available when I ran 1st pass live update, but 15 minutes later when I ran the second pass, they were magically available? That would mean I have the worst luck of virtually anyone on the planet. 2 days after file post to the network, and I picked the wrong time to update by 15 minutes...do you really expect us to believe that?
I'm not trying to be disrespectful, but have you actually done a file compare on the server nodes to confirm those files weren't available...simple matter of checking file dates.
-
Out of curiosity, I just ran live updater again (3rd) pass, and noticed a couple of files downloaded...so I assume that means after 2 update passes, and almost 3 days after files were posted to your server network, live update is still finding files that weren't available.
SERIOUSLY?
Sounds like it's time for a different server network.
-
You mean to tell me that 2 days after the update was posted, the server network was still not completely updated...wow, is it a dial-up server network?
That's not what I'm telling you, of course. The time it takes to be updated it's quite short, but that doesn't mean every server checks for updates with the same frequency.
The DNS was just an EXAMPLE, this doesn't really have anything to do with DNS, but the Cloudflare network works in a *similar* way.
That would mean I have the worst luck of virtually anyone on the planet. 2 days after file post to the network, and I picked the wrong time to update by 15 minutes...
That's what happened. Which is clearly proven by the fact that, of MANY THOUSANDS of GSX users, only an handful of them reported this problem. If the Live Update really had a "problem", it should have affected everybody, and the forum would have been flooded by reports.
-
Out of curiosity, I just ran live updater again (3rd) pass, and noticed a couple of files downloaded...so I assume that means after 2 update passes, and almost 3 days after files were posted to your server network, live update is still finding files that weren't available.
SERIOUSLY?
No, it simply means that we have posted OTHER updates in the meantime! There were several very minor things and, as usual, we fixed all of them, and we added a couple of more liveries that were requested in other threads.
Are you trying to say now that we shouldn't continually post updates, as soon as issues are reported ?
-
Which is what I expect caused the issue in the first place...some of the files causing this issue were not included in the first post to the server...that's all we needed to know...not that we're idiots that don't know how to use live update, or "all the files were there it was just poor luck for me they hadn't been replicated at my server node.
I would argue the reason thousands haven't seen this problem, is that the files missing did not affect the airports they have used so far. Just so happened KLAS is one for which files were not available.
-
Which is what I expect caused the issue in the first place...some of the files causing this issue were not included in the first post to the server...that's all we needed to know...
No, this is NOT what caused the issue if, with "issue", you are referring to the "GSX has been disabled" error. This could ONLY be caused by a mix-up between old and new files, because your local node didn't got all the files. Are you now trying to say I'm lying to you ?
We posted OTHER updated files after the release to fix OTHER issues, not this one.
not that we're idiots that don't know how to use live update
Nobody said this, you are making this up.
all the files were there it was just poor luck for me they hadn't been replicated at my server node.
All files were there, and it was just poor luck for you they hadn't been replicated at your server node. That's exactly what happened.
I would argue the reason thousands haven't seen this problem, is that the files missing did not affect the airports they have used so far. Just so happened KLAS is one for which files were not available.
Who said it affected only KLAS or the supposedly "unavailable" files belong to KLAS ? The topic is closed.