I have it freezing on Apple TV when trying to start the trial. I also tried restarting Apple TV but it’s still crashed on the same screen. I can’t get past the trial screen. Latest software on Apple TV.
This is an old bug, surprised it’s still around
Also not HIPPA
Try deleting and reinstalling Zwift. What model of Apple TV is it?
minor addition to this I just noticed; Antarctica flag changed as well:
It’s doing this in miles too, not just KM! I do a lot of structured workouts with quarter mile intervals and this has been frustrating.
Thanks Steve - that worked!
Only shows tenths of a mile. I have to use companion to see hundredths. What’s going on?
Hey @_Geralt_of_Rivia - Did you see a countdown at all? If not, were you around other people at the times you attempted to use it? To use it, you have to have at least 1 other Zwifter near you going the same direction.
Check out the FAQ here: Coffee Stop FAQ
Is this the right place to talk about persistent dropouts since the update? Sampling from my team’s recent experience shows that it isn’t device or trainer-specific.
I had eight dropouts in a single TdZ ride yesterday (200ish people), including ANT+ and BLE, my trainer, pedals, and HRM. I know there was a recent Windows update, which I installed, but others on the team are on macOS and iOS.
So this really starts to feel like a zwift issue that has been crept in?
No countdown. I was in a small group of riders for most of the ride. It never became available to me.
I’ve not had any at all and have been on the new update for multiple rides since January 8th
Not to discount that possibility, but I’m running the game on Windows 10 with a TP-Link UB400 adapter (Bluetooth 4) on an extension cable, haven’t seen any problems. I’ve had a brief dropout perhaps twice a year on that system.
@catevaa
Thanks for calling that out. This will return to expected behavior in the game version 1.82.
Hello everyone,
We’re releasing a patch for macOS machines in phases.
We’re working on this
Let’s stop with this attitude and try to help ZHQ make the product better. We get it, they messed up with the communication. Let’s move forward and give them our feedback about the product. I don’t care if they let me know or not, as long as they fix it. PD5 has issues and we told them that. Leave it at that.
It’s easier to give productive feedback when we know what they’re doing specifically. DavidP was great at that and PD4(.1.1) ended up in a pretty good place in large part because of his engagement with the users. PD5 is a black box and all we know is that some employees had it assigned to their accounts for a few months before it went live, but given how little serious use takes place among ZHQ employees they didn’t get much actual feedback. @Jon is level 38 if that tells you anything.
Sometimes blind feedback is also very useful. Perhaps they wanted to see if anyone would notice the change. I think we’ve made it very clear that something was off and later learnt that there was a new PD at play. I am sure they’ve learnt something from that.
What benefit does it serve to ask ZHQ to admit to their lack of communication? It’s clearly a very lean team and I rather have them work at actually improving the product.