The reinstall fixed it. Thanks
1 Like
Average speed is an after ride value.
I find this also. It does an excellent job (accurately) making the climb harder because of my waistline, but descents don’t feel as accurate. If Im going down grades that steep in real life I’d be flying by people far more than I do in Zwift and there’s nothing they can do about it. I also feel like the inertia a decent creates doesn’t continue on as accurately as it would in real life after the decent.
Either way, I’m still pretty happy with Zwift overall. These are just things I’ve noticed.
Why? Sometimes it’s nice to focus on, or set a goal, for something that’s not power related.
1 Like
I’m feeling your pain Kenny. PD 5 is the worst PD so far. Good luck coming to terms with it cause no one seems to care. Totally makes every race a TT effort. Which of course does not reflect road cycling whatsoever. Favours the heavier rider, which I have no doubt is very deliberate. I’ve got plenty of stats to prove, but no one at Zwift seems interested. Just as well there’s other platforms out there!
I asked for this about 4 years ago. If you want to record you can’t use Nvidia ansel. Go with OBS or something.
1 Like
Adding some in in case it will help the Zwift teams debugging efforts. ZC was working fine with iOS 18.2, macOS 15.1 and Zwift 1.81. I updated to macOS 15.2. Then Zwift 1.82. The ZC app no longer displays the map when the ride starts.
Zwift is not showing in the Local Network setting on macOS and there is no option to add it. The same is true on ZC on iOS.
One oddity to note is that when ZC was showing the map on the 18.2 / 15.1 / 1.81 configuration, ZC would not exit that map view after saving a ride until the Zwift app was quit on the Mac.
I’m using a Mac M4 Mini and iPhone 16 Pro.
Thanks for taking the time to report your setup and steps @Steve_Brown9, we’re continuing to investigate on our end and will provide some updates as soon as we have them.
In the mean time, check out the official thread for this issue:
Many users have reported a fresh install of Zwift resolves this issue for them, same for a couple of Zwift employees. However, it does not seem to have worked for 100% of the users experiencing this.
Before I did the reinstall of Zwift on my Mac Mini M2, the companion app on my iPad would occasionally connect.
I don’t understand why it would work sometimes and not work other times.
This is a feature not a bug. People like to hit distance records.
1 Like
@evan-zwift
While you are fixing the “%” distance marker in Zwift Run, change it in the Companion App also.
Browsing the My List shows the distance marker as “%” also.
That as well. I believe Nvidia is now the world’s biggest company by market cap, since surpassing Apple. Seems interesting not to at least offer full compatibility.
Thanks, John
Reporting that I was able to fix the issue on my Mac Mini M4. I did a full uninstall and a reinstallation. The newly installed version (1.82) successfully asked for permission to use the Local Network resources.
After accepting the permission request, Zwift was added to the allowed application list for Local Network. The ZC started connecting again right away once the Local Network permission was allowed.
My previous Zwift installation was not fully installed since it wasn’t correctly registered for the Local Network permission–It wasn’t shown in the Local Network permission list.
I got the Mac Mini M4 about a month ago. It shipped with macOS 15.0. I originally install Zwift 1.80 on 15.0. Unlike previous major versions of macOS, there doesn’t seem to be a way to add the Zwift app to the allowed list without a reinstallation so that the app can successfully ask for permission. You used to be able to drag and drop apps into the permission list to register them if the app didn’t do it.
Anyway, thanks for the tip about reinstallation.
S
2 Likes
Two little bugs. I am not sure if someone has already reported them:
- When joining a ZRS race grouped by score, the upper right window still shows pace group which is irrelevant. This label should be suspended unless the race is split per pace group or it is a group ride.
- While the route elevation profile is very cool and helpful, often times it misses banners along the route. See the screenshot from TdZ Stage 3 Long. It does not show banners when entering he jungle and then passing downtown, which both award a power up.
4 Likes
It only shows the end points of segments you will complete on the route.
I’d much rather it show all the banners too, though maybe as a different colour to indicate that it’s only a banner and not a segment end point.
3 Likes
There was a recent comment that PD 5 was not being applied to races, only group rides and free rides.
I don’t know.
The races I have been in (all are non TT) have been fine.
Yeah, I’d much rather they show something for all the banners - mainly want to know when the next power up opportunity is so I can decide when to use the one I have, and often I’ve been surprised to need to quickly dump a power-up ahead of a banner I didn’t see on the mini-map.
2 Likes
While we are talking banners, it would be nice if at the start of a sprint segment, there was an indication of how long the segment is.
I’ve started to try to do something about my poor sprinting.
The seg along the new Coast in Watopia seem to be 500 m but the ones in London and old Watopia are 300 m.
That’s a big difference.
A green sign with 500 would mark the start and give that info.
I know it’s on the Leader board but I would like to permanently hide the leader board on my HUD.
I might even turn on my Hologram sprinter
1 Like
Just wondering if anyone has had issues with ANT+ since the update earlier this week. The first day the update installed on my MacBook - the pair screen froze whilst trying to get ANT+ connections, Bluetooth was fine. There was a second update on Thursday or Friday I think - and it seemed to work after that until my long ride on Saturday when my HRM and cadence sensor both disconnected 2:00 into a long ride. This morning, they both disconnected after 20 mins or so. Not sure if it’s a result of the update or maybe my ANT+ dongle needs replacement.
I have seen reports like that from Windows users. Not specific to the latest release. I am unsure if this bug affects Mac users but you could try the solution in this topic: