The latest Zwift update is now available on all platforms.
Not sure if your Zwift install is up-to-date? Here’s how to check >
This update is just a patch fixing a few bugs. We don’t always post when Zwift releases these minor updates, but we thought this one was post-worthy.
Here’s what Zwift says is fixed in this release:
- Fixed a bug that caused the Canyon Speedmax CF SLX frame to have an incorrect aero rating.
The updated frame is the new fastest TT frame in game, and the best all-arounder as well! Read our speed test notes > - Fixed a bug with some Tacx trainers which would cause riders to move at incorrect speeds.
This was a power curve bug for some low-end wheel-on trainers – see our post about it here. - Fixed a bug that caused some ANT+ connection diagnostic data to be missing from the log.txt file.
This made Zwiftalizer unusable temporarily, but hopefully we’re back in business! - Fixed a pairing issue with USB Elite Real Axiom trainers.
- Fixed a crash when Zwifters would send a very long chat message in game.
Word is there are still problems with ride leaders using AutoHotKey to send messages – if the keystroke rate is too fast, it crashes the Zwift game.
See/discuss release notes on Zwift’s forum >
Note: Zwift recently changed the way they display the game version, for the purposes of clarity. Starting with this post we’ll be using the same version + build number formatting moving forward, where each release has a version (1.11.0) plus a build number for that version (65416).
If you spotted any other changes in yesterday’s update, please comment below!
Thank goodness, at least a partial fix for the chat crash. My own testing (holding down a key until maxing the character limit and beyond, yes…very scientific) no longer crashes the game to desktop 50% of the time, so I’m hoping that’s a wrap. I see your side note though so perhaps will keep chat messages on the shorter side for now to be sure…
Curious how to wrong parameters of the Canyon TT bike can be overlooked in testing??
@Aristos, the testing was performed by us Zwift users after the update was rolled out! We are the QA/QC team. Why waste budget on internal testing when you can just have the users test it live?🤑
Wait a minute, Zwift finally changed from being Zwift 1.0.xxxxx to Zwift 1.11?!
For a game that’s been in v1.0 for so long, is it a coincidence this version numbering changed at the same time as the save without quitting option came in? Or am I reading too much into it?
I think the previous Bugdate was 1.10 which just before the Return to Home function got rolled out. The Bugdate QC group, aka All of The Zwift Users, are hopeful 1.11.00 doesn’t introduce other problems.
I must have missed that in the last update. The point I’m wondering about is how significant was the last update for Zwift – how much of the platform did they rebuild to think “this update is so significant, it’s the first one ever that we’re going to say is no longer v1.0”?
I always felt that if they’d been able to do save without quitting with v1.0, they would have done it long ago, so it’s interesting that the numbering change came when that came in. But as I say, I could be reading too much into it.
Did the latest patch just break the F10 photo upload that was finally fixed last week? It’s taking an awful long time for my photo to appear on Strava.
Update: It appeared 3 hours later
Just checked my last ride for ANT+ performance on Zwiftalizer. Nice to see that diagnostic feature is available again.
My zwift crashed whilst giving out ride on’s. Hope they fixed that as well.
Also – when are we getting HED Wheels.? 🤔 😁
After todays uppgrade on Zwift my latest rounds don´t upload to Todays plan. However it works to garmin…….. Any fault issues?????”
….and it seems to some kind of corrupted parts in the .fit file that should be read by Todays Plan……
VERSIÓN 1.11.0 (65416) ??? this is a big jump for a squirrel,
I still see version 1.0.65416 in my launcher.
Those are the same version – just two different ways of writing it. Confusing, I know! The build number is the important part.
Is anyone else having problems with the new update? On multiple occasions my avatar stops. I stay in the game but I can’t get going again without logging out and logging back in again. I’m using a Wahoo Kickr.
I saw a rider instantly stop and then slowly start again in front of me, when I got to the same position in the road the same thing happened to me. Didn’t have to log out but weird nonetheless
I can no longer stream Netflix on my PC while running Zwift. Did resource usage become higher? My laptop isn’t a high powered gaming rig, but it’s no slouch either.