In the last couple of weeks, possibly since 1.80 but not certain, I’ve seen this sudden visual jumping scenario randomly but fairly often; maybe once every few minutes. It’s not related to any frame drop or CPU limit as far as I can see in the Zwiftalizer log. Seems maybe avoided in first person view but not 100% on that. I know of at least other person reporting seeing the same in all worlds.
Examples at 2:50, 6:00 and 9:02 in the YT video linked below.
On Win 10 PC, 3060Ti GPU and 13th Gen i7 CPU, 32M RAM.
Hi, @Sam_Crofts, welcome to Forums! I’m Francisco from Zwift Support.
I totally get how strange this situation might seem, especially since you weren’t switching between first-person and third-person views or anything like that, even with your great 3060Ti GPU!
In version 1.80, we added an option to turn the screen shake on or off. However, some members noticed that this option was set to Off by default. It seems that even though the setting appears as “Off,” screen shake remains active. Once you switch the setting to “On,” screen shake stays enabled, but if you toggle it back to Off, it will actually disable the screen shake feature/effect.
If the issue persists, try to make a clean fresh re-installation following the steps in this article below and keep us posted.
Thanks for your reply Francisco, but I don’t think this is the screen shake. I don’t mind the shake effect and have never tried to turn it off. Did you look at the video?! It’s not just ‘shake’ the whole visual swings around and jerks back to Center.
I noticed it this morning while riding with Maria on the Paris route. I was using third person view, best description is the camera stops moving for a moment then quickly moves forward quickly and bounces back and forth as if it’s on a bungee cord. Didn’t happen consistently tied to any place on route or group passing or being passed.
If your visual was only backwards and forwards then that is the known “rubber banding” issue that occurs as frame rates dip. This issue is visually different and swings sideways as well as back/forward or in/out.
I still have not seen this issue for the last few weeks when before it was very regular every few minutes previously.
Well I spoke too soon; this issue is back again tonight, maybe it came back with 1.83 as I updated just before the ride but either way the issue has returned for me………
This started again today; in London and after updating to 1.85. The good news is getting a video clip is now easier since the ‘none main screen’ bug is fixed so I have a short clip of one example but I can’t load it to the forum unfortunately.
@evan-zwift - I can reproduce this consistently now; oddly turning OFF one of the Play Controllers induces it as the controller disconnects. I assume something in the auto steering differences kicks in and it causes a camera swing in/out/left/right depending on whether you are cornering at the time or not.
If you read the other comments above, even if you can’t be bothered to watch some of the video, you can see it’s not the same as the rubber banding that article is talking about. But thanks.
People call it different things. The root cause could be similar, which is some odd assessment of your graphics card vs the update. Messing with config files isn’t ideal but tends to work. It also worked for the “trees not loading”.
Don’t know if this will help in your case, but I had the same issue show up at just about the same time as you. Tried various fixes mentioned in past posts (reboots, updates, frame rate restrictions, etc.) with no success. Finally decided that bluetooth was involved since I was seeing occasional HR dropouts too.
Turns out that my bluetooth adapter was picking up interference. It had probably always been there, but some change in the game caused Zwift to suddenly become sensitive to it. I use an external bluetooth adapter plugged in to a usb port. Discovered that 3.0 ports can be a source of interference with these types of adapters, so I plugged it in using a 2.0 USB hub instead. Problem solved. No visual jumping, no HR dropouts since.
If you don’t use an external adapter, a weak or compromised bluetooth signal may still be the culprit. Might be why turning off your Zwift Play seems to affect it.
I do think it could be small amounts of BT interference that causes the play controllers to drop out briefly which seems to be what causes it. But I never see the ‘DISCONNECTED’ warning and Zwiftalizer doesn’t show any BT reconnects.
Also TBH I very rarely see it occurring recently, although did a couple of times the other day. I only saw it and realised what caused it today when I started to shut things down to finish my ride and realised it was induced by turning off the controller. Repeatedly turned back on and off and it does it every time on a turn OFF.
@evan-zwift Did anyone have chance to look at this at all??
It is easily reproducible all the time now; sometimes I see it an every few mins and sometimes not at all unless I purposely turn off one of the play controllers.
Seems a brief BT drop is enough to trigger it even tho I don’t see any dropouts on Zwiftalizer, but whatever the minor disconnects are sometimes the visuals shouldn’t jump around like they do.
