What are your pc specs?
Where was this promised?
1 Like
Then thereās something totally wrong with your PC.
2 Likes
Iāve seen some other threads where zwift mods, or devs have made comments of future improvements.
That was my initial thought. But nothing else runs slowly. After uninstalling, reinstalling, virus checking, malware checking, windows updates, windows rebuilds Iām still sitting around for 15 minutes plus waiting for Zwift to load.
Today I started Zwift at 6:40 for a 7:00 am Activity. To my horror I got the dreaded āAn update is neededā dialog. By 6:55 while still waiting for the update to finish I had enough. Iām done. The Trainer came with a free Rouvy trial. By 6:58 Iād registered, downloaded, installed connected sensors and started my ride. The most annoying thing about it was at 7:10 when Zwift finally popped up and blocked my view.
There is something seriously wrong with that PC. Even the Zwift installation on my wifeās pentuim 10year old pc is faster (about 3 minutes)
EDIT: it is a Core2 Duo E8500
1 Like
Probably a Celeron or Atom, or non-Ryzen AMD. Coupled with a mechanical hard drive.
Itās massively underestimated how important the CPU is to virtually every aspect of Zwift performance, including load times.
2 Likes
A common (ish) issue Iāve seen with Zwift is mismatched MTU (maximum transmission unit). Assuming you have a windows box then open a command prompt and type
netsh interface ipv4 show subinterfaces
This will show a series of interfaces - one with a very big number and others (maybe only one) with a number about 1500. This laptop shows 1500 for example on the WiFi interface. Picking the interface you actually use then find the MTU and subtract 20 from it.
Now type in the command prompt
ping -l 1480 -f 8.8.8.8
8.8.8.8 is the IP address of Googleās DNS servers. If this comes back like
ping -l 1480 -f 8.8.8.8
Pinging 8.8.8.8 with 1480 bytes of data:
Packet needs to be fragmented but DF set.
Then you have a problem. Itās easily solved but a bit involved - let me know if you have this issue.
1 Like
Hi Paul,
Iāve already maximised my MTU to account for any Latency. My optimal MTU is 1472, so when I add 28 to that (20 bytes for the IP header and 8 bytes for the ICMP Echo Request header) Iām back up to 1500 anyway. I did try lowering it on the PC and it made little difference. Iād expect latenmcy that is causing minutes worth of delay would affect all applications and not just Zwift.
It was about 2-3 Minutes when I first installed. But Every Update seems to make it slower. Iāve been Using Rouvy under a free trial for the last week. It loads in a minute or so. Thought Iād try Zwift again today, and yup, another update and another 30 minutes waiting for the thing to load before I gave up.
AMD A8
Once the thing loads it runs well, its just the blasted start-up time