Zwift Chat

[Del C]

Well I did my first Team Time Trial tonight.

Some good things, some not so good but overall I really enjoyed it and I'd recommend it.

So, there were 8 of us in my team and the course was 2 laps of Greater London flat at around 18 miles. We were part of the 18.30 start group, but we had an offset start time of 7m 30s. So at 18.30 we stopped pedalling and sat in the pen chatting on Discord until our Captain shouted 'Go' at our start time of 18.37 and 30 seconds.

I'd forgotten to select a big enough gear before we stopped pedalling so I got a crap start and had to chase back on to the group. Another of the team had the same problem. Once we both chased back the group stayed together for the first 10 miles. We were riding quite tightly as a group, but it was quick and we were pushing about 270/280 watts a lot of the time. I was staying with the group, but it was hard work.

Then a little after 10 miles, coming out of the tunnel near Green Park on the uphill after the tunnel, disaster struck. We had another group in front of us . I was near the back of the group and got caught in the sticky draft of the other group. I tried repeatedly to break away but every time I got to the front I got swallowed up again. Going past Buckingham Palace I just had to tell the other guys to go on and I rode the last 6 to 7 miles home by myself. The team finished 65th out of 110 teams in our class with a time of 42.01. I was about 0.8 mile behind when they crossed the line and finished in 44.32

And, as I closed Zwift down I got an FTP upgrade from 251 to 253 watts!

I got an invite from the guys to ride with them again, which I've said I'll take up, although it may be a couple of weeks as its my 3rd race in 4 days and I don't think I can keep that up.

But it's great fun and I can recommend it!

 

[bridgy]

Well I did my first Team Time Trial tonight.

Some good things, some not so good but overall I really enjoyed it and I'd recommend it.

So, there were 8 of us in my team and the course was 2 laps of Greater London flat at around 18 miles. We were part of the 18.30 start group, but we had an offset start time of 7m 30s. So at 18.30 we stopped pedalling and sat in the pen chatting on Discord until our Captain shouted 'Go' at our start time of 18.37 and 30 seconds.

I'd forgotten to select a big enough gear before we stopped pedalling so I got a crap start and had to chase back on to the group. Another of the team had the same problem. Once we both chased back the group stayed together for the first 10 miles. We were riding quite tightly as a group, but it was quick and we were pushing about 270/280 watts a lot of the time. I was staying with the group, but it was hard work.

Then a little after 10 miles, coming out of the tunnel near Green Park on the uphill after the tunnel, disaster struck. We had another group in front of us . I was near the back of the group and got caught in the sticky draft of the other group. I tried repeatedly to break away but every time I got to the front I got swallowed up again. Going past Buckingham Palace I just had to tell the other guys to go on and I rode the last 6 to 7 miles home by myself. The team finished 65th out of 110 teams in our class with a time of 42.01. I was about 0.8 mile behind when they crossed the line and finished in 44.32

And, as I closed Zwift down I got an FTP upgrade from 251 to 253 watts!

I got an invite from the guys to ride with them again, which I've said I'll take up, although it may be a couple of weeks as its my 3rd race in 4 days and I don't think I can keep that up.

But it's great fun and I can recommend it!

Well done Del, glad you managed to do it - Lee and I were in a team at 7pm. Absolutely brutal! To give some context, one of our team averaged 4.9 w/kg and another 4.7 - which meant they were doing turns on the front at 6+w/kg so hanging on was something of a challenge! We did mostly hold it together quite well though. I'm not sure of our official time but ZP say 52:02 for 4th man and we had to wait on the line for 13 minutes so around 39 minutes maybe? Where did you get your time - just from ZP in the same way?

 

[Del C]

Well done Del, glad you managed to do it - Lee and I were in a team at 7pm. Absolutely brutal! To give some context, one of our team averaged 4.9 w/kg and another 4.7 - which meant they were doing turns on the front at 6+w/kg so hanging on was something of a challenge! We did mostly hold it together quite well though. I'm not sure of our official time but ZP say 52:02 for 4th man and we had to wait on the line for 13 minutes so around 39 minutes maybe? Where did you get your time - just from ZP in the same way?

I signed up to the WTRL website last Saturday so I can log in and check the results, but you can work your own and team times back from ZP.

If you tell me your team name I can check it on WTRL

 

[Brendan Parker]

Well I did my first Team Time Trial tonight.

Some good things, some not so good but overall I really enjoyed it and I'd recommend it.

So, there were 8 of us in my team and the course was 2 laps of Greater London flat at around 18 miles. We were part of the 18.30 start group, but we had an offset start time of 7m 30s. So at 18.30 we stopped pedalling and sat in the pen chatting on Discord until our Captain shouted 'Go' at our start time of 18.37 and 30 seconds.

I'd forgotten to select a big enough gear before we stopped pedalling so I got a crap start and had to chase back on to the group. Another of the team had the same problem. Once we both chased back the group stayed together for the first 10 miles. We were riding quite tightly as a group, but it was quick and we were pushing about 270/280 watts a lot of the time. I was staying with the group, but it was hard work.

Then a little after 10 miles, coming out of the tunnel near Green Park on the uphill after the tunnel, disaster struck. We had another group in front of us . I was near the back of the group and got caught in the sticky draft of the other group. I tried repeatedly to break away but every time I got to the front I got swallowed up again. Going past Buckingham Palace I just had to tell the other guys to go on and I rode the last 6 to 7 miles home by myself. The team finished 65th out of 110 teams in our class with a time of 42.01. I was about 0.8 mile behind when they crossed the line and finished in 44.32

