When doing a workout, one can include free ride blocks. Before 1.25, they also gave resistance and grandient changes to kickr and climb. But after 1.25, there’s no change in resistance and grandient anymore while being in a free ride step of a workout.
But once you finish the free ride step, you get a big bump up incline change on the kickr climb, but it doesn’t even depend on the actual gradient of the map.
Noticed this while doing a workout which included free ride steps followed by ERG mode blocks and vice versa. The ERG mode blocks did work as intended.
Today, I did another workout which included Free Ride steps. Again, no gradient based changes in resistance for my Kickr. This is so annoying, Free Ride step in workout is completly broken since the v1.25.0 update.
What workout was that. there are very few workouts that will simulate the terrain during free ride, most will be flat road where you can adjust the resistance in the companion app or the ± keys on the keyboard.
Hard to say, Mike because like Gerrie said and to my knowledge, most ERG mode workouts aren’t supposed to simulate resistance changes when the gradient increases/decreases. It’s usually just a SIM mode thing where that happens.
If there are specific workouts where you notice you have been able to do this previously in free ride blocks, I can take your issue to the team and try to get some feedback for you. Thanks!
From the original post, I think Mike designed a custom workout that simply included Free Ride segments. Meaning, I think, that this means the ERG mode would effectively turn off (hence ‘free’) and wherever you’re riding, that’s where the “free” ride portion occurs; so you’d be subject to whatever the course terrain hands you?
Built a custom WO this evening with freeride and freeride goes into SIM mode (feel the terrain). Checking the zwo file, flatroad=0 which is SIM mode whereas flatroad=1 is flat. I have no idea if this has changed as OP indicates however as I have never used a freeride. Doesn’t appear that OP has confirmed whether its a custom or Zwift WO either.
@Dean It was a custom workout which I built inside Zwift, so yes. I’ll check the .zwo file if flatroad=1 is enabled. Can you please send me the text line of that step so that I can see how the syntax should be?
I did some digging into my .zwo files. I created two workouts using the Zwift Workout Builder. These two have Flatroad=“0”.
I then just copied one of the workouts two times inside Zwift workout window and altered them, e.g. changed length and included a few repetitions. These copied workouts all had this parameter set to FlatRoad=“1”. These workouts where the ones I rode and experienced the changed behaviour.
This is interesting. Maybe it’s not because of the update, it’s because something got changed during the copy process. Or if it’s related to the update, it changed the default parameter to “1”, because I copied them afterwards if I can recall this correctly.
Anyway, I’m quite confident we found the solution to this.
This is kinda contrary at least somehow. I can assure you that I’ve created the workout from scratch inside the workout builder and the .zwo included FlatRoad=“0”. I didn’t manually edit the file afterwards.
After copying one of the two workouts, these had FlatRoad=“1” set. I also didn’t edit them after creation.