Game Update 1.57 [January 2024]

“spaghetti code” is ok, as long as you know what you’re doing! They seem not to know…

How comes that trainer connection is corrupt in 1.57 though there’s no hint in @shooj 's list of changes?
Are the developers playing around without knowledge of their strategy managers? They should have learned by the desasters in the past, e.g. 1.33, that you keep your fingers away from basic functions… well, modifying the graphics engine such that red squares flicker regularly around the avatar seem not to be critical, after a few months it’s now a feature…? :man_shrugging:

How does Zwift’s quality assurance work, if existing? Obviously, it’s hard to guarantee the function of every graphics card of the past 15years, yet Tacx trainers should be really common. Do they run a local test server, with accounts for the QA staff, developers and managers? Ah, with the lack of employees using their own product, they could invite some truely enthusiastic Zwifters to test new features and stability in this secondary virtual world a few days before roll-out on the main servers?

I really like Zwift, its concept; we are running meetups in our circle of friends, everyone paying 15€ each month. Those persistent connection errors and Zwifts reluctance to work on well known basic, non-gaming bugs are really frustrating.

2 android tablets Zwift bricked with 1.57.1, they disconnect every time you try to ride, it could be 5min into a ride, it could be 20min into a ride, you never know. Zwift has become totally unpredictable and useless. There will be no rider on the bike, or your bike will be laying on the road sideways.

Wife and I were in the fondo ride this afternoon, she got 18km in and poof, disconnect, I paired her to my V5 and poof another disconnect. It then bricked my game on Asus laptop(1.56), no connection. I was able to save her ride, but mine I could care less and left at 24.4km.

Was no issue on 1.56 and my tablets did NOT have 1.57. Zwift updated our tablets to 1.57.1

I say, this has been one of the worst releases, is their no one who checks code, or work before it gets released?

On 1.56 rolled back after 1.57. Took a screenshot via companion of my power graph at the end of my ride (please just make this a default capture, and make it the default starred image, or at least an option to do that) and it didn’t show up at all on the save/share screen. I do have it on my phone so I didn’t just forget to take the screenshot or hallucinate that I did. The two auto-taken screenshots were there in the save/share screen.

What’s happening then @shooj or anyone at Zwift?? Over a week since the 1.57 update and it’s all gone very quiet since the roll back?

Maybe we are just going to skip to 1.58 next week??

Hey everyone,

We released a version 1.57.3 patch with some information on a fresh discussion. Let’s pick up this conversation and resume on the new thread, please.

1 Like