Trying out Zwift is probably often done by trying it on a laptop/tab/phone you already have. After running Zwift for a while and starting team time trials with my team, it seems like performance has become an issue. Question is on what part I should start…?
Bluetooth connection to trainer (speed, delays) and/or heart rate monitor? Wi-fi connection to internet router (speed, delays)? Uplink/downlink? Graphics performance in IPad Air 4?
It would have been great to get some support for analyzing the technical setup, using function within Zwift (trainer setup already) or separate app.
If you want to check graphics performance of iPad Air 4, triple tap on the Zwift logo at the log-in screen, email yourself the log file and drop on zwiftalizer.com. I’m currently working on a new version that does more with BLE and UDP network traffic up and down, and divides the session into multiple activities. I don’t know when it will be ready. Free time is non existent.
Ha ha ha, flattery will get you everywhere. Thanks mate. Here’s a sneak peak of v2 showing how UPD server to client packets affect FPS. On a PC with an average CPU and quite capable GPU, the high UDP server to client traffic - which is typical of a race or group ride bunch situation - bogs down the CPU and GPU is underfed. About half way the rider leaves the group and we see the UDP StC packet count go down, and FPS go back up to the expected 60, give or take a few for the World and course - which is now logged. France, Casse Pattes in this case. I’m hoping to use this additional context info to start up the benchmarks report again.
