vELO rating instead of ZRS – now!

I really think you are over estimating the impact of racing on Zwift.

Last numbers I heard was that only 15% of Zwifters race and even less (around 5%) are racing reguarly. So I doubt those 85% other paying customers care or think it is a great idea if Zwift build in a automatic weight checker and would rather see that money and time spend on things they do use, like new roads.

1 Like

Age category racing is supported by zwift, it even has pen enforcement.

Age is a pretty terrible indicator of performance on zwift which is why these races generally aren’t very popular and there aren’t many of them.

5 Likes

I’d much prefer racing some unfit 30 year olds than the beasts who are my age :face_with_peeking_eye:

1 Like

It’s a terrible idea

3 Likes

Carl, I envy your self-confidence, but sometimes I find it a little over the top.

6 Likes

What problem do you think a weight platform solves? Personally I think it is pointless and unrealistic.
Nobody really wants to throw money at this. There is no Zwift racing for money, so who cares?

Obvs you think it’s a great idea because it’s YOUR idea. I think it’s a crap idea because it’s completely unrealistic and doesn’t really solve any serious issues.

10 Likes

Well, at least we got an apology. :wink::blush:

3 Likes

While known dubious hardware setups probably need to be booted, there are less extreme steps that could be taken to improving fairness in terms of using some AI (as much as I hate AI) to catch out dubious performances automatically during races so they don’t completely ruin races. That definitely needs to be across the entire platform.

Sure it will probably have some glitches to start with concerning edge cases, but over time it can be sorted out. At least deal with the simple cases to start with.

But when dubious performance becomes the normal people will start jumping ship to elsewhere. It’s a case of a must-have.

New routes are done by the graphic artists, rather than the programmers. So it’s not a case of one or the other. When I used to do 3D stuff for games I didn’t need to bother any developers, we had plugins for the 3D software to handle the export process into the required file formats.

1 Like

keep in mind… we Germans looooove sarcasm :wink:

4 Likes

Dubious performances must be dealt with. But building in a weight scale into set ups and demand everyone to use/buy them isnt the way forward.

4 Likes

Zwift is a perfect application for AI but not only would it need to check for sudden weight changes it ideally should monitor each individuals heartrate and for a fitness profile for you that again should only go up and down slowly. This would help eliminate people with any changes outside the pre-set parameters. Note the AI is working on just your heartrate and not against anyone else. Zwift could also do the classic recovery test where you simply stop riding and a timer runs against your decline in heartrate. This technically only needs to run for 60 seconds but I found it useful data if it ran for 3 minutes.

And I wasn’t suggesting that, but we must have controls to prevent wild weight changes from day to day or one event to the next.

The Simpsons : Mr Burns IS BACK And Better Than Ever!

Completly agree. And I can not really think of one reason why this has not been implemented in the game yet. I would love to hear the reason as to why Zwift thinks this is not needed/wanted.

2 Likes

Does it bring in quick cash? :money_with_wings: No? Then it’s a ghost ride! Zwift likes features that keep their wallet as happy as our avatars. :man_biking::sparkles:

Not to mention the massive shifts in height

1 Like

Height should definitely be part of the formula that decides your pen, given the insane aero advantage in Zwift for riders claiming to be short, along with weight and power.

Don’t know how this thread about categorisation got so distracted, but +1 for vELO adoption. (Especially after vELO2 becomes the norm)

2 Likes

Pure power wins every time

Pretty obviously any manually entered weight change should be then locked for 30 days before another change can be made. That should be pretty easy to implement.

The reality is, the whole problem is the “Manually” entered in the first place.