Since last update I ride less (w/kg) than half of watts I am riding. I weigth 68kg and for instance with 200w my rider goen less than 0.8 w/kg. Could be related to this update? I have reinstalled zwift and updated trainner but does not work. Any other with same bug?
It sounds like your weight is set wrong in Zwift. Please check that in your settings.
You might have hit this problem - Weight setting wrong on Companion app
1 Like
You are right. I had 68000kg! Too much for riding. 
thanks!
2 Likes
Canāt the app/program check to see if someone has entered a really high number? Why not set a weight limit and if itās greater than say 200kg it asks the user to enter the weight correctly?
3 Likes
Wasnāt sure where to put this but itās something Iāve seen a few times recently. Not had time to try and replicate it. 
Setup: Win10, Neo 2T & Wahoo Tickr both paired by ANT+ (FE-C for the trainer, with legacy ANT+ disabled). No other devices broadcasting or receiving. Companion app running on Android. Latest versions of everything.
Typically everything pairs automatically in a couple of seconds and advances to the home screen; this has been the case for years. However a few times in the last couple of updates, my HRM doesnāt pair and isnāt even visible to Zwift, despite me doing nothing different. The battery is new, I know the HRM is broadcasting, and it works fine when it pairs normally. The only thing I can think of by way of a reason (and this could just be coincidence) is if Iāve got the Companion app up as the game loads, and it goes into game mode straight away. The reason Iām thinking it could be this, is that the Bluetooth icon rings are pulsing, despite my Bluetooth option being set to āuse built-inā, as default. The PC does not have Bluetooth, Bluetooth isnāt enabled on my phone running the Companion app, and thereās a yellow warning triangle over the Bluetooth icon, so I really donāt understand why itās pulsing. If I force close the Companion app, the pulsing rings go away. I still canāt find my HRM though, until Iām in a world and riding.
At no point have I ever used the Companion app to bridge, nor paired the HRM via Bluetooth, to anything. Itās as though Zwift stops searching for ANT+ devices if the Companion app is in game mode early enough in the device pairing process because it assumes you will be bridging - but this only seems to affect my HRM and not my trainer. Perhaps it still searches for ANT+ FE-C, and itās only legacy ANT+ that it stops searching for. I can use the Companion app normally if I pair it to the game after my devices, and often do.
Identical issue being experienced, with some slight differences.
Setup:
Ipad Pro 12.9 (M1), iPadOS 15.4.1, Wahoo TICKR FIT HR Monitor (firmware 1.0.13), Wahoo KICKR Core (firmware 1.1.13) Companion App running (iOS version 3.34.0)
TICKR HR and KICKR Core always connected to iPad via Bluetooth.
KICKR Core always pairs without any issues, TICKR FIT not pairing as per above issue and ONLY started doing this after latest game update.
Never used ANT+ for anything.
Cheers,
Chris.
Yet another bug report here and this one is cross-platform. Details cribbed from one of my other comments.
Datapoints:
-
Tacx NEO2T with current firmware, Polar H10 HRM, I double-record on a Garmin Fenix that ālistensā for the ANT+ signals from all devices. (it is NOT set to control the trainer, ever)
-
Devices running Zwift: Windows 11 Pro laptop that was new as of last week, very clean and up to date. (Core i5 11300h w/Nvidia RTX3050 - it ran Zwift beautifully when I first tried it) and an AppleTV4k with Gen2 Siri remote. The laptop has a Garmin ANT+ USB stick, BLE has never been connected to anything but a mouse.
-
In both cases, theyāre hooked to a Samsung 4k OLED 32" TV with WiFi and BLE disabled - it acts as a ādumbā TV - using Zeskit Maya HDMI cables.
-
Companion App on a Google Pixel 5, NEVER used as a ābridgeā. This had Spotify playing to a set of BLE earbuds, as always.
-
No WiFi range extenders, nobody else in my household thatād be stealing bandwidth - my router (a well-rated, reliable ASUS) is on the wall in the pain cave about 3 meters from the Zwift devices so it has a clean signal.
First ride: rode with Diesel Pace partner in Makuri on the PC laptop. Got 8.94km, 15:44ET into the ride, tried to sprint, first noticed HR wasnāt connected, followed shortly thereafter by power/cadence, and the pace bot and pack passing me. Activity here.
Second ride: tried AppleTV4k via BLE (no Companion Bridge, though I always run Companion). Got 1.3km, 3:35ET into the ride, same dropouts, these of course BLE not ANT+. No activity evident in log as it was too short to register.
Third ride: unplugged NEO2T, restarted the AppleTV, plugged NEO2T back in, went into Zwift on ATV, reconnected. Did a 26km, 49:37ET Diesel ride in Watopia and it stayed connected. Activity here.
Something screwy is going on. Nothing in my RF environment has changed. Only change has been the Zwift update last week.
Duration seems way off on the new routes. Three Little Sisters in under 30 minutes is over 74kph avg speed. Eastern Eight under an hour is in excess of 51kph. The others donāt look correct either.
1 Like
FWIW Iāve been avoiding having Companion going when launching the game since I noticed the HRM anomaly and itās been absolutely fine. Same quick and reliable pairing over ANT+, same low rx fail numbers, and zero dropouts - just like normal. Still not tried to replicate it, but it definitely feels like it could be a logic thing where the game is making incorrect assumptions about pairing methods.
A post was merged into an existing topic: New Zwift Home Screen Update [April 2022]
I am just wondering, how do I do just a regular ride in Watopia? Before the update, I would āJust Rideā in Watopia- this ride included a couple of short sprints, some hills and flat stretches and it was perfect. In two hours I would ride close to 60km and I loved it. I donāt know how to get back to that old Watopia āJust Rideā route. Today I tried doing the āLarge Watopia Loopā- canāt remember exactly what it was called, but I only ended up covering 40km in two hours when I am used to almost doing 60. I am planning on riding 180 in two weeks and I want to do that on the old just plain old Watopia āJust Rideā route. Which of the new routes will be most like the old standard ride in Watopia? If you could let me know which of the new routes to pick so that I can cover the same amount of km as I used to, I would really appreciate it. Thank you!!
Hi @Liza_Crawford, the old UI remembered the last route you had chosen, so everytime you logged in and hit ājust rideā it would put you on the same route. There is no āstandard just rideā route, you were on the flat route (I looked at some of your old activities to figure it out).
Sounds like you havent explored too many of the routes in Zwift, i encourage you to spend some time looking around and trying out some new roads.
1 Like
Hi Guys,
I have a problem with Zwift in the new laptop with Windows11.
At the beginning everything was fine after updating Zwift 1.1.4, Windows and Nvidia graphics, the application doesāt want open. I reinstalled the applications and nothing has changed ZwiftLauncher.exe also doesāt want open. Any suggestions ? I will be grateful for your help.
Not sure if this helps, but maybe youāre missing something:
Unfortunately, I canāt go back to Win 10, I donāt know why.
Still doesnāt work. I checked everything.
Thank you for your help.
You donāt need Win10.
The point of the link is the command winget aka Windows Package Manager for installing, updating, etc., software packages in Windows. It is part of both Win10 and Win11.
Everything is updated.
You should train to time/duration and not distance. You can do 60 km on the flats in 2 hours or 40 km in the mountains in two hours or 10km in the Zwift dirt in 2 hours. The important metric here is your duration. Most cycling pros will train for a 3-8 hour ride for example. Distance can be cool but there are too many variables wrapped up into it.
ERG Mode gets stuck after finishing a workout and doesnāt switch back to SIM riding with this update.
Verified with Kickr18 via Bluetooth connection.
Itās been working fine for me, Windows 10, Kickr Core, ant+