Zwift Update Version 1.60 (127000) Released

Zwift version 1.60 begins its phased rollout today. It’s a minor update with a small Player Highlight upgrade and some priority bug fixes. See details below…

Ride On Bombs + Player Highlight

The new Player Highlight feature was released in the previous update, and today’s release expands the feature to include Ride On bomb highlighting.

Now when you send a Ride On bomb (by pressing the Z-button on Zwift Play or tapping on the Zwift Companion map) the riders receiving Ride Ons from your bomb are temporarily highlighted and an animation shows your bomb dropping.

Here’s what it looks like:

Read more on this forum topic >

Coffee Stop Fixed

The previous update caused some Coffee Stop bugs which made it so riders weren’t able to take Coffee Stops in certain situations. As cyclists, of course the Zwift community rose up in arms against such an injustice, so we’re happy to announce that Zwift reports today’s update should fix any Coffee Stop bugs.

Apple Watch Rollback

The release notes say “Reverted recent Apple Watch updates to address connectivity issues.” Apple Watch users have told us that the previous update seemed to break Watch connectivity with the game, so it’s good to see Zwift has rolled back the latest updates so Watch users can get heart rate into the game and Apple Health.

More Release Notes

Zwift provided notes on additional tweaks and bug fixes in this update:

• The Ride Streak screen now automatically closes itself after a period of time. If you’d like to keep the screen open longer, touch or click anywhere to cancel the timer.
• Fixed an issue where routes with minimum level requirements were not correctly locked in the Route selection screen.
• Fixed an issue that could potentially award The Big Ring route badge after completing a different route.
• Fixed an issue that could cause some rocks to flicker in Watopia.
• Internal changes made to reduce the likelihood of red squares issues.

Discuss this release on Zwift’s forum >

Questions or Comments?

If you spotted any other changes or bugs in the update, please comment below!