Black Squares Game [1.40] [1.41]

After doing the 1.40 Zwift update this morning I started to see these black squares while riding in Zwift. My wife got them also while riding in a different computer and trainer. We’re on Windows 10. I thing is a bug related to the tail lights. Asked other while riding and some responded that they also were seeing them. Below is a link to a Youtube video I did showing the problem.

Black Squares While riding with RoboPacer

1 Like

I had the black square visual artifact either yesterday or the day before. Happened in the middle of Watopia daytime so I don’t think it was taillights.

I’ll add that this happened on one of ~6 rides since I started so it’s infrequent. Haven’t figured a common thread.

Multiple reposts of black squares on FB as well.

Still waiting on that answer! Just started happening to me. Fine in War then 1 min later black boxes in Neo

This one’s back!

Large black squares pop up in the middle of the group pack on my windows 11 machine. Just started with.
1.40 update.

Thanks, I’ve flagged this with our team.

I had this tonight too, started with Robo Pacer after a good 10-15mins and got worse and worse quickly, it continued when I joined a race pen but then stopped with a game reboot (not PC reboot as I didn’t have time) and never came back even when joining Coco again for 20mins after the hour of racing.

I had this today, Zwift on Windows.

It appears to be related to the number of avatars being drawn. In my case C pacer about 70ish participants. Up to a half dozen squares at a time.

Backing off from the group and the number of squares dropped.

One of my events (Tiny Race) also had them.

Restarted Zwift after that, and it worked ok for the next hour and a half.

Same here, I was just on the Saturday Donut Ride with the HERD and the black squares were really bad in the bunch on the reverse titans kom. Video attached.

Also when we got to the end of titans, a number of the riders turned left unexpectedly and were lost to the desert…

Fixed in 1.41.

Sorry folks, this one is a bit annoying.


Since the latest update that I got yesterday May 20th, I get random flashing black square on screen.

Not full screen. Always above the riders. But not always the same place according to my position.

On Pc. Windows 10 up to date.

Is this a know bug ? See pic. I was able to get a pic with the black square. Not easy at it flashes non stop.

I’m not one to join the Zwift bashing but it does baffle me how something this blatant and widespread makes it out on a release which was all about fixing the last bugs…. :man_shrugging:t2: it’s tough to defend I’m sure.

Perhaps it’s not as widespread as you might think. Sure there are multiple reports but what percentage of Zwift users aren’t affected?

People don’t come on here to post that they haven’t got a particular bug.

Although out of interest i don’t have the black square bug.

Several posts on here, several posts on different FB groups, many people complaining of it on the in game chat…… seems widespread enough to me that it should have easily been picked up prior to release.

As I said I really am not one to complain normally but this just seems pretty basic I’m afraid. :smirk:

It’s not widespread. I’ve Zwifted for about 4 hours since the release and only seen this for about 5 minutes.

I think certain conditions have to be met for it to be visible.

Anywhere in the dark/dusk so the rear light is on; on a PC is pretty much all you need as far as I can tell……. I’m repeating myself but really not a lot of testing needed to catch it. Just silly given the mess of the last release.

I think you have made your point.

I think it’s rather widespread. I did an hour and a bit session yesterday and it bothered me as well. The thing is intermittent and only small percentage of affected users will be annoyed enough to post about it on reddit/fb or here. I wasn’t going to complain till I found this thread were Zwift employee is playing it down. Anyway I understand there’s been a lot of code changes recently and bugs can happen. Just this one is very annoying and should’ve been detected during testing.

1 Like

I’m not playing it down - I said it was an annoying one, but I also gave an example from my own riding of how much time I actually had the issue for.