It should but since ZHQ has refused to say anything about it people are reporting the broken pack dynamics behavior as a bug in this thread.
When it’s a topic ZHQ wants to have discussed in its own thread, @shooj will typically move all related posts to a new thread.
ZHQ guys coming back from Christmas break:
This is what we don’t know about, but IS the biggest flaw of the code.
And when it happens to me is 100% of the time non-nonsensical.
For Ben: sorry, I only check on the forums at work, rarely at home I still haven’t watched the video 
, that’s the only reason for not being sure (and here I am again, on lunch break).
I think I mentioned it here in one of our rides on London, where I noticed all of our sprinters were on the left lane all alone, where the blob was all to the right, leaving all the higher power folks to their own.
I’m still wondering if this is what the code is attempting to do, but failing at 95% of the time.
Happened to me today on a group ride ( ZZRS The Weekend Starts Here ) where a rider split to the right of the group and pushed both of us well outside the draft. I tried to steer against him, but he wouldn’t move. I backed off, got behind him, and was finally able to steer back into the draft. The other rider moved back as well. I didn’t notice if the other rider had steering or not.
Is this what reduced the number of rows in the leaderboard to 10 vs the previous 15?
Sometime between a Zwift ride on 13 December and the next one I have screenshots for on 22 December, the leaderboard went from 15 rows to 10.
There are no names listed in this one, but the number of rows are clearly visible
This one clearly shows only 10 rows.
Every ride now only shows 10 rows, on different Mac Mini computers, too.
Interesting thing of note; today after a month, our Saturday 100k ride, the “PD5” / steering v5, seems to be disabled:
Not sure if this was done just for us, or in general.
However; steering still functional despite being disabled in the ride settings.
Same old poor QA. They can’t test a simple on/off switch properly. They could not even label the on/off switch in the same language. In French, it’s labeled “Oui”/ “Off”!
I’ve taken to calling it “pack dynamics version: ‘scream get the eff out of my way the entire ride!’”
Probably don’t have steering devices
In a race today there were myself and another 3 cyclists on one side of the road who all had steering but I never used steering to get there and on the other side of the road about 6 riders who never had steering, we were going round a right hand bend and the steering riders had the shortest line.
Only happened once in the race as far as I noticed but I thought it was strange.
I’ve had it several times now that my avatar tried to steer towards a runner in front of me in order to get into his “draft”. Shortly before bumping into it, the avatar pulled back.
This bug was fixed many months ago. Nice to see it’s back, it’s certainly entertaining.
That’s right about the spot where it changed from showing Fox Hill.
If I’m right it also is going to change to show the rest of the elevation shown on the MiniMap.
It’s what I posted here -
I just didn’t get screenshots of it.
An issue with a workout in the new Endurance plan:
The first workout is based on the Big Ring. Designed to be completed with ERG mode off, using the sprints & terrain changes to generate the load.
All was fine until I was climbing through the Mayan jungle, when the virtual gears stopped working, and it had me locked in a max effort. I couldn’t fix it by re-pairing the bike & app, and after a period of anaerobic misery, I gave up!
No problems with normal workouts before or since.
Wattbike Atom v1, Apple TV, iPhone for ZC. All on current versions & OS.
This is an issue in lots of places but this route specifically has a lot of instances, and it’s not just at junctions which is the confusing part.
Quite a few comments about pack dynamics in here! I can share a bit of information about it.
The latest batch of tuning (which some call pack dynamics 5) has a few goals:
As for how we’ve been testing it:
So this is where we’re at today. We didn’t announce these changes as we’ve found with pack dynamics we often get lots of false positives when we announce we’ve changed anything, and we were actively changing and improving (and often disabling) the code throughout the fall. The plan was to announce and get more specific feedback once it comes time to start trying it in public races, which is where we’re getting to soon.
Next changes coming later in January:
Beyond:
The tuning of our pack dynamics is a much more continuous thing than I think people realize…and I’m sure will continue for years to come. Sometimes we specifically test with a smaller group of Zwifters, sometimes we just want to start with robopacer groups and general riders in the world, and sometimes we’ll reach out to a race organizer to see if they’re up for testing something with us. Apologies for having it enabled in the TTT’s before we’d announced it - that was definitely not intentional.
i think that if you can make this properly it would fix the biggest issue people are complaining which is riders pushing you to the outside of the group instead of the aggressor moving around you like irl
Great update.
I’m cynical about how far you can take it whilst everyone sees completely different things on their devices, and therefore are all experiencing draft in a different way, but I can’t see Zwift switching to server-authoritative (yes I have read your reasons why, but indieVelo/TPV has proven that server authoritative works for racing).
That said, very positive steps in the right direction, it is good that it is an area of concern for zwift at all.
