I’ve noticed that the interaction between Zwift Companion and Zwift itself when it comes to the left/right/go-straight commands as well as the U-turn command are very very flaky.
Currently I’m running Zwift Companion 3.37.0 (1258) and Zwift 1.27.0 (101324) and what I notice is the following:
U-turn command from Zwift Companion does not work at all
Turn commands sometimes do not work at all
Turn commands sometimes work only once (can’t change after making a choice)
Turn commands sometimes work normally (can change multiple times before hitting a turn)
It seems that with the latest update of both Zwift Companion and Zwift this functionality is broken and that’s kind of a bummer.
Is there a way to downgrade my Zwift version and/or Zwift Companion version?
If you’re on Android, it’s possible to sideload an older APK of either/both. Companion app being the easiest. This wouldn’t be supported or recommended by ZHQ though.
Yeah, I noticed this too. The direction arrows appeared but pressing them didn’t affect the direction in game. Reloading the companion app seemed to help bit not sure how long for as I didn’t try and turn untill near the end of my ride.
For the last couple of weeks, the U-Turn button on Companion seems to take two long presses (rather than one) to register and turn my avatar.
I also had the issue today where the straight direction button on Companion did not work despite multiple presses. I used the mouse on the computer running swift to register the direction change.
If anyone from ZwiftHQ or Zwift Dev Team is reading along, I’ve found this in the logs:
[14:30:48] Manual Selection Branch - Direction STRAIGHT at Marker 0 on Road 0
[14:30:54] Route decision completed!
[14:30:54] Actual Intersection Marker Id: 0, Route Intersection Marker Id: 0, Route: Big Loop, Current Lap: 0, Route Complete Distance: 4260380.0000, Intersection Index: 0, Check Point Index: 1
[14:30:54] Route Decision State: OFF ROUTE, Script Turning Direction: LEFT (1), Actual Turning Direction: STRAIGHT (3), Script Moving Direction: FORWARD, Actual Moving Direction: FORWARD
[14:30:54] Allow U-turn: YES, Force Follow: NO
[14:30:54] Route Decision: Staying on same road
So Zwift did receive the command that RoadCaptain sent it but it chooses to then ignore it and staying on the same road as the last log entry indicates.
Corresponding RoadCaptain logs:
2022-07-24 14:30:40.446 +02:00 [DBG] Received command type TurnLeft
2022-07-24 14:30:40.457 +02:00 [DBG] Received command type GoStraight
2022-07-24 14:30:40.463 +02:00 [INF] Game state changed from OnRouteState to UpcomingTurnState
2022-07-24 14:30:40.467 +02:00 [DBG] Transitioning from 'OnRouteState' to 'UpcomingTurnState'
2022-07-24 14:30:40.472 +02:00 [INF] Executing turn "GoStraight" onto watopia-bambino-fondo-002-before-before-before
2022-07-24 14:30:40.477 +02:00 [DBG] Sent 27 bytes, 27 sent so far of 27 total payload size
I had this issue tonight. Joined D. Draft but didn’t want to ride up the volcano, so navigated away from the pace partner. From then on I wasn’t able to make any turns with the companion app running on my iPhone 11. Eventually realised I could still make turns using the Apple TV remote