pink catering logos

[ashun]

After the update, all logos on catering vehicles as well as pushback truck are pink.  I tried to update by checking. Still no change.

[virtuali]

Already discussed and answered here:

https://www.fsdreamteam.com/forum/index.php/topic,33280.msg208942.html#msg208942

- The installer and the update is fine, there are no textures missing from the update. Users have been testing this version /TEST channel for almost a month now.

- If you are missing textures now, it’s because it takes time to update many thousands of updates files on the whole network of 270+ servers in the Cloudflare CDN, so your node will get the files later.

- If you don’t want to wait, Uninstalling and Reinstalling GSX Pro from the FSDT Installer will work, you won’t lose your airport/airplane profiles or your activation.

[whiggy]

After the update, all logos on catering vehicles as well as pushback truck are pink.  I tried to update by checking. Still no change.

I reinstalled complete GSX + FSDT Installer.
This solved the problem.

[davidcherrie]

Oh look at that? Another update deployment issue due to your CDN. Maybe push updates to your CDN well before releasing them to ensure things like this don't happen so that users don't have to download multiple times to fix issues an incomplete download causes?

[virtuali]

Oh look at that? Another update deployment issue due to your CDN. Maybe push updates to your CDN well before releasing them to ensure things like this don't happen so that users don't have to download multiple times to fix issues an incomplete download causes?

OF COURSE the updates pushed on the CDN in advance and, while there's an update in progress, there's a BLOCK to prevent users to update until the update is completed. Then, BEFORE removing the block, the update is tested. And no, I'm not testing just my local node: I do several tests using a VPN to connect to various random nodes in difference continents, to check the update has been registered. But you can't expect I could possibly test ALL 270 nodes in Cloudflare. Last update we had an user in Australia reporting a problem, he's from Melbourne, so I tried ALL nodes in Australia and, guess what, they were ALL fine EXCEPT the Melbourne one!

The larger the update is, the more time it takes for all nodes to replicate. Without even knowing how Cloudflare works, you might say "can't you just wait more time to remove the Update block ?", which is basically another way of saying "push updates to your CDN well before releasing them".

Well, that wouldn't work because, it's not as if Cloudflare replicates files automatically "just" because we purge them from the CDN. If nobody from a certain node doesn't request a file, the replication won't even start: it takes somebody requesting a file to have Cloudflare starting to update that local node.

And of course, because Cloudflare is careful not to crash OUR server, it doesn't try to do too much transfers at the same time.

We have this update online on the /TEST channel for over a month. NOBODY ever reported a "CDN problem", and we released like 5-10 updates PER DAY ? And you know why ? It's because way less people was on the /TEST channel compared to the official release, like 1% of the normal users, so replication was very quick, because Cloudflare would immediately get the update file from our origin server as soon somebody request it, when thousands of users make requests all at the same time, Cloudflare obviously staggers requests in order to be sure it's not crashing our server.

