No, Nigel, this is definitely not the intended behavior and this bug is new. You have the u-turn button in the menu and you have to press this button for several seconds before doing a u-turn. That is the „normal“ way to do a u-turn. The other option is using the ZCA where you also have to press the button for several seconds.
That is true, but that doesn’t mean that is the intended behavior when using the ATV remote. I can also turn at intersections by swiping across the touchpad of the ATV remote in the direction I want to turn, but that is not the same as how it works in ZCA.
I’m not saying that it is a bad idea to change it, just that this likely isn’t a bug but the intended action from the designers.
With both options you have to press and hold the button and now you can do a u-turn just by tapping the sensitive area??? This can‘t be a feature. Something went wrong in the December update.
Wahoo RGT requires you to hold the turn around button for 5 seconds to turn around. I don’t have the same issue on Wahoo RGT. This is definitely a Zwift problem.
The key phrase there is “I don’t”. This doesn’t mean that everyone wants it the way you do. Again, I am not saying that things in Zwift couldn’t or shouldn’t be changed, just that just because you think it should be different doesn’t mean that everyone, or even a majority, want it changed.
Thank you for your contribution to the topic. Unexpected u-turns are a great feature, many people love it, especially while working hard to get badges.
Wow! I’m only noticing this thread today for the first time. It’s June and 6-7 Zwift releases later and this is still not fixed. I didn’t even realize it was a bug until seeing this thread. But, now I know why I often suddenly do a u-turn when I grab the remote to end a ride.
I use ATV almost exclusively and have never had an unexpected u-turn. And, AGAIN, I didn’t say it couldn’t or shouldn’t be changed, so you can direct your sarcasm elsewhere.
Good talk.
With the latest changes to the ATV remote control (Game Update 1.29 [September 2022] - #77 by evan-zwift), the bug now seems to have been fixed.