Day 2 tour de Zwift: still huge lags!

Hi guys, I know we all used the platform to train but how come you can not provide the necessary technical support to have a smooth event?!? It s my second attempt to a tour de Zwift and I m still facing the big lags issues. Very frustrating especially when all the normal events works smoothly. By when will you guys solve this issue ???

Hi @frederic_desutter

what is your Pc spec?

Did you do other group events in Zwift before?

I did stage 1 today and it was faultless. I believe Zwift have made some changes following reported issues yesterday.

2 Likes

Hi Gerrit,

I m on a Samsung S9+ with the app.
I did 1x smaller event without issue and no problem neither with my training plan.

Would be happy to have the same experience with the tour.

Hope you will improve the situation as it seems others had similar issues.

Thx

I did the standard ride at 6am PST. No hiccups at all. I recall a bit over 1,000 riders.

over 2000 riders on Tue stage 1 A ride around London, no problem on Apple TV 4K with devices connected through iPhone 6 companion app.

as far as i know you can only see 200 riders even though the event is having a lot more riders online.
so as long as you are in the middle of the pack and work forward to the tip of the pack everytime you pass a certain amount of riders you will see progress in front of you (loading more riders) till you are at the tip of the peloton. this is causing lags all the time.

en top of that if the event is very big thousands of riders i encounter frequent lags just because of the size itself … zwift should split the riders limit per event and make simultaenously events possible on different worlds not just Cat. It really is annoying!

The huge rider list (thousands of participants) next to the event is also annoying making watopias common routes feel like a “emigration of nations”

Stage 2 done and no issues

There were issues in the 11am GMT Richmond ride. Only about 1300-1400 riders, whereas typically it’s been the larger events. I did better than in stage 1 (see previous thread), in that I did finish, but my first lap was ruined and my second was lonely. Remarks:

  • People began to complain in the chat as soon as it started, but others were saying that they were having a great ride, so it was uneven
  • I had the usual thing with Zwift time being much slower than real time. I finished eventually in 1h6m of Zwift time, but 1h48m of real time
  • Power and speed readings were as though the ride was normal
  • Everyone else vanished in the first mile. I don’t think they went up the road; they just vanished. After that I only saw occasional riders.
  • Except that, as I struggled to reach the bottom of the climb on lap one, large bunches started to come by. I think they were the faster riders lapping me in real time (but remember that, in Zwift time, I wasn’t slow enough for them to have done that - so which time was Zwift really using?)
  • Numbers of riders were drifting upward to 1400 even then; how could riders be increasing that far in? Later, when many others would have finished, numbers still didn’t go down that far, maybe 1300.
  • When riders were in sight, all the usual nonsense with riderless bikes, riderless wigs, massive bike pile-ups, and at one point someone riding across the lake by the road, approaching the first hill.
  • Finally, approaching the end of lap one, it all suddenly went normal, except that I saw no other riders at all after this point. A whole lap completely alone! The rider table said that there was one person 7 minutes ahead and one 30+ minutes behind, but those were the only two names showing. It did say that there a large number of (unidentified) others.

Overall, it was not a group ride. I did the whole thing alone, but lap one was just plain frustrating. And now, I no longer believe that looking for events with maybe 1000 riders will guarantee a proper ride.

After the first week of the Tour, I’ve noticed that with a little creative planning, you can definitely find events with fewer people. I haven’t had any of the issues people talk about (ever really - in lots of events, tours and group rides - I don’t really race much) but I don’t like the experience when you are riding with 1000+ people.

Doing the routes in reverse order is a great way to guarantee fewer people. I did route c today and we had 700 people instead of nearly 3000 in Route A. Later in the week, Route A will be quieter so I’ll do it then. Similarly, the 10am EST slot has been really busy while the 11am EST slot has had a fraction of the folks.

Little things like that can make a big difference.

I did the 8 am cst tdz stage 2 A ride. Lots of crashes big time lags and didn’t work normally until about half way through second lap. I did a warm up prior to ride and stayed in Richmond after stage 2. Both of those rides were normal. Talked to another participant who used Apple TV for his setup and his ride was fiuh[quote=“David_Rossall, post:9, topic:525207, full:true”]
There were issues in the 11am GMT Richmond ride. Only about 1300-1400 riders, whereas typically it’s been the larger events. I did better than in stage 1 (see previous thread), in that I did finish, but my first lap was ruined and my second was lonely. Remarks:

  • People began to complain in the chat as soon as it started, but others were saying that they were having a great ride, so it was uneven
  • I had the usual thing with Zwift time being much slower than real time. I finished eventually in 1h6m of Zwift time, but 1h48m of real time
  • Power and speed readings were as though the ride was normal
  • Everyone else vanished in the first mile. I don’t think they went up the road; they just vanished. After that I only saw occasional riders.
  • Except that, as I struggled to reach the bottom of the climb on lap one, large bunches started to come by. I think they were the faster riders lapping me in real time (but remember that, in Zwift time, I wasn’t slow enough for them to have done that - so which time was Zwift really using?)
  • Numbers of riders were drifting upward to 1400 even then; how could riders be increasing that far in? Later, when many others would have finished, numbers still didn’t go down that far, maybe 1300.
  • When riders were in sight, all the usual nonsense with riderless bikes, riderless wigs, massive bike pile-ups, and at one point someone riding across the lake by the road, approaching the first hill.
  • Finally, approaching the end of lap one, it all suddenly went normal, except that I saw no other riders at all after this point. A whole lap completely alone! The rider table said that there was one person 7 minutes ahead and one 30+ minutes behind, but those were the only two names showing. It did say that there a large number of (unidentified) others.

Overall, it was not a group ride. I did the whole thing alone, but lap one was just plain frustrating. And now, I no longer believe that looking for events with maybe 1000 riders will guarantee a proper ride.
[/quote]

ne. I’m using a laptop with windows 10. Any ideas why my ride was so glitchy.

I would guess there was just to many riders for the laptop to render. Big events pit a big load on the cpu and gpu

1 Like

So a better laptop would help the problem

1 Like

Would a better optimized Zwift help the problem?

1 Like

how much? the engine is pretty low.
if the cpu will blow up its based on the shitty code.
if the gpu will blow up its easly fixable just to see what causes it by simply choose the lowest graphic setup available.

what @Ronald_Summers was talking about is a simple connection loss. or a server client problem caused by to many riders at the same time … my guess the servers cant handle so many connections, the current rider mass.

i remember 2 years ago events with 2000+ riders causes these problems too and this was later fixed. when pros were used to gather more and more people into one event of sponsor X. most of the times those rides crashed or people finding themself riding alone … but now you have even beyond 10000 riders … thats insane.

its far beyond making fun riding with such a huge amount of people in one world… at least its not on all routes.

Decided to plan around it and did the run yesterday afternoon when I saw that Zwift was busy and the ride this morning. Much smaller field, noooo issues. Prefer (personal preference) the smaller fields anyways.

1 Like

Much of this ground was covered in a previous thread on stage 1.

No, the numbers in my event were relatively small. 1400 riders is half the number that have ever caused me issues before. Hence my comments in my post here where I reported my experience. I’ve linked in my last post to a thread about stage 1 that discussed whether the issue was in our devices rendering, or in Zwift’s servers, and was leaning towards the latter. But I don’t think we know.

Put your Log file in Zwiftalizer and look at the frame rates of a successful ride and compare it to a big group ride.

It depend on a few things like what is your laptop specs, how many other programs are running?

Put some of your log files in Zwiftalizer.com and see what is your FPS on different rides. That way you can see what size events to avoid if your Laptop is struggling.