Category Enforcement not working (Racing Score)

Racing
21

I have made an assumption that Zwift have made a change today so may well be wrong - I usually am.

IMO the issue is that there are possibly four ZRS score in play;

I. Previous ZRS race result score

ii. Possible different ZRS score as a result of decay or a non ZRS race 5 min pb prior to the race - and likely the race sign up ZRS.

iii. In race 5 min pb change to ZRS

iv. Actual race result change to ZRS

Which ones do you use in the race results to cover all the 4 scores and the changes accurately and clearly ?

22

Hi, for someone who has a quick look in the companion app Iā€™d like to see their ZRS before the start of the race and the total increase given by their performance in the race.

It would at least make sense if the guy who won my race showed a score below 510 and an increase of 400. The current display doesnā€™t show their original ZRS or how much it has increased, which seems a bit pointless.

23

thatā€™s got to be dodgy equipment, maybe he is on a spin bike :rofl:

24

I might have guessed.

I follow zrApp quite closely but just to check, does it also handle out of racing decay and new[edit: out of race] 5 min pb changes ?

25

Iā€™m confused. I was 240 something before todayā€™s race. Or I thought I was. Just did a race and I now show in 300s. Which is fine, but it looks like I cheated as it is only showing me going up 6.

image
image1206Ɨ1253 171 KB

26

It seems you set a new 5 minute PB during the race, which has set you a new seed score above your old score. On top of that you gained 6 points due to where you finished in the race.

Until very recently the score movement shown would have been the difference between your score at the end of your previous ZRS race and your score at the end of this race.

It seems itā€™s only in the last few days that this has changed to showing only the movement due to the results of the race.

Not quite sure why Faithorn is showing only a score floor increase. Thatā€™s inconsistent with the rest of you. Could be a bug that zwift wants to resolve before announcing this change.

27

Thats actually great.