Bring back the exact watt goals for workouts. Stop the rounding!

Had a TrainerRoad workout in Zwift today. No rounding on main screen and for current interval on companion app. For upcoming intervals in the list below current, values at each end of a ramp were not rounded but values in a steady state were rounded. So you had the odd sight of a ramp from, say, 114 to 127 showing correctly with the next interval showing in the list as 125 but when you got to it, it would be 127. Minor detail at this scale of course.

Didn’t see any rounding in a workout synced from Xert this week either.

Yeah, I saw that mention from @Craig_Harris_KoS up above. What needs to figured out is how the wko files from some sources are authored differently in a manner that the Zwift app doesn’t round off.

Does anyone know… if you edit the text in a wko file (eg. using Notepad) and save again, will it still work perfectly fine in Zwift?

It’s nice that the workouts of 3rd party apps are no longer rounded. But what about Zwift’s own workouts? When will the rounding stop there too?

1 Like

Probably never because the “integration partners” are almost certainly paying Zwift for the privilege of having a bug fix implemented for their users.

Guys, we have to remember what our head of open communications told us :rofl:

1 Like

We’ll, obviously it is. It seems to be a little toggle now.

3rd party integration = not rounded
Own integration = rounded

2 Likes

Not sure how I got in that habit.. I meant .ZWO files (not wko files). How is one driving a different app result than another?

What happens if you have an imported 3rd party workout and you then edit your FTP in zwift? Does it scale those workouts?

I understand that all native zwift workouts - except ftp ramp tests - are set up as a % of FTP, even if you build them as defined watt targets.
If the 3rd party workouts aren’t scaling with FTP changes, then it would indicate that those are set up as defined watt targets, and it follows that the rounding issue is somewhere in the FTP scaling calculation.

Yes, it scales the workout as well. Already tried that.

Asking again, if there’s someone who is a TR or whatever else subscriber, who is getting imported workouts that are not rounding the watts in-game, can you please open the .zwo file in notepad and copy/paste the full text of the file here? The files will be in [username]\Documents\Zwift\Workouts, and depending on your configuration there may be a \OneDrive\ directory between your windows username and \Documents\

Did this today via intervals.icu. 90% of 245 came across to Zwift as 221 watts :+1:

<workout_file> 
<author/> 
<name>2x20 sweet spot</name> 
<description/> 
<sportType>bike</sportType> 
<durationType>time</durationType> 
<tags/> 
<workout> 
<SteadyState Duration="300" Power="0.5"/>
<SteadyState Duration="180" Power="0.7"/>
<SteadyState Duration="120" Power="0.9"/>
<SteadyState Duration="300" Power="0.4"/>
<SteadyState Duration="1200" Power="0.9"/>
<SteadyState Duration="300" Power="0.4"/>
<SteadyState Duration="1200" Power="0.9"/>
<SteadyState Duration="300" Power="0.4"/>
</workout> 
</workout_file>
1 Like

It appears that the bulk of your zwo text didn’t make it through the forum controls. There’s a </> icon in the post controls that should allow the full text to show up.

Sorted :+1:

2 Likes

This is one of my built-in-Zwift workouts for comparison.

<workout_file>
    <author></author>
    <name>Z2</name>
    <description></description>
    <sportType>bike</sportType>
    <tags>
        <tag name="zone2"/>
    </tags>
    <workout>
        <SteadyState Duration="300" Power="0.55449998" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
        <SteadyState Duration="300" Power="0.7015" pace="0"/>
        <SteadyState Duration="300" Power="0.78483331" pace="0"/>
    </workout>
</workout_file>

Couple of differences in syntax but not anything that screams “stop the rounding because of this.” Is the zwo in a different folder than just \workouts\zwiftID? \TR\ or something like that?

Nope. I just dragged and dropped it into the usual spot. My Zwift account is linked to intervals.icu, and it shows that when I look at my custom workouts.

1 Like

@calfzilla someone mentioned a “TR” subfolder containing the workouts. Maybe it is related to the rounding? We could give this a try.

Or someone at Zwift could simply tell us how to edit a zwift-created ZWO file so that it won’t be rounded.

2 Likes

:joy: Really, you expect SUPPORT? :sob:

PS: They seem to have changed the mechanism for 3rd party workouts. Testet with Trainingpeaks, there is a folder named “Trainingpeaks” in “custom workouts” available in game, but no file is downloaded in the/a local folder Zwift\Workouts\ <uid>… → sadly, we have to pray and wait that they don’t forget their own customers.

@calfzilla Did some testing with a TR mrc file and a zwo file. The mrc file is very different and doesn’t show up under Zwift at all. Didn’t try a zwo file inside the TR folder, will do that next time.