After doing stage 7 of TdZ I wanted to do a cool down on “Fine and Sandy” in Urukazi.
Not only for a cool down but to achieve the route badge while I’m at it.
But is was misrouted and did the mech island route twice without doing something to turn actively and to leave the route.
Ride on Strava is even called “Fine and Sandy”.
On PC, update forced to 1.33.2
Misrouting still present in 1.33.2. Occured two hours ago in meetup on Watopia “Legends an Lava”, when the group has been divided - interestingly, the chat continued working…
System Windows 10, 1.33.2.
Since the 1.33.0 update my Precor ChronoPower bike will no longer pair. I been told by support that the bike isn’t supported. Spending thousands on a new bike isn’t an option. Please support your loyal members and undo the line of code that ruined Zwift for those of us with Precor bikes that used to work last week.
Same with my Precor bike. The update killed it.
Does 1.33.2 not resolve it?
copy- I played with it last night, the auto-brake is still very grabby at 0w / 0rpm. What’s the dev take on incorporating a toggle for autobrake on/off?
I can guarantee you that at the moment, auto braking will only come into play if you are doing less than 27km/h and stop pedalling (it assumes you want to stop).
Above that speed there is 0 auto braking.
27 km/h? Well, maybe that’s the issue. Perhaps set it at 15 km/h, or maybe even 11 km/h.
Okay, that would make sense, where I was playing with it it was just spin up and seeing how it would catch was definitely below that threshold (agree with @Nigel_Tufnel it seems high). Interesting logic though, 2 questions:
- Could we be given the option to toggle it on or off? set a delay?
In theory we could, but given the list of priorities and things to do + the amount of work to do that, I wouldn’t hold my breath waiting for that option to come. Because essentially this was a problem when you were in a group ride (robo pacers for ex.) and wanted to coast for a bit. I don’t see this being a problem as it is now…
- If it is speed triggered, does that impact climbing (or really any gradient >1%) as well?
It’s not only triggered by speed, but also by power. You need to stop pedalling. And yes it also happens on climbs.
From being a Zwift Beta back in 2015 and a competitive racer, it was a huge blow to the UX in my experience when it was added. It’s like having your avatar ride without a helmet, it’s a virtual space- there’s some allowances to be afforded. RGT has never implemented it, but did implement speed limiting in corners (where it isn’t physically possible to go a certain speed) and the UX from a ride quality perspective is much more conducive to indoor riding.
I would humbly ask that an ‘issue’ be captured for a toggle, assigned ‘feature request’ and prioritized in the backlog to at least track for possible closure.
I still don’t understand. What is the actual problem we are debating here?
Having the game mechanically bring you to a stop when you don’t intend to stop, but coast for a period of time [speed agnostic], is not desired.
Following my complete ANT+ device dropout on Monday, and then issues today I’m more convinced things went awry with ANT+ this release.
ANT+ connections have been rock solid for me over 7 years and three different houses.
When I start Zwift, my Neo and HRM always pair instantly. Cadence needed waking up first, but then paired every time.
Until now. Today when I started Zwift, none of my ANT+ devices paired. When I clicked the button to find devices, nothing was found on an ANT+ channel at all. I had to pair everything over Bluetooth. All my ANT+ devices were picked up just fine by my head unit.
Bluetooth worked, but is not my preference so I hope the ANT+ issues get resolved.
No ANT+ issues for me, maybe your ANT+ stick died? Does Zwift recognize it with the glowing icon?
Yes. It was working yesterday, and I have two ANT+ dongles in my PC. It’d be unlikely both of them died.
A highly unlikely scenario indeed.
have you tried updating the driver?
Not specifically, but ANT+ has been stable on my PC for years, I haven’t done any recent updates, and ANT+ is working with other software. I do think the more likely variable in this equation is the latest Zwift update, since after years without issue I’ve had two major problems since 1.33 came out.
But I’ll investigate more tomorrow, next time I’m down in the garage. It’s too cold to want to spend time in there troubleshooting right now.
Given that there has dearly been issues with Bluetooth pairing of certain devices I’d say there’s every likelihood there are some ANT+ gremlins lurking.
I doubt you’ve had a failure of your hardware.
