Tried updating to 1.75 in Australia, and even when I updated from the website, it just downloaded 1.74.2 again. Are you unable to update from the website? Ahead of staged rollouts? Seems a bit antiqued to geo lock people out of self service updates, when it is physically available for others
I think they have rolled back the update due to crashing problems.
"UPDATE October 1
We detected a potential game crash in our telemetry and have paused the release of version 1.75.0 while we investigate.
Zwifters who received the 1.75.0 update will be automatically moved back to the previous 1.74.2 release.
Android users who received the 1.75.0 update will see their new game version as 1.75.1, which is identical to 1.74.2."
Folk complain when it’s a staged rollout and yet this is a perfect example of why that’s a good policy.
5 Likes
Phased rollouts go to a percentage of randomly selected machines of each type, so it never matters where you are, and if you download the latest launcher from the website that doesn’t mean it will install the latest release when the phased rollout is in progress. But if you have multiple devices capable of running the game, you may get the update on one but not others so sometimes that’s a way to speed up access if a release is in progress.
Not getting an update that doesn’t work isn’t good, it’s just not bad.
Whereas not getting an update that does work is bad.
So you can’t proffer it as a win - it’s just not a loss - and yet the people who had an update and it crashed or had performance issues without any choice in the matter lost too.
It’s like popping up when an airplane crashes and telling everyone “This is why you shouldn’t complain when the airline oversells seats”
Ultimately, if the servers allow different versions to co-exist then there’s no reason not to let people try a new version when they want or switch back if they discover a problem. Perhaps with some limits - maybe there’s a point where you say “You have to be on at least 1.74.2”
None of this stuff is new either, people have been releasing betas and letting people download different versions etc since it was possible to download updates.
It would be good to trust users to have a little bit of control over it, especially since they may be in a population affected by a bug and can’t ride if they can’t run the version with the fix
I think they already have that capability, at least on some platforms?
Phased rollouts are, and have been, a major part of software distribution since I was a lad.
So has syphilis. Doesn’t mean it’s a good thing.
There’s a good reason not to force everyone onto a new version that you haven’t tested especially when their support staff can barely keep place with all the broken and pieces missing zwift rides - but that’s not the same as not letting people upgrade and downgrade through choice.
Bottom line this wasn’t a good example of why phased rollouts are a good policy. It was just a bad software upgrade that had to be rolled back.
for most updates does it really matter when you get it… I mean the scrolling names on the screen instead of being truncated is great and all… but I wasn’t holding my breath waiting for this huge improvement…
When new roads are released, then I get the frustration from people who have to wait… but that happens like once or twice a year if we are lucky… the rest of the updates are usually pretty boring.
That’s another thing to improve then.
It’s odd how people think “Updates are boring so it doesn’t matter if you get them or not” not “Updates should be interesting and it should be possible to download an install them”