How Cadence Affects Rider Position

I tend to spend a lot of time climbing at a cadence of 70 rpm. It seems that your avatar will stand and climb below 70 rpm, and sit above 70 rpm, causing him to move around a lot when pedaling right at 70 rpm. Maybe this could be fixed by requiring you to be at a certain rpm for 3 seconds before the new position takes affect, then the rider wouldn’t move around every half second. You can see an example in this video:

I agree with this. Very annoying if you are hovering around the 70rpm level. My ‘solution’ is that the avatar should stand at 70 rpms, but then not sit back down again until 75 rpms. This would allow a little slack in the system.

I also wonder if, someday, Pedaling Dynamics (or whatever it’s called that is used in Garmin and Favero pedals, might be implemented in Zwift (for those with compatible devices, anyway) so that the avatar would stand and sit in tandem with the actual Zwifter. I think that would be great.


I concur… with a caveat. Everyone’s self-selected optimal cadence level is different, and within fairly large bands. The individual rider should be able to select the cadence level at which the avatar transitions between modes. A more subtle cue in this regard would also include the crucial on-screen transition between being in the drops, and being on the tops. Since the group-dynamics AI alterations, this important cue has been drastically altered, and often in a detrimental way. One is now often shown “on the tops” when the entire peloton is at one’s side… and confusingly, be shown in the drops when shown immediately behind and in the draft of the (on-screen) rider ahead. These essential visual cues should be directly correlated to “game physics” as they are crucial visual feedback indicators in races, and especially in TTT events, inter alia.

I agree, but I think this is tied up with the fact that we don’t all see the same thing. Where I think I am with regard to another rider might not be where the rider next to me thinks I am, nor where the server thinks I am.

It should be consistent with what I see I think, but that would be misleading if my client is saying “Dude! You’re drafting!” and the server’s thinking “Nah mate, you in the wind.”