“After a week of regular riding”
… what regular riding???
“Neuromuscular ride”
… Three sisters is as far away from sprint-inducing route as I can think of; in fact, it has literally ZERO sprints, meaning it encourages ZERO neuromuscular efforts.
“leveraging your current freshness and … stable load trend”
Ignoring the fact that my load trend looks like this for the week, and Companion trends show it.
It’s still mega evident this system has MAJOR flaws, not like… some tweaks and changes.
But if it seems to think that a route that some people would claim has “endurance power level focused climbs” (Epic… since, Grade and ADZ is all Watopia has to offer for long climbs), is… a neuromuscular series of events is literally polar opposite.
Something here is just all kinds of backwards wrong.
It’s however massively concerning that it seeing my massive downward spiral trend thinks I’m not only fresh, but … that I had a week of regular riding???
Honestly this program needs to just be put back to closed doors at this point if this thing is this wrong. It was goofy when I was healthy and gave some weird recommendations, but this recommendation after a week of nearly zero riding until this weekend… is dangerous, and 100% false on every level.
Right, this is what I was saying earlier. The words don’t match the workout suggestion, the workout suggestion doesn’t match what you would expect given recent load etc. Sometimes it’s completely backwards. There are too many glaring holes in how this is working today to even call it a beta let alone expand languages to more and more people in its current state with no ability to opt out of it.
Edit: For me at least the training score, and training status tend to work most of the time. When I took time off due to sickness it didn’t seem to want to dip into “detraining” for some reason, but other than that at least those features seem to work for me.
This timer countdown popping up every 61 seconds during a next Up suggested pace partner ride needs to go away. Incredibly annoying, and would be even if it were set to 60 seconds. Could be tolerable at 15 minutes. Edit: it’s going off every minute at the :00 but the countdown clock is broken and running fast. But seriously drop the seconds and reduce it to 15 minutes.
More issues: Companion suggested an hour with Jacques and called it a threshold focused session. The game decided it should be two hours which would be absurd if it were actually a threshold effort. Jacques is a solidly low-tempo pace partner ride for me. If I actually had to match the bot in output it would still only be mid tempo.
I’ve noticed in the last few days that all 5 robo pacer suggestions in the tune menu are all set to 2 hours (where previously they’d be 30, 45, 60, 90 and 120 minutes)
100%! I just posted about this elsewhere, presuming it was a bug having jsut encountered it for the first time. I didn’t link it to my pace partner ride with Maria - I thought it was a bug related to levelling a TT bike or something.
No one needs a message every minute saying how long it left in some supposed goal, especially when it’s not even correct.
My recommendation was for 45 minutes, but the game started off telling me I had a 120 minute goal.
Once every minute is far too much. My ND brain can’t handle it. It’s incredibly distracting and annoying. A message every 15 minutes might be tolerable.
I sent an email to Zwift support using the link provided. That was several weeks ago. I still have “Next Up” displayed in the Companion App.
Ironically, one of the reasons I dislike it is because of the harmful effects of using AI, which I mentioned in my email… and Zwift replied with an AI-generated message.
Please, turn this off for me. It takes up a lot of real estate, at the top of the screen, which I have to scroll past every time I use the app.
@AlanZ Hi Alan, could you opt me out of the Personalized Recommendations - I followed the links in this forum thread, but got the same response back from the support AI as Allison Thompson reported in the "Make Fitness Trends & Recommendations Optional" topic saying it couldn’t be done blah blah blah. Thanks!
The feature really should have been deployed with an opt out selection so that us Zwift users can “self serve”…
Sharing the same note as above: due to caching it may take a few minutes for the change to propagate from our end to your client, but should be visible after logging out and logging back in.
Hi @AlanZ, could you please add me to the opt out group and remove this from showing? For all the reasons mention in this thread which now has about 390 comments asking for a simple way to turn it off. Thanks in advance!
Sharing the same note as above: due to caching it may take a few minutes for the change to propagate from our end to your client, but should be visible after logging out and logging back in.
Sharing the same note as above: due to caching it may take a few minutes for the change to propagate from our end to your client, but should be visible after logging out and logging back in.
Please just wait a few minutes for the change to propagate from our end to your client, but after that the change should be visible after logging out and logging back in.
