Recently the community of people I use Zwift with have noticed a potentially new bug. We stream and ride together often. We have noticed a new issue where after teleporting to ride with a friend, what we each see happening on screen is out of sync.
As an example, I was cycling with a friend recently trying to do a vEverest attempt, during the ride I was seeing myself ahead of the other player, and he was seeing himself ahead of me. Multiple people in our community have noticed this recently. It is not an issue that we have previously encountered.
Yeah, I noticed this issue as well. At one point, the desync created a 40 meter discrepancy (about 10 seconds at our pace up radio tower) between me and the other person.
Maybe this is related to a recently added feature which you can notice in Zwift log, āDonut Fail-Safe V2ā. Check your log for messages like Donut fail-safe for player xxx took xxx ms | Distance increased. Apparently now it can take longer to sync riders.
It seems to be happening most noticeably during teleporting to other riders and/or U-turns for hill repeats. Would be tragic for any competitive sprints/race finishes.
If Zwift is able to reproduce the issue internally, they should be able to indentify the cause and fix, without our need to troubleshoot the problem. This is interesting though.
I started noticing this desync issue yesterday during a friendās veverest attempt. When comparing both our livestreams, it appears that the desync didnāt happen immediately after the warp, but instead happened after a rep of radio tower. We U-turned at the top, then again at the bottom. It was at this point that the game desynched us. When comparing VODs, I was now 10m off from my friend. This gap continued to grow during this next rep until about 28-30m and we would only resync at the top when we U-turned to go back down the hill. You can even see some level of rider āteleportingā upon execution of the U-turn.
My experince was similar to what @Aaron_Pookie is describing. It was during a seperate vEverest attempt up the grade however. I am on the latest build of Windows 10 currently. I am not sure the exact Zwift version at the time, it would have been a week or two ago. I think the bug should be reproducable in Zwifts lab using two Windows clients.
I decided to report this because when it happened to me I thought it was an isolated occurence, and I chopped it up lag, or something else. However then other people in our community started reporting the same behaviour.
My teammates and I are struggling with this one on the WTRL TTTās starting in June as well.
Oddly, not all of them (rather, they see those of us experiencing the issues, but donāt seem to have it themselves), but one other in particular as well, who I do know is on Windows. As for the others not seeing these desyncs, Iāll have to ask them tomorrow.
For me Iād be hanging out the back like 10-20m, while on my screen Iām the one pullingā¦ and other times, Iāll be pulling and they might see it, but Iām not providing any draft somehow?
Things ebb and flow in terms of syncing, but itās as broken as much as itās not broken, and for the TTTsā¦ well, simply putā¦ makes them not possible (and understandably not enjoyable one bit) when you donāt have accurate positions of your teammates.
Something with the netcode has absolutely been screwed with this month.
I have not received the new update as of yet, but, definitely want to agree that it started to appear after 1.67
Happy to share all of my logs if itās helpful lol! Iāve got plenty now
Was still happening today after getting this weekās 1.68 update.
I will also state that starting ā¦ Monday I think? the āconnection disconnectedā is only showing temporary, and I can not send messages for a few seconds; but not a total loss of connection like I was getting last week, where Iād literally lose visibility of everyone for anywhere from 5-20 minutes.
@markandrewj
The fix for this was enabled server-side after last weekās release of game version 1.69. It was technically not a fix on the game client, so we didnāt put it in the release notes.
Please let us know if this has been resolved, and definitely let us know if it hasnāt.
