Zwift Chat

[Whorty]

Oh no that's less than ideal! You've probably seen it but the WTRL rules say:

View attachment 792546

I suppose that Zmap thing affecting lots of people is down to suddenly having 4-5 minute climbs in a race where everyone is going full gas - a bit like in the old days of 20 minute power when they'd throw in a course with a 20 minute climb and loads of people got upgraded!

Probably why that put that course early in the league, to filter riders out. I don't think anyone in our race (C Development) exceeded limits but some came close.
Once up those KoMs was brutal, definitely wouldn't have been able to get up there twice!! Kudos for you Bs

 

[mjd1988]

Probably why that put that course early in the league, to filter riders out. I don't think anyone in our race (C Development) exceeded limits but some came close.
Once up those KoMs was brutal, definitely wouldn't have been able to get up there twice!! Kudos for you Bs

In fairness I think the pace probably reflected that people were keeping something in the tank for the 4 climbs, no point in placing well on 1 or 2 then getting dropped as you lose so many points. There were two climbers who were head and shoulders above the main pack and just glided away on the uphills then let the pack take them after the sprints. Played it well to be fair

 

[bridgy]

Here's the race from my perspective


View: https://youtu.be/4G2FOm3Oh9o?si=EoSzobC4qllSyGNn

 

[mjd1988]

Here's the race from my perspective


View: https://youtu.be/4G2FOm3Oh9o?si=EoSzobC4qllSyGNn

Great effort. You managed the descent of that 2nd KOM very well, didn't realise how strung out it was

 

[bridgy]

Great effort. You managed the descent of that 2nd KOM very well, didn't realise how strung out it was

Yeah I did make one mistake on that second KOM which was to use my feather too early - which is partly why I think the gap formed ahead of me. But I think I was feeling a bit desperate in that moment when I deployed it! I was never that worried about getting completely dropped though because I knew there was only a small number of riders ahead, that the gap was quite small, and I didn't think people would want to pull hard at the front of that group because there was still a long way to go - and that proved to be the case.

I was trying to manage my efforts on the first two KOM's - on the second two I think it was just on the limit!

 

[N0bodyOfTheGoat]

Anyone else doing the CTT winter series TT first round tonight? Points for position and bonus points on specified segment each week, ~700 signups so far!
https://zwiftinsider.com/cycling-time-trials-winter-series
https://zwiftpower.com/events.php?zid=5188741

 

[Dorset Boy]

Looks like Zwift is currently down, so maybe no CTT tonight!

 

[13 rider]

I have finished a ride and was wondering why it won't upload to Strava and why I couldn't log back on . Sorry if I broke it 😁

 

[Legs]

I'm down to ride but I'm not sure I will. I might do Saturday morning (9am), but it'll be a bit of a race to get it finished, get myself clean and to get my son to his 10am Lifesaving class on time.

 

[13 rider]

Looks like Zwift is currently down, so maybe no CTT tonight!

Looks like it's all back up , companion App working and ride just uploaded correctly although App feed only has a third of the ride

 

[alex_cycles]

IMPORTANT: Due to an inordinate high number of DQs initially in Race 2, we disabled several systems that determine zMAP excesses (Code 6) these to ensure accuracy. These systems will be re-enabled later today (Wednesday) which will affect the current results for Race 2. We are expecting to see more than 700 Code 6 and 7s to be reinstated which will impact many teams as Race 2 routes were very zMAP and zFTP demanding. Most will already see their category has upgraded on Zwift so these should not come as a surprise to most.

You couldn't really make it up. Consider the results not finalised and subject to flux.

[Edit to add] Looks like the dust has settled and the people DQed by code 6 in our race are only the 7 who became Bs. The Watt-floor has been respected and that means the lightweights are not kicked out without actually becoming Bs. This makes sense to me. But more importantly, it means we came third in that race and are third in the League and we are all still allowed to race on.

Our sister team lost 2 riders to B though, but they are strong riders so it wasn't a huge surprise. I wish the system coped better with returning riders.

 

[bridgy]

You couldn't really make it up. Consider the results not finalised and subject to flux.

[Edit to add] Looks like the dust has settled and the people DQed by code 6 in our race are only the 7 who became Bs. The Watt-floor has been respected and that means the lightweights are not kicked out without actually becoming Bs. This makes sense to me. But more importantly, it means we came third in that race and are third in the League and we are all still allowed to race on.

Our sister team lost 2 riders to B though, but they are strong riders so it wasn't a huge surprise. I wish the system coped better with returning riders.

Sounds like they basically failed to take into account the watt floor in their automatic detection of Zmap infringements. They did the right thing by reinstating everyone under the watt floor like you, as that's simply part of the categorisation. I'm not surprised they did this but forgetting the watt floor part of Zmap initially is a bit sloppy!

As for returning riders I get where you're coming from and have sympathy for some, but others should really know better I think. For example, both Michael and I dropped down to C after not racing much over the summer but chose to join a Cat B team as we knew it was our true level and we'd probably get upgraded once fully racing again (which I immediately did, although by some miracle Michael is still Cat C despite doing the 2nd highest power in our team in the TTT, and then finishing 7th/46 - highest in our team - in the last race!). Not everyone thinks ahead like that

 

[N0bodyOfTheGoat]

Head up for Zwift racers, your ZRS score may well be higher today, rules for decay have been changed for the better.

Don't forget the ZRS plugin for zwiftpower, to see more details than currently available natively.

The CTT TT last night was brutal, not very turbo acclimitised at the mo so I think my heart rate was a bit higher for a given power, plus in recent months the closest interrval I've done to last night's ~34mins was a single outdoor ~23min segment. Can't see a league table yet, but after loads got pen promotions I think I got 6th on whole ~19.3Km time and 4th for the Fuego Flats Reverse segment bonus in the weakest pen... The dodgy looking youngster got promoted to A!

 

[bridgy]

Head up for Zwift racers, your ZRS score may well be higher today, rules for decay have been changed for the better.

Don't forget the ZRS plugin for zwiftpower, to see more details than currently available natively.

The CTT TT last night was brutal, not very turbo acclimitised at the mo so I think my heart rate was a bit higher for a given power, plus in recent months the closest interrval I've done to last night's ~34mins was a single outdoor ~23min segment. Can't see a league table yet, but after loads got pen promotions I think I got 6th on whole ~19.3Km time and 4th for the Fuego Flats Reverse segment bonus in the weakest pen... The dodgy looking youngster got promoted to A!

Oh yeah - they've finally fixed the fact your racing score decayed simply because you haven't done a ZRS enabled race (but could have been smashing it in ZRL for example) which I think everyone agreed was silly! Here's the detaisl of what's changed (from https://forums.zwift.com/t/racing-score-update-nov-12-2025/659342/17)