Hi, last night tried Zwift play again, and had so many disconnections I lost count this time (11 last time). That and the manic darting from left to right have left them unusable. Will these issues be covered in the latest update as currently I have 2 £100 paperweights.
Ta
There are further improvements being made indeed.
The latest workaround is if you pair through the companion app (if possible) it seems to severely reduce the dropouts.
I wonder if you need the bluetooth connection antenna very, very close to the devices. Is it distance related?
FWIW - mine is about 1.5m away in front of the bike - but it’s in the back of the Mac Pro (it’s the internal bluetooth antenna that is beneath all the PCI-E slots.
i must be lucky no issues with mine so far. There is a game update rolling out right now for version 1.50 worth seeing if htat improves things.
How do you pair your trainer, hrm do they use bluethooth as well is it just the plays that are dropping out?
Bridging through the phone reduces the dropouts massively, although still some issues remain. Will keep trying
I’ve had a few dropouts/disconnects since version 1.49 and above was released, never had any issues before this update
Same here i notice more short drops of 1-2sec since the last update.
Had the left controller disconnect twice during a race last night, seems to be getting worse not better with newer versions
When the controllers do work, it seems that I don’t have the finesse to select any lane other than far left or far right. Sometimes, they pull me to the far left if I don’t hold the right steering button down.
The frequent disconnects make them pretty much unusable, though, so I guess it doesn’t really matter.
From this morning’s ride…
[7:17:51] BLE : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 223657606639612 ] Zwift Play-R EFFC
[7:17:51] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-R EFFC" changed state from 3 to 0
[7:17:51] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:20:56] BLE : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 267965180872854 ] Zwift Play-L 0896
[7:20:56] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:20:56] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:43:39] BLE : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 267965180872854 ] Zwift Play-L 0896
[7:43:39] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:43:39] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:45:10] BLE : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 267965180872854 ] Zwift Play-L 0896
[7:45:10] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:45:10] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:48:42] BLE : Sending DEVICE - BLE DISCONNECT ERROR [ UUID: 267965180872854 ] Zwift Play-L 0896
[7:48:42] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:48:42] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:49:47] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:49:47] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:54:53] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:54:53] HUD_Notify: STEERING DEVICE DISCONNECTED
...
[7:56:21] INFO LEVEL: [ZwiftProtocol] Component on "Zwift Play-L 0896" changed state from 3 to 0
[7:56:21] HUD_Notify: STEERING DEVICE DISCONNECTED
...
It sounds like this is what everyone else is experiencing as well.
Yep, that is pretty much it. Constant disconnects although they seem to have got a lot worse with every update recently. Connecting through the companion app does help hugely, but having constant swerving etc does make them pretty much useless even when they manage to stay connected. Not a £100 well spent I’m afraid
@Dappy-Muppet-TFC I found that I need to pair from the companion app but only connect to the play controllers in game…not from the initial pairing screen. So open up zwift, select what I want to do…world, workout etc, enter game. Pair play controllers. Seems to be much more stable. Not perfect but if I connect from the initial pairing screen I always get some random disconnections.
Further to the above, I changed the Bluetooth adaptor to see if this caused the issue, as from what I can gather it is down to the way Bluetooth makes requests and uses different channels (I could be speaking rubbish as I am a novice on these matters). The new Bluetooth adaptor (TP Link) has had zero issues since with direct connections ie not using ZC. Maybe it is poorly written drivers for generic cheap chipsets, I have no clue, but it seems the issues have stopped.