Observed on multiple Windows 10 PCs running Zwift. Two entire buildings disappear and reappear on Crit City; one on the left after the esports arena, the other also on the left at the top of the KOM, just after the banner. Appears to be the same building style with the white render feature to the ground floor in each instance. Screenshots below from a stream last night, so game is on the latest version. Timestamped videos included too, though not sure they’ll work embedded.
Possibly, an artifact of Zwift’s graphics engine rendering algorithm: a decision is made which objects (=buildings, etc.) to render based on rendering complexity and available CPU/GPU processing power (=frames per second).
It does make building disappear at times, then re-appear (and am not sure I follow the logic…)
Have you noticed bikes/riders disappearing from a (big…) group ride? Same idea.
Been mentioned before by multiple people including me but thought I’d log it. If you want to figure out why some people are getting random crashes, probably start with stuff like this.
I noticed some strange effects like that when I was on Yorkshire last week trying to get some route badges, particularly with slow loading of the route ahead (seen in your second last image).
I was using latest Zwift at the time on Mac Pro 2010 with macOS 12.6.1 with AMD RX580 8GB, Dual Xeon X5690 CPUs at 3.46ghz (6 cores each) and 96GB ram.
It’s clearly not related to specs, but the platform as a whole. My point is that it’s easy to see why all that stuff popping up on a lower end system could be very problematic. Likewise if the game is looking in the wrong places for things, such as the paths being incorrect for no apparent reason. If it’s symptomatic of a wider issue then it needs looking into.
I’m wondering if the switch to Metal on Apple platforms has a part to play in this; if the previously unified development is gone.
I wouldn’t expect the Metal for Mac platforms is to blame, things like different textures showing where they shouldn’t be means probably that resource is being called twice.
I don’t know inner workings of Zwift but I have done game development before (3D models and texture mapping).
I just mean if they’ve taken their eye off the ball, not the Metal stuff per se. Yorkshire has been around ages and they’re not expanding it, why should it suddenly go wrong? Hints at a bigger issue IMO.
I know its getting off topic for this thread, but this is what mystifies me about major Zwift bugs - they don’t seem related very often to anything that has been added/changed in the update. Its the same as the recent major bug with the challenge completion popup for example (but the same pattern is seen with many other bugs too) - Zwift hadn’t just released the challenge or the bike unlock function (or made any changes to it I saw announced), the challenge had been in place for years, so why did it suddenly break? It seems so odd that stuff keeps breaking in Zwift updates in areas that aren’t even related to any new features.
Its like a surgeon who’s carrying out an operation for an in-grown toenail and somehow manages to lop the patient’s head off.
Riding in Urukazi today, the trees were dissolving and shape-shifting. As you approached them, initially deciduous/leafy trees first started to dissolve/speckle/pixelate and then shape-shifted completely as you got nearer into palm trees!
I doubt it is relevant but I am on ipad Pro, iPadOS, latest version of both the OS and of Zwift itself (updated yesterday and checked for updates before ride today).
Screenshots below of the sequence, with the area I’m trying to highlight “zoomed”/superimposed to make it clearer. It seemed to happen persistently (across multiple laps) and also for all trees.
I have to say this one did amuse me… but is still ridiculous
