Game Update v1.69 [July 2024]

HAHAHA, exactly, that’s life, you’re riding high in April, shot down in May…

1 Like

Why do you find it necessary to interject in a question that I didnt ask you? What you find unimportant is not my concern.Enjoy your evening.

1 Like

I have noticed frequently in the 1.69 app that the times shown in Group Riders Nearby are often highly inaccurate. Other riders have commented the same.

Examples are with S. West in one screenshot who is ahead of me, not 16 seconds behind of me as shown.

In the other screenshot, D.Hill_YYJ is shown 43 seconds ahead of me and is within a stone’s throw and the two riders who are ahead of me show times behind me.


1 Like

@shooj

+1 to riders nearby times being wrong in group rides today. Had this problem on two rides.

For example, riders would be 20 to 30 seconds behind me, but list would say 3 seconds.

K.Nail is much further than 3 seconds behind in screenshot; you can tell from mini map. Also A. Kemp is shown as being fewer seconds behind than folks in front of them.

1 Like

They are inaccurate whatever you are doing then they go haywire when you go through junctions.

Sauce does a much better job of accurate gaps.

I think this might’ve been an intentional decision but to not start the game clock at the same time as the event clock is nonsensical (and it exists in 1.69 and so it’s relevant to this thread). Please correct this.

1 Like

Zwift did ‘sort’ this out in December but I believe things have reverted back to how they were pre 1.55.

Easiest way to identify changes is to watch race videos.

Pre December and now are the same - race results from the gun and HUD from crossing the start line (not the pen line). At end of race HUD time doesn’t change.

Feb/March videos - race results from the gun, HUD time from the gun. At end of race HUD time changes back to the ‘from crossing the line’ time.

1 Like

What the heck happened with 1.69? So many bugs that had been dealt with are back. Did someone reference an old batch of code inadvertently?

@evan-zwift how did the QA department that both exists and is good miss all of the issues brought back in this release?

4 Likes

In my 3 years of Zwift, I’ve never experienced crashes until this patch; now it’s happened twice.

Happened again trying to take an auto screenshot of all things…

[11:59:56] Got Notable Moment: FINISHED EVENT
[11:59:56] Requesting Notable Moment Screenshot, type=FINISHED EVENT, delay=1.75, distance=-1.00
[11:59:56] ERROR: ZwiftApp Crashed

2 Likes

Interesting position in pen with v1.69 :thinking:. Anyone else saw it?

Luckily, it only took an U-turn upon race start to get back to normal :pray:.


That’s been an issue with Paris since it was launched. Dont think it was ever fixed.

1 Like

So that is about 1/3 of the group looking the wrong way.

Maybe they are trying to lower their racing score.

5 Likes

That’s not a bug, it’s a feature.

It promotes a richer user experience by encouraging interaction and communication between riders.

Why else would it still be happening 4 years later?

6 Likes

This feature would be more appropriate for April’s Fools Day :joy:

Perceived effort increases in ERG Mode downhills or at lower resistance than uphill and higher resistance - KICKR Bike v1 connected via Bluetooth LE on latest firmware with ZwiftApp 1.69, more videos showing the changes in cadence here (this has been an issue for a long while, more information to help investigate per comments on this thread and the thread of the previous build):

Can observe in the cadence line that it is easier to pedal faster at higher resistance (the 295W parts) - the trainer flywheel “bites” less:

Just to support this, Spoke with my other half who only uses erg & she suffers the same. Using a Kickr Shift via BLE

Im fairly sure its been about a lot longer than this release as I remember feeling it a good while ago using a Atom.

Its a really difficult one to pin down and say yes there is an issue.

1 Like

It felt glorious when I used TacX Neo2T. I first noticed it around April 2022 and started an ERG Mode Smoothing thread which I thought was culprit, but it happens with or without smoothing. A few others brought it up in the 1.68 thread, but it is definitely a longstanding issue. I want to replace a lot of my group riding routines with workouts so it’s very much worth my effort to get an investigation into it knowing (finally) it’s not only me. :slightly_smiling_face:

I switched KICKR Bike from Bluetooth to ANT+ FE-C in ERG mode and SIM mode during the same ride this morning and everything felt MUCH better. I did some “Google Probing” to see if there were comments on the Internet.

Then I found this Zwift Insider article from 2019:
Wahoo KICKR Tests: Connecting via Legacy ANT+, ANT+ FE-C, and Bluetooth | Zwift Insider

The degradation in Bluetooth performance I found would have been around the same time as the KICKR Bike firmware 1.22 which implemented Bluetooth FTMS.

The problem is the “base resistance” on Bluetooth still remains to be different than with ANT+ FE-C - why this is the case, I do not understand - and this seems to be what is contributing to these issues observed in ERG mode and with Trainer Difficulty = 0. The cadence becomes “fought” and harder pedaling has to be contributed to compensate for the flywheel resistance “bite”.

This is notable:

  • ANT+ (non FE-C): 184 watts average
  • ANT+ FE-C: 215 watts average
  • Bluetooth: 182 watts average

Update: Tried a group workout on Tempus Fugit using ANT+ FE-C. Base resistance was definitely better but the “cadence fight” persists at lower resistance levels. As the power target increased, so did my cadence. The “cadence fight” effect was a little less severe with ERG Mode Smoothing off - turning this off, however, is by no means ideal nor does it solve the problem.

I’m 99% sure on a definitive root cause on the resistance issue impacting workouts. It’s not something you would expect to be possible. On Phoenix Rising Polar Express this morning we did the Mat Hayman Paris-Roubaix workout and I commented about pedaling getting harder downhill for KICKR users, Sue Hall PHX/EZR said it impacted her Tacx Neo2T also. Kim Salt (Yeti upRising) said she had the issue in Metric Units but not Imperial units. “Impossible”, I thought. “Those are just display units and have nothing to do with the game algorithm, right?”

As I was fighting cadence resistance feedback doing the workout on the Cobbled Climbs route I changed it and my resistance feedback improved significantly.

Why would this be the case? @evan-zwift @shooj and CC: @Eric_Schlange_ZwftIn

This was a tough workout but MUCH less difficult once I switched it to Imperial.

As an aside it was some point around the time I started having these issues when I switched to Metric, so it may not have any correlation with KICKR or the firmware or whatever, or it might. But this is a key piece of information, and if the game algorithm is different based on display unit setting, I’m sure that can be determined in the code.

I was using ANT+ FE-C (see comments above) but I think perhaps the lower data sample rate versus Bluetooth FTMS smoothed out this anomaly a bit.

After “Cadence Fight”, I switched the setting to Imperial.


Here’s a video where I would have dealt with a cadence fight going downhill before (low cadence/low resistance), but since I was on Imperial I didn’t.

1 Like