Custom Workouts: Cadence errors from zwo file


(James Berry) #1

BUG - Please help.

In general, I’m seeing a pretty consistent bug where cadence values in the zwo file are not what are being displayed in Zwift.

I notice this in almost all of my custom workout files, but especially when I have lots of blocks. For example, the following blocks …

<SteadyState Duration=“30” Power=“0.82222222” Cadence=“80” CadenceResting=“95”>
<textevent timeoffset=“0” message=“Subtle and smooth transitions”/>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“90” CadenceResting=“95”>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“100” CadenceResting=“95”>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“110” CadenceResting=“95”>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“80” CadenceResting=“95”>
<textevent timeoffset=“0” message=“Subtle and smooth transitions”/>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“90” CadenceResting=“95”>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“100” CadenceResting=“95”>
</SteadyState>
<SteadyState Duration=“30” Power=“0.82222222” Cadence=“110” CadenceResting=“95”>
</SteadyState>

… result in the following blocks and cadences in Zwift …

30sec @ 82% FTP, 87 RPM
30sec @ 82% FTP, 92 RPM
30sec @ 82% FTP, 97 RPM
30sec @ 82% FTP, 102 RPM
30sec @ 82% FTP, 87 RPM
30sec @ 82% FTP, 92 RPM
30sec @ 82% FTP, 97 RPM
30sec @ 82% FTP, 102 RPM

… instead of what was specified in the zwo file …

30sec @ 82% FTP, 80 RPM
30sec @ 82% FTP, 90 RPM
30sec @ 82% FTP, 100 RPM
30sec @ 82% FTP, 110 RPM
30sec @ 82% FTP, 80 RPM
30sec @ 82% FTP, 90 RPM
30sec @ 82% FTP, 100 RPM
30sec @ 82% FTP, 110 RPM

 

 


(James Berry) #2

Note : to try and accommodate, I’ve attempted to use an IntervalsT block and specify cadence transitions as TextEvents.  This works for now, but obviously isn’t ideal.

+1 for all block types (Warmup, Ramp, SteadyState, IntervalsT) to allow variable cadence setting at specific time offsets. (e.g. TextEvent)


(James Berry) #3

BUG IDENTIFIED

Cause: Adding ‘CadenceResting’ values to blocks other than Warmup and Ramp (e.g. SteadyState, IntervalsT, etc.) results in inconsistent cadence values being displayed.


(Jason K) #4

We had a look at the data you sent, and it looks like you’re trying to edit the file itself instead of using the in-game editor which is why you’re seeing these issues. We only recommend using the editor to change workouts as it can cause validation issues otherwise.

Thanks!