Thanks for reporting this and sorry about the issue - we’re looking into it. It looks like a very rare crash that is happening to your device with significantly higher frequency for some reason. In the meantime, just to rule this out if you already haven’t, could you please try doing an uninstall and fresh install of Zwift?
Confirming we are currently looking into this 
3 Likes
I think I saw that the other day as well - but I wasn’t doing a pacer ride.
Ever since the latest update (using Apple TV) I no longer get popups on my ride of things like race results (upon finishing a race) or completing a route badge. Just completely gone.
Windows 10 pc, fails to load blue zwift screen after launching zwift. Happed the last 2 days. Have to cancel the load screen and exit. Relaunch and it works.
Hello Evan,
I got an E-Mail how to do the Re-installation properly like you showed and everything is working now
Thanks for your help!
1 Like
Tangentially-related, is it feasible to add a setting to pick which monitor to use in a multi-display setup? It’s not super reliable that a non-primary display will always keep Zwift when having other monitors turned on or off (sometimes I want my non-Zwift display on and sometimes I want it off, if my Zwift screen isn’t set to default it often will take over my other screen)
I noticed yesterday, while riding the Island Hopper Route, the mini map in the top right kept reverting back to the zoomed in view.
I assumed I must have inadvertently tapped the mouse pad on my laptop but it occurred several times.
The rider arrow seems magnified out of proportion in that view
I’m on Windows 10.
Long-standing issue in areas of Makuri, unfortunately.
Yes, something like the destination you selected no longer exists. Meantime on another pacer ride today with Yumi, I had the same experience and needed to teleport back to the group about 3-4 times over two laps of the route.
Pen exclusion still not working in Tiny Races, joker has been 325+ after winning first two races in zone 1 pen E.
How is pen exclusion meant to work? It seems to be working in other races. I’ve seen people signed up for who have gone above the limit before the race has started, and none of them have been in the race. I know that’s not at all definitive but I saw them in the races previously.
It’s hard to tell if you’re not the one impacted, and it requires a particular set of circumstances to test.
The results still don’t seem to be finalised until 12 hours after a race, so it could be that these gains are being treated as provisional and the exclusion isn’t being applied.
Does it currently work for people who have pushed their floor above the pen limit?
ZwiftHQ announced ~3+ weeks ago that pen exclusion now works for Tiny Races.
So in pen E, it is supposed to check if a racer’s score is over 260 when they try to enter the pen and prevent them joining, even if they signed up to pen E when their score was under 260.
The check is supposed to happen before each of the four races, with ZwiftHQ having speeded up the post-race score adjustments after each race 3+ weeks ago.
This week’s outstanding joker was ~246 before race 1, but after 1/1/4/1 results, went 325/334/340/355.
At least seven others pen E racers breached 260 during the zone 1 quartet, completely changing the race dynamics, even if @Eric-Schlange-ZI DQs them for race 4 or all races later today.
It’s not just a pen E issue, but I focus on that, because it’s supposed to be the pen for the weakest racers and it’s the one I compete in these days.
It’s bad enough that the strongest racers with a score under 260 are stronger than those in the weakest pen (D) under Category Enforcement, without jokers bypassing the pen exclusion check by running an old Zwift version and/or the coding by ZwiftHQ not working.
There has been no public acknowledgement by ZwiftHQ as to the reasons the pen exclusion is failing for at least Tiny Races.
The issue has been highlighted in this forum for 3+ weeks.
If it’s simply racers running old versions of Zwift to bypass pen exclusion checks, surely an emergency update can be issued that forces all users to run version 1.82 or higher to join a race pen.
1 Like
They announced that pen exclusion was live, and they announced that the score changes for Tiny Races would be more accurate - taking the cumulative changes into account - before the finalizer runs 12 hours later.
I don’t recall them saying specifically that the pen exclusion would be working correctly for Tiny Races.
Gut feeling is that they’ve coded it to only exclude people who have gone over on their finalised score to avoid an edge case of someone being excluded based on their provisional score, only for that score to change after more people cross the line.
Score Floor seems to come into effect immediately - I’ve seen people’s score change during a race after they’ve attacked early and left the field behind. So the exclusion may be applied in that case.
I agree that it should work as you’re saying. I’m just curious about how it’s been coded, and whether the coding matches the intention.
The joker that brought about my posts this morning set new seed floor scores at least twice in today’s quartet, including race 1.
So did several others in pen E, just looking at the full race 1 results above.
Why aren’t the elevation HUD settings part of the release notes? And also why isn’t it what everyone was asking for instead of this
3 Likes
Apparently it was released by mistake.
Posted in another thread.
1 Like
Hey @Steve_Cl - thanks for raising. It looks like the pen enforcement mechanism does not always work as intended for back to back races like Tiny Races. In the case you raised, this was not due to an outdated game client. We’ll look into making improvements here.
4 Likes
Good suggestion, thank you! I’ll share this back to the team.
1 Like
Cross-posting an update here from the dedicated thread about recent issues with Zwift Companion connectivity on macOS:
1 Like