Anyone else bothered by that? Anyone?
By what? What?
Just for fun hereās my main rig with vsync disabled: https://streamja.com/BOJM3
Casual 50fps penalty for looking the way youāre going.
@Dave_ZPCMR Unless Iām missing something, it makes sense that fps would drop if looking at something w/moving elements vs a static wall per se. Whether or not the fps drop-off is reasonable I have no idea 
On the other hand, if this drop-off is new or exaggerated in the same circumstances w/the new updates, then something got borked 
The GPU is never maxed out on any of the videos - see the second one for proof - so the frame rate isnāt being affected by what itās having to render. There is a massive CPU load holding the GPU back, that historically has never been present in those circumstances (solo, not busy etc).
As for whether itās a reasonable impact, obviously on my main system itās not really a concern, I just wanted to show that the issue is still present and is still massively damaging the output. But on lower end systems itās far more significant because itās dropping the resultant frame rate below 60fps, where it never has before. The exception being Makuri Islands, which has always been this bad.
So, low CPU utilization can still result in a CPU bottleneck? Itās not like the %CPU moved much either way. Or is that %CPU low due to being multi-core and Zwift not making use of the full CPU capacity?
Yeah, Zwift never utilises anywhere near the full capacity of any CPU (well, apart from really old ones) so that particular percentage figure doesnāt really mean anything - unlike the GPU one which is very straightforward. The GPU isnāt maxed out, meaning it has more to give. But the system isnāt hitting the 60fps target. The bottleneck in this instance is the CPU. The point of those videos and what Iāve been complaining about is that up until the last two game updates, that behaviour would not happen to anywhere near the significance in those circumstances - if at all. And itās causing systems that historically would have been locked at 60fps to be well below it.
Hereās another example. The graphics card is not struggling here, far from it: Streamja - Simple video sharing
@Dave_ZPCMR : I know next to nothing about how computers work, but Iāve been following your commentary on this matter because I find it fascinating at some level. In reading what you are saying, and putting it together with some comments on other threads (probably incorrectly) I am wondering this:
Is it possible that with the new UI being introduced (which seems to correspond with when you began noticing issues) that Zwift is somehow running two concurrent instances of the game: one which the user sees (with whichever UI they have been assigned) and one which they donāt see (with whichever interface they are not assigned)? Sounds far-fetched, I suppose, but is it possible that there could be a Zwift multiverse, with a user only being able to see one, even though more than one exists?
Itās possibly related, and is something Iāve also speculated on because the timing seemed to match. The user interface overlay has always had a larger than expected impact on frame rates (once we could disable the HUD it became clear). However Iām starting to think itās a red herring, and the underlying issue is possibly to do with culling. Stuff like the new UI probably isnāt helping but itās as though stuff much further away than normal/required is being calculated, even though you canāt actually see it.
So in that clip above from Watopia example, it gets worse when the camera is aimed towards the shadows of Titans Grove over the other side of the hill. The Richmond ones are looking down a long straight section of road. Other riders and shadows are the things that have always caused a large CPU load in Zwift. Itās as though the game is crunching data up to a mile in the distance instead of say the 1/4 mile it always used to (numbers totally made up). Whatever the root cause is, the game is performing significantly worse than expected.
If I can I might just fire up Zwift on my regular Xeon X5690 powered old Mac which runs 3.73ghz on turbo boost (3.46 normal) just to see how it goes as a comparison to what youāve seen.
I canāt ride myself because Iām so smashed up after the accident, but watching another rider should do.
Think you have your answer.
Then again itās been like this for at least six weeks and if nobody at the company has even noticed then I guess itās no surprise.
Great now (after 1.23.3) I canāt even start a ride. It crashes on starting a ride. This is where it crashes. Iāve already emailed support. So far their responses have been less than helpful as theyāve been a waste of time to read through.
Provide some information and possible solutions that might work instead of canned responses with links to support pages that are too generic and unrelated to the issues experienced.
There has been an awful lot of crashing going on with this March release, unfortunately.
Not much consolation, I know, but itās not just you.
I am getting more and more pissed on Zwift as with each and every update we get to more problems seem to appear.
Just did my 5th round of TOW (The longer ride) and in the last few KMās before the finnish line the app closed on it self and I needed to start up the app again and try to resume the ride. At first it looked like it worked, but then I saw I was in the same ride, but I was in the lead in again, but with all the KMās I had ridden. Also I suddenly was wearing a different KIT and riding the carbon Zwift bike.
After riding a few KM hoping to reset it back I finnished my ride and now I have 2 rides mentioned in the companion app. one of 52,7 KM and one of 55,1 KM. Neither of them are showing my 2 PRās, but I seem to have recieved around 2.100 XP for the ride.
But after having a better look I only have recieved 1.400 drops instead of at least 30.000 drops I am sure I allready had on the clock. For most people that does not matter much, but I want to buy a new bike and was saving all the drops I could.
Updated to version 1.23.3 before joining the Tour of Watopia, stage 5, Group A, 4 pm EST USA, Saturday. Zwift froze at exactly 8.9 km from the start.
Decided to do it again at 5 pm, so I restarted the computer, just in case. Started the event, and surprise, it froze again, EXACTLY at the same place, 8.9 km into the event.
I have a good PC, good processor, more than enough RAM and memory, good AMD graphics card, good connection.
The fact that it froze at exactly the same location would indicate that the problem has to be in zwift, maybe it is a problem in the last update? Last day I used zwift was on Tuesday, everything was fine.
Posted in error
Iām not sure what your point is. Youāre using a totally different setup in every way.
Iāve built over 75 Zwift PCs now (Intel/Nvidia/Win10), so you get very accustomed to how it feels and performs in various scenarios. Itās performing significantly worse than ever right now, and thereās not been a hint of acknowledgement from Zwift HQ about it. It feels like they are hoping it goes away, like the launcher flickering/stutter, and Makuri Islands where youāve always needed inexplicably powerful hardware to hit 60fps.
āDoesnāt affect Apple TV, so who cares.ā
updated earlier and everything paired automatically as it should but i had no movement or cadence until i went into the pairing screen and disconnected everything and reconnected, then it started working on the Neo 2T via Bluetooth, havenāt had this issue until this update