And, as I closed Zwift down I got an FTP upgrade from 251 to 253 watts!

I got an invite from the guys to ride with them again, which I've said I'll take up, although it may be a couple of weeks as its my 3rd race in 4 days and I don't think I can keep that up.

But it's great fun and I can recommend it!

Great work @Del C Isn’t this the course for Monday. I rode it yesterday and for a flat course this is where the attacks will happen. The kick out of the underpass?

 

[Del C]

Great work @Del C Isn’t this the course for Monday. I rode it yesterday and for a flat course this is where the attacks will happen. The kick out of the underpass?

Yes you're right.

Same course, but 3 laps on Monday.

The danger spots are probably the start because it ramps up through the finish banner, Northumberland Avenue and the underpass exit at Green Park. The small ramp after Buckingham Palace might come into play on the last lap as well.

 

[JLaw]

New update for Zwift with loads of changes 😀,new bike new challenges, improved sandbagging controls

https://zwiftinsider.com/update-1-0...GX4kRIfbXC1CWYucLvRV7BnX2gfJB4bUBRn6Pg0-Lo9EA

My ATV updated today without issues. I'd already decided to go for the beta ZHQ race today to see how the anti-sandbagging bits worked in practice and to start doing somewhat longer races.

About 3:35 into the race I started seeing a few cones of shame ahead of me, not many, but they were certainly there and at least some of the riders who got the cone were reeled in and spat out the back of the group. Over time I saw a few more cones in the group and we spit out some other riders. By the midpoint in the race it was just one other gent and myself. He seemed a stronger and likely to DQ, so I just kept putting him on the front.

At one point we caught what appeared to be his teammate who had already received a cone and apparently had the code removed (i guess if you throttle back power you cone may go away?!?), but the teammate was a lap behind us. It appeared to me like they were trying to work together, and my thinking was I wanted to lose the other guy's teammate and get my opponent back in the wind. So I hit the gas a few times and forced them to work and reel me in and bang, the teammate got a fresh cone and fell off the pace, leaving just two of us again.

I had a ghost on the 11th lap and used it near the end of the little cobblestone climb. Two thoughts here. First I wanted my opponent to pick up the pace a little to keep us away from a rider that was closing in. Two I wanted him to work harder to wear himself out while I was hanging out in his draft. Well, it backfired, I went ghost and he hammered and I couldn't keep up. Ugh!

I let the rider behind catch me and we pulled my original opponent back with about a half mile to go before the finish. I was either 1st or 2nd in our 3-person group. ZP has me as the winner. My original opponent doesn't appear to be on ZP and the other gent in our little group finished 2nd behind me on ZP by .1 seconds.

 

[bobinski]

Was doing some easy stuff and close to 40kph at 120 watts didn't seem right. Not even on the Trek Madone with aero wheels. :/

I had the same problem post app update on our team TT and had to drop off. The strange thing is I had updated and then done 2 warm up rides to make sure I wasn’t affected by the problems others were complaining about.

It was fine for me tonight. But maybe appletv doesn’t have the update yet. Anyone know how to check I can’t remember.

Click on blue App icon and it will give you option to update.

 

[Freelanderuk]

I have just done a group ride on Zwift and it was all over the place, in the middle of the pack I was having to push 2.5/7 w/kg to keep with those doing 2w/kg and if I went to the front of the group I only had to do 1.7w/kg ,something definitely not right, people reporting doing 50w and doing 22mph

 

[Whorty]

Great work @Del C Isn’t this the course for Monday. I rode it yesterday and for a flat course this is where the attacks will happen. The kick out of the underpass?

Correct The initial attack/split will be the little lump up Northumberland Ave (about 6 mins in), then you're right, the only other lump is the little climb after the underpass past Green Park. Definitely going to be a fast course

 

[Freelanderuk]

Correct The initial attack/split will be the little lump up Northumberland Ave (about 6 mins in), then you're right, the only other lump is the little climb after the underpass past Green Park. Definitely going to be a fast course

Let’s hope it goes ok and not the same as the group ride this morning

 

[mjd1988]

On this sort of flattish course discord would be really useful (on a hilly course everyone knows when the attacks come)

 

[Whorty]

Let’s hope it goes ok and not the same as the group ride this morning

I'm planning to join a Beta Crit race later to see whether I've been infected with the drafting virus Not going to be pushing full out as legs tired from a session yesterday - just hoping to get into a group and hold on. Lots of noise on FB etc about the bug .... yeah, hoping they fix this before the race on Monday else it could be 'interesting'!

 

[JuhaL]

I have just done a group ride on Zwift and it was all over the place, in the middle of the pack I was having to push 2.5/7 w/kg to keep with those doing 2w/kg and if I went to the front of the group I only had to do 1.7w/kg ,something definitely not right, people reporting doing 50w and doing 22mph

New update seems to cause some bugs. How did the riders nearby list worked?, yesterday all the names vanished from the list when we start to move from the pen, it happened both Zwift and Companion app. Some riders have also "missile inbound" effect as well, they were that fast.

 

[kipster]

There was a small update released late yesterday, for Windows systems anyway

 

[JuhaL]

There was a small update released late yesterday, for Windows systems anyway

Just checked, also for Mac as well.