I’ve just done a clean install of Windows.
Installing the app took an age compared to normal and taking into account the clean install the load time for Zwift isn’t anywhere near as quick as it was the last time i did a clean install.
I’ve just done a clean install of Windows.
Installing the app took an age compared to normal and taking into account the clean install the load time for Zwift isn’t anywhere near as quick as it was the last time i did a clean install.
I have had similar issues, lot of Dropouts via Bluetooth. After reinstalling the all-in-one VCredist Package it wasn’t fixed. Switching to ANT only Communication between Trainer and PC, I had some drops every ~5 Minutes. So something else was wrong.
It turned out, that one of the BT Antennas of my PCIe BT Card was faulty. After fixing the WLAN Cable for 2,4GHz, its stable now.
But if I have a mixed configuration in the pairung screen, like BT (Power) and ANT (controllable) to Trainer, drops reoccur. So I prefer BT only connections.
I didn’t realise at first but my connection had switch from the companion app to bluetooth directly from my PC. I used the Wahoo app to put my phone somewhere close to me where I got full bars. Using the companion app I have been getting a more stable connection again. I am interested to see how ANT+ compares though. Going through my PC’s bluetooth directly I always seem to get drops. It never seems to be an issue with other devices, but always seems to be issues when using the trainer. I have a cable for the ANT+ device, so I will be able to put it right under my bottom bracket when it arrives. Noticed aftewards one of my antennas was actually loose on my PC as well, curious if it will help now that secured better.
Just a follow up note/edit. Switching to ANT+ significantly improved stability for me. I noticed though that the issues I was having seemed to usually happen when I paired both my HRM and trainer through my phone. Using just the trainer alone seemed more stable. I am using a Pixel 6 at the moment. ANT+ paired immediately, and I haven’t had any connection issues yet.
2 weeks later, and the ZwiftGPS maps are still not updated.
I would actually like if they give access to Jesper from ZwiftHacks.com. He is always proactive with these things.
Myself and several others on this thread are also experiencing the same thing! It happened on the Rooftop KOM reverse and Railway Sprint reverse, both of which are not timed but are timed in the forward(?) direction.
I saw this on an iPad, game version 1.31. Haven’t tried on PC yet.
It does it on all platforms
This has never been the case for me. It always defaults to the first club in alpha order and I’m always having to select from the drop-down.
I actually regularly experience several issues with the club select feature.
Another 2 weeks, and the ZwiftGPS maps are still not updated.
Who really does the maps on ZwiftGPS?
Another week.
46 days since release.
And the ZwiftGPS maps are still not updated.
I guess I should not expect more.
It took well over 2 months, if I recall correctly, to get the Watopia map updated when the short connector routes were added.
Isnt that a 3rd party add-on? Maybe you should ask the developer?
I would if I really knew who did it?
There’s some uncertainty.
@Eric_Schlange_ZwftIn probably knows the answer
@Gordon_Rhino-Racing recently mentioned that WTRL is involved…
You posted in the wrong thread.
Should have posted in the 1.32 December thread.
This is the correct thread. The lack of update to the ZwiftGPS maps follows the launch of the Urukazi extension to Makuri which launched in the November update.
Gives them an excuse to ignore it though.
Both threads are wrong if you know that Zwift has nothing do do with ZwiftGPS.
We all know full well that ZwiftGPS is a 3rd party website that people use to enhance their experience while using Zwift. Presumably the creators of it must read these forums.
Go have a mince pie and have a merry Christmas.
They may circulate in the forum but not in this outdated thread for shure.
The one who asked the question did not seem to know it. Hence my answer.