Phased rollout for Zwift game version 1.82 begins to Windows / macOS / Android.
Phased rollout to iOS / tvOS begins tomorrow.
Windows, macOS: It’s now easier to exit Zwift with a keyboard or Zwift controller. While on the home screen, press the Escape (Esc) key on your keyboard, or the B button on your Zwift Play or Zwift Ride to see the exit prompt.
Fixed an issue where the workout block countdown chime sound would not play in some cases.
Updated flag icons for some countries.
Fixed an issue that could cause an incorrect flag icon to appear when a Zwifter does not have their country set.
Improved in-workout messaging for workouts in the Sprint, Attacking, and Endurance challenges.
Running: Fixed an issue that caused distance units to only show one decimal place instead of two in the HUD.
Fixed an issue that could cause calories shown in the HUD to overlap with its icon when greater than 10,000 calories.
Improved the visual quality of road art on some devices.
iOS, tvOS: Fixed a crash that could potentially occur after completing multiple workouts in a row.
Android: Fixed an issue that could cause some frames to have invisible seat posts or saddle rails in the Drop Shop.
General stability improvements.
UPDATE January 22
Phased rollout to macOS / Windows / Android continues today.
Phased rollout to iOS / tvOS has begun.
UPDATE January 23
Phased rollout to all platforms is complete.
Do you have questions or issues to report? Please let us know below.
@shooj Is Racing Score pen restriction (eg. someone at 155 signs up for range one 0-160 race, but before race gets a score increase to 162, they cannot join that pen any longer) tied in to racers needing to have v1.81 or higher installed?
If so, can we please ASAP have a game update that prevents people from racing, until they have installed a game update, where pen restriction works?
Numerous examples of pen restrcition not working for Tiny Races for at least the last two weekends.
How about the video screenshots not working when Zwift is not running on the Windows “Main Monitor” it’s been like that since video screenshots were introduced.
Hello! Is the issue of Companion not syncing with Zwift while Zwifting addressed in this update? I’ve seen lots of discussion around this issue but no fixes. I saw forum discussion around this last fall. At the time Zwift blamed the problem on Apple but offered no fix. I’ve seen all sorts of unofficial, (non Zwift) recommendations but none has fixed my issue. And I know many others experience the same problem. I really miss being able to use Companion whole Zwifting. Isn’t ensuring full functionality part of the software validation process? If Zwift has an answer, could you share that? Thanks!!
I haven’t had any issues with the companion connecting and haven’t seen any other reports on the forums. Are you using a mesh network wifi extender or something?
See Zwift Insider Club Forum where others reported issue. Also discussed in September on another Zwift Forum where others experienced same thing. I’ve tried all the usual straightforward possible fixes. Not running mesh network (although IDK what that means LOL)
Hi Paul - Running Sequoia. But if it is a problem with Z not playing nice with Sequoia, it’s Zwift’s problem to fix! I worked in the medical device industry and we had similar issues with Windows all the time but we didn’t just blame Microsoft. Part of robust software validation is identifying problematic hardware/software combinations, making them fail, and testing again after the software is revised to address known issues.