Really, after what happened to MICROSOFT with the release of MSFS 2024, where users were even PREVENTED to complete the installation for days ( not just "pink" textures" ), you are still insisting that CDN issues don't happen in real life ? And yes, there is a difference: Microsoft OWN the CDN, so you CAN say "your CDN" in that case.

[davidcherrie]

If this is such a widespread problem, then why do no other developers issue updates that have problems like this? I don't download aircraft, scenery and find big chunks of it missing because the CDN hasn't populated. Why is this not a widespread problem in the tech world that I see on a daily basis but only a problem that is ever with your software that you then blame on everyone else?

[virtuali]

If this is such a widespread problem, then why do no other developers issue updates that have problems like this?

Microsoft MSFS 2024 release day

Why is this not a widespread problem in the tech world that I see on a daily basis

How many other MSFS add-ons are made of ten of thousands of files that must be synchronized on a large CDN ? Let's do some actual counting:

- GSX pro package = 10GB 55.661 files in 43.399 folders

- GSX world package = 4.08GB in 22.886 files and 16.611 folders

- GSX jetways package - 169 MB in 16.000 files and 15.128 folders

- Couatl/GSX folder - 348MB in 3.247 files

So, we have about 100K files, even not counting other smaller folders.


Some comparison from other products:

- Fenix A320 = 1475 files

- IniBuilds A350 - 3921 file

- PMDG 777er - 1875 files.



There's only one I can think of being so large, and it's MSFS itself. How good was the 2024 release again ?

but only a problem that is ever with your software that you then blame on everyone else?

"blame" ? I'm not "blaming" anybody of this problem, it's just the same as if when you use a slow DNS and you see an outdated page of a website, is EXPLAINING why this happens means "blaming" ?

So yes, now I AM blaming you, but only because you refuse to accept the explanation.

[davidcherrie]

Comparing GSX to the complexities of MFS2020 or 2024 is like the difference between driving to the supermarket than landing on the moon.

Why is every update from Asobo not problematic then? So many world updates, sim updates, airport products that are being added daily. Why do they not have missing files?

Also as far as I am aware, you're sending everything in very large packets so why are individual files missing instead of the entire packet corrupt or missing?

I've designed countless broadcast packages for international sporting events like the Olympics with tens of thousands of files that need to be distributed to 20-30 venues. I've never had issues sending that amount of data (video files, not just images) and then when it comes to needing them they fail to load. However I get it every time with GSX. Am I just that unfortunate living in Australia?

[virtuali]

Comparing GSX to the complexities of MFS2020 or 2024 is like the difference between driving to the supermarket than landing on the moon.

This sentence is trying to be clever, but it's just wrong on so many aspect. A CDN doesnì't obviously know how much "complex" a software is. But it's surely affected by the sheer NUMBER of files.

Why is every update from Asobo not problematic then? So many world updates, sim updates, airport products that are being added daily. Why do they not have missing files?

I would EXPECT that, considering the own the whole network! You still haven't explained

Also as far as I am aware, you're sending everything in very large packets so why are individual files missing instead of the entire packet corrupt or missing?

We are using BOTH approaches, precisely so we are not as much affected by replication issues AS IF we were "just" sending individual files. We have both .ZIP files containing many small files and also individual files, not only during a clean uninstall, but also during an update. For example, all small files are packed into individual .ZIP files, so it will be less of a burden to Cloudflare sync process, because we can group many of them.

And that is precisely how Uninstalling/Reinstalling will fix this DURING THE FIRST HOURS/DAYS (obviously depending on location): for this release, we updated the base .ZIP files to start directly from 3.5.3, which means it's impossible for anybody to get an outdated version, since that file has never been seen on the internet before.

Of course, a "simpler" solution would be doing for EVERY update. That is, publishing a new set of 6-7GB files for every single little update.

Seems clever ? It's not, because:

- Those with a smaller connection would still have to download a new package every time, for every update, taking hours.

- Those with a metered connection will be screwed.

- Those with a monthly data cap will be screwed as well.

But that's not the point. The point is, again, your attitude. You said in another post you don't WANT explanations (you called them "excuses") so why you are continuing arguing, and why I'm even replying ?

[davidcherrie]

I don’t want explanations. When I am asking why, it is rhetorical. You should be asking and explaining this to Cloudflare as to why you have such dissatisfied customers reporting so many problems every time you issue an update because not all of that update is on their CDN. If it isn’t then you should be delaying your updates until you confirm that all CDNs have all files.

Every time I update GSX, it downloads a huge portion of data of what I presume is files that I already have. What I would do if I was you is be separating all your packages into smaller packages so that every time you do an update, a large library doesn’t need to be sent to your CDN and then redownloaded because you changed one file. Doing updates as packages would be much better so users don’t need to download a package they already have because you have added new ones to it thus deleting the ones that already exist if they haven’t been uploaded to your CDN.

[virtuali]

I don’t want explanations. When I am asking why, it is rhetorical.

Alright, so it was rhetorical, just for the sake of trolling.

You should be asking and explaining this to Cloudflare as to why you have such dissatisfied customers reporting so many problems every time you issue an update because not all of that update is on their CDN. If it isn’t then you should be delaying your updates until you confirm that all CDNs have all files.

Now you are assuming we never did that ? What's wrong with your continuing assumptions without knowing any facts. Even if you don't want explanations, I'll give them anyway, because somebody ELSE might found them useful.

OF COURSE we reached Cloudflare several times, over the years. The problem is, out the in the real world, support works like every support, so, they take 4-5 business days to reply to a Ticket, if there's weekend, they don't reply and, by the time they answer, the issue has already fixed itself, because of course Cloudflare server replication WORKS, it just need some time, if there are many updated files.

So, whenever we get an answer from Cloudflare, they invariably reply "It doesn't happen here, we cannot replicate it", and IT'S TRUE, because in a few days, every node would surely have completed replicating.

Unfortunately, we only have a standard Business account with Cloudflare, the only way to get a faster/dedicated support, is for Enterprise contracts starting at 5000$/month. We cannot increase all prices JUST because after an update *some* files might be missing for a while.

[davidcherrie]

Ahh so you get the inspiration for your support from Cloudflare. Do you not have betas? Can’t you just wait a few days before releasing updates so you’re 100% sure all the update has reached every CDN?

Wouldn’t that save you time from replying to all these bug reports about things not working because they have an incomplete update? What is the rush to have the update instantly released?

[virtuali]

Ahh so you get the inspiration for your support from Cloudflare. Do you not have betas?

Now you are funny: you haven't even understood the irony. The difference is that I accept that as normal, and I don't go around making a fool of myself trying to teach Cloudflare how they are bad at their job and how they should handle support.

Can’t you just wait a few days before releasing updates so you’re 100% sure all the update has reached every CDN?

This update has been available for EVERYBODY to try for several weeks, on the TEST channel. Nobody reported any problems with it. Obviously because the amount of people trying the TEST channel is a tiny fraction of the whole user base, so Cloudflare replication works better, when there are just a few requests.

Wouldn’t that save you time from replying to all these bug reports about things not working because they have an incomplete update? What is the rush to have the update instantly released?

So now you are suggesting we release an update, then prevent everybody from updating for 2-3 days, JUST to wait to all nodes to be replicated. That's asinine.

[davidcherrie]

Hang on, so these files have been available for weeks on your CDN for testing, yet when it got released, the files are still not on your CDN?

Yes, I am suggesting you wait until all files are uploaded to your CDNs before allowing people to download them or redirect them to CDNs that do have all the files. That's a common practice... not to download incomplete updates.

When I send files, I don't give people the link to download them until I know they are uploaded, otherwise I'll get people prematurely going to link and not receive all the files, email me and complain that they can't see the files, and then I spend my time telling them to wait and keep looking until they are.

[virtuali]

Hang on, so these files have been available for weeks on your CDN for testing, yet when it got released, the files are still not on your CDN?

It's NOT our CDN!!!

Yes, I am suggesting you wait until all files are uploaded to your CDNs before allowing people to download them or redirect them to CDNs that do have all the files. That's a common practice... not to download incomplete updates.

"You wait", means forcing EVERYBODY to wait, even those for which their local node is fully updated, which is wrong as well. Lots of users never had any issues to begin with: their node was already up MINUTES after the released.

When I send files, I don't give people the link to download them until I know they are uploaded, otherwise I'll get people prematurely going to link and not receive all the files, email me and complain that they can't see the files, and then I spend my time telling them to wait and keep looking until they are.

Because you normally send 100K files to thousands of users across the world.