After four years of Zwift with ups and downs in terms of “stabilty” patches and issues afterwards,
close to the point where I think I´ve had it and it´s time to move on. For two weeks now, half of my rides get corrupted, not uploaded, half of the rides missing, The experience is beyond frustrating and anything I´ve tried and investigated in the logs has not helped. Zwift support answered with 3 prefabbed AI mails, my case was escalated…but nothing happend.
My new computer was running Zwift just fine for a year, till the last patches from Zwift. I first thoght I changed something - new grpahics driver, rolled that back, and tested about everything possible.Thought it was fixed - finished a 200km ride. No issues..but analyzing the log showed: only the strong cpu kept the session alive, it was full of errors. Though the local fit file updated, and I got a complete fit file. No sync. Ride shows on companion, can not be downloaded or viewed - if it can be viewed, the file is corrupted. The latest NVIDIA driver (for 4070 super) makes the issue worse (no rides can be recovered at all) but even with the previous 2025 driver that worked fine till this day, the issues presist. Video functionis turned off, has nothing to do with it. Changing tab to windows makes the issue worse and CAN trigger it.
However, today, no tab changes, video off, old Nvidia driver, everything as it as for the last 15 month. Except for Zwift, with recent updates to the folder structure. Yes, files are created, some are saved, but 50-70% of the rides are now broken.
The “support” that was once very good, is now mostly AI based, ignoring the reported issues - responding with the usual “default” answers (turn off vide, reinstall zwift…and so on). My log findings and the errors are ignored.
Usually part of the game engine will shut down somwhere during the ride after
[22:13:31] GL error GL_INVALID_FRAMEBUFFER_OPERATION[22:13:32] GL error GL_INVALID_FRAMEBUFFER_OPERATION
After that, no more communication with the server
[22:16:11] [ERROR] Curl error: [28] 'Timeout was reached'[22:16:32] [ERROR] Curl error: [56] 'Failure when receiving data from the peer'
The curl errors are braking the ride. There is tons of different errors, and wild error loops that canbe triggered by teleporting or taking a video screenshot. Both things do make the issue worse, but the unability of the engine to recover and write a proper fit file is new (after March updates)