Sometimes when launch the program I get jerky video. The background will shift and not be smooth.
I have to reboot to get it smooth.
What info do you need to sus this out. I’ve gone into task manager to see if something is using excessive resources but don’t find anything.
Thanks
Ray
Can you post the details of the system you are running Zwift on. Along with the in game graphic settings you’ve selected.
Device name XPS8490
Processor Intel(R) Core™ i7-10700 CPU @ 2.90GHz (2.90 GHz)
Installed RAM 64.0 GB (63.7 GB usable)
Device ID 674D1258-5C17-4F72-BBA5-41F6C83F7F5A
Product ID 00331-10000-00001-AA365
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 11 Pro
Version 25H2
Installed on 12/4/2024
OS build 26200.8655
Experience Windows Feature Experience Pack 1000.26100.315.0
What graphics card are you running?
If the display cable is connected to the Nvidia card then there’s no way the integrated GPU matters (and if the cable is connected to the motherboard then there’s no way the Nvidia GPU matters).
What do you see when you upload a Zwift log file to trainerdx.com? There is a Share button on the log report you can use to make the analysis public and let other people review it, or you can post screenshots of it.
If you have an ANT+ dongle, pull it out for your next test since that can cause performance problems on Windows. Those problems usually show up on the pairing screen first though.
If you can ride without the dongle at all, that would be the first thing I would do, but those are some crazy bad frame rates given the hardware you have, and they’re very steadily bad all the time. The dongle is just something to rule out, not necessarily the cause (unless it is). You could do a “just watch” activity without pairing anything and might get the same result.
Drop the Zwift resolution down to 1440. 2160 could be a step too far for your spec and to be honest you’ll barely notice a difference.
Also put on exclusion on windows defender checking the Zwift folder. This will do wonders to your load times for the game and also the world’s.
I see other users with the 1660 Ti and i7 10700 getting far better frame rates in 4K. Not with the latest game version but still, that is reasonable hardware.
Ok. The Zwift folder in appdata?
No dongle, no pairing.
So, I have a bottleneck somewhere. Move dongle closer? It’s about a yard away,
This is new issue. Can’t connect to any specific build.
I can pair and get to a world but the video is, again jerky, making it unrideable.
I used to have those framerates in Makuri with with Laptop version of that setup (Lenovo 10850 & 1660Ti) and it did not have to be crowded. With a desktop perhaps should be a bit better. Things to check:
-Check your CPU cooler (monitor temps).
-Network: WiFi or ethernet…do a speedtest
-background noise: Check Task MGR to see if some other program(s) might be hogging resources
-When was the last time you re-installed Windows? I had to do that once with noticeable improvement.
Note that I believe that running Zwift is getting more and more heavy over time. Not noticeable update to update but over 20-25 updates. But this is only IMO. I have not proven. I could put my laptop back into use and compare to the past but that would take some time. More fun to upgrade.
I don’t think the pairing method or the network is going to give you a steady 20 FPS on that hardware. I bet you could pair nothing, do a “just watch” session and see the same thing (which you could prove if you want). It does look more like a throttled CPU or something else gobbling up the CPU in a steady way. But if it were consistently CPU throttled that would result in a steady level of very poor performance because the clock speed would be always less than expected. The performance you’re getting is like what I see from people with a 10 year old Celeron laptop.
One way to check for CPU throttling…
Thanks Paul
Ray
Where would I see the throttling in HW info Paul?
You might also see a CPU clock speed on the sensor page that is much lower than what you expect from the CPU, since that’s the expected result of throttling.
