^ Only one way to know for sure!
Hi @Silly_Bugger
Yes a number of people (including myself) experienced this last week. A few more people experienced it this week after the latest minor release. Appears to affect both the
Four horsemen route
Uber pretzel route
There is a large discussion about it in the bugs and support section.
So far weāve had an incredibly underwhelming response from Zwift (ie they claim they can do nothing about it), and Iām not holding out for any better response from themš¤·āāļø
Incredibly disappointing.
Zwift has always consistently said that they can not award badges after the factāi.e. you definitely shouldnāt hold out for a different/better response about that particular aspect of the issue.
Worked fine now for me on France. Huge relief as Iām riding Ventoux often.
Thus adding to a negative user experienceā¦ Great way to keep customers happy
Their ātechnical limitationsā excuse is complete rubbish. Itās more a case of ācouldnāt be botheredā.
A flag against the userās account on the database is not complex work. They have the technical capability to do so - this is basic database stuff.
@Jim_Mattson this recent situation has definitely made me agree with you!
They still have not fixed the route badge for Surrey Hills. I wrote to them a couple of months ago since Iāve ridden that route many times and have never been awarded the badge. The reply I received said that I would automatically receive the badge when it was fixed in an āupcoming releaseā. Rode it again after the latest release but still no badge. Guess āan upcoming releaseā could mean sometime in the next several years ā¦
To get this badge, I set it up as a meet up. The meetup started me in London and I then had to climb to the top Fox Hill where the route officially starts. The meetup actually finished on the flatter sections between the bottom of Box Hill and Fox Hills, but the badge was not triggered until I reached the banner at the top of Fox Hill (ie I had to climb it twice).
A larger number of us are experiencing own route badge achivement issues with the āFour Horsemenā ā¦others cannot get it with the āUber Pretzelā - the replies we have received from Zwift have been underwhelming to say the least, saying ātechnical limitationsā preventing the badge from being awarded after the fact. Obviously this is complete rubbish and itās ridicuous Zwift actually believes people will accept this excuse
(just applied the update) I never had issues connecting over bluetooth with the companion app, now I canāt zwift anymore because the connection keeps getting dropped
Kickr Core
Wahoo Tickr
Wahoo Cadence
What platform are you running Zwift on? Seems more likely something went wrong with the update and a reinstall is worth trying.
Windows.
Reinstall seems to work! Thanks
For Surrey Hillsā¦
The meetup started me in London and I then had to climb to the top Fox Hill where the route officially starts. The meetup actually finished on the flatter sections between the bottom of Box Hill and Fox Hills, but the badge was not triggered until I reached the banner at the top of Fox Hill (ie I had to climb it twice).
Canāt tell if youāre just giving info or suggesting that the route was wonky, but Surrey Hills always begins on the London side of the river, then you climb Fox Hill for the first timeā¦ and then (after doing the other hills) you have to climb Fox Hill again at the end to get the banner. Thatās the standard route. If you already knew this, just ignore this paragraph
In other news, itās one thing to have an issue the first time you try to complete a route like the Uber or the 4 Horsemen, and you donāt get the badgeāyes, itās a frustration; make a post and complain to Zwift. But after that, when itās already a known thing that there is an issue with these routes, and itās already a known thing that Zwift has always consistently said they will not award badges after the fact, then it becomes a little bit strange (a) for folks to keep trying to ride these routes in the hopes of getting the badges prior to any fix having been announced, and (b) for folks to keep complaining that the badges arenāt being awarded after the fact
Havenāt had any issues with Zwift since starting using it years ago. Since this last update itās has crashed and also will not let me log back in, says script errors or something like that. After several tries it let me back in but then would not recognize password. I really like Zwift and hope they get things right soon, cause all these issues might get people to to start looking elsewhere. Seems like every time Zwift does an update it makes thing worse. The only progress Iām seeing lately Is backwards. Hope they get things right cause at this rate they will have it FUBAR by end of year.
Obviously Zwift is not consistent in stating that badges are not awarded after the fact because they told me something different. Also, in my case, I ride Surrey Hills frequently for training and not to get a badge: I was just stating that there is still something wrong with that route.
I think that been done and still no acceptable response or resolution from Zwift.
I didnāt know this until I experienced it for myself - do you actually expect people to read forums each time they want to do a route? A new user is certainly not going to know this. Just because you claim to know all things Zwift doesnāt mean everybody else does
The fact people are still posting to the thread suggests most are only finding out about this bug AFTER they do the route - which is a rubbish customer experience.
This is what screws everyone up. I had to ride it twice before getting the badge. The lead-in is ~5km including the climb up Fox Hill to the start of the route. Then you have to climb Fox Hill again at the end to reach the finish of the route. Last I checked, this does not align w/the actual ZwiftInsider segment, which starts and ends at the base of Fox Hill vs the top. So itās entirely possible to complete the ZwiftInsider segment w/out actually getting the route badge.
Again, the start of the Surrey Hills route is the top of Fox Hill. The finish is also at the top of Fox Hill.
Unfortunately the lead requires you to climb to the top of Fox Hill which is not really well communciated and thus is likely to confuse many. To track all the routes I did I used zwifthub.com - by studying it, you quickly realise some routes have very long āleads insā compared to others.
I think these problems could be fixed with āroute startedā banner so you know where you need to ride to to finish the route.
I think I know what the problem was in my case, the official Zwift documentation for the route is wrong:
https://support.zwift.com/en_us/zwift-worlds-and-cycling-routes-Sy2_gxTGB#London
Zwift says the route is 40.8 km with 890 m of elevation gain with no mention of a lead-in (though the lead-in is included in the route animation, and the route animation ends before the second ascent of the climb begins). Iāve been riding 42 km (with 920 m of elevation) and I stopped before the top of the second Fox Hill climb.
Why does Zwift even bother creating documentation when itās wrong? Also, why did customer support tell me it would āfixed in an upcoming updateā and that I didnāt need to do anything to get the badge?
Anyway, thanks to everyone that responded and helped me figure out that what Zwift says the route is and what the route actually is is not necessarily the same thing.
This is such a horse s**t response.
The fact that itās a āknown issueā doesnāt make it OK. Once an issue becomes known, itās on Zwift to rectify it. In addition to that, their communication is atrocious.
It shouldnāt be up to the community to find a āwork aroundā and share tribal knowledge about a malfunctioning feature so others are aware.
Itās people like you that simply accept this kind of incompetence that make it easy for Zwift to turn their back and ignore known issues. We pay a monthly fee for what is essentially a beta version of Zwift. Some of us are tired of the constant bugs and broken āfeaturesā while Zwift seems to be focusing on eracing and cashing in (IPO).
If you donāt care or have nothing to add, just keep scrolling.