Game update v 1.104 [December 2025]

What's New? Zwift Game
245

I love giving out the confetti and the +2XP in group runs. It makes it… festive!

That would be cool! It would be cool also to be able to give confetti while wearing the Lightning Aero socks - since unlocking these in August, I have ridden with the Lightning Aero socks exclusively and I run with the Confetti Socks. The fact that they give some aerodynamic benefit outweighs me “paying it forward” while cycling. They took me about 460 hours of Zwifting to unlock. Confetti Socks took arguably longer, but I gave out so many +2XP that “what’s in it for me” while on the bike won over this time.

I still do the three modes of “Mass Ride On” regardless almost incessantly while cycling despite them no longer giving +2XP nor confetti to other Zwifters because of having Lightning Aero socks equipped.

  1. Ride On (Companion) Circle on Map.
  2. Ride On (Windows Keyboard) F3 Key.
  3. Ride On (KICKR BIKE V2) Control Button.

Each of these has a separate “recharge” interval, allowing near tripling-down of mass Ride Ons.

1 Like
246

Not sure if it’s the latest neo 2T firmware or the game but going from gear 19 to 24 felt like there was no change in resistance, did the wtrl recon ride and when it came to the sprint went from 17 to 24 and it felt the same

247

I thought hard resetting and calibrating helped, but alas, it didn’t.
However I’ve found a reliable way to replicate the issue:

  • starting the game, both controllers steer as expected, no issue.
  • When pressing the left or up button on the Left controller, steering on that controller stops working until I power off/on the left controller. After that it works like normal again (until pressing Up or left button).
  • Pressing the right button on the left controller does not interfere with steering.
  • Pressing the down button makes the controller keep steering left in some cases (not always).

But every time I can just reset the behaviour by power off/on the left controller. That doesn’t seem to be a hardware but more like a firmware issue, where something goes belly up in the code, and it gets resetted by rebooting the controller.

249

experienced the same issue earlier at the end of the tour ride, was in 24 and it felt like it was in 18