I’ve been using Zwift for several months and have had my fair share of application crashes, but I think I’ve resolved them after a bit of trial-and-error. Here is my list of tips for having the most reliable Zwift experience. Note that you should only consider the following tips if you’re having issues… if you’re not, then ride-on!
As a programmer, seeing the error message “Object reference not set to an instance of an object” is pretty common and pretty annoying. What’s even more annoying is when you get that error when simply trying to get the latest source code from your Team Foundation Server within Visual Studio, as shown below.
Over the last weekend, our TFS 2013 server decided to stop building projects for no apparent reason. No one had changed any software on the TFS or build controller servers and the only evidence of a problem was the following message in the “Diagnostics” log file for each build:After spending hours searching for solutions to this problem and finding nothing, I finally figured-out the cause of the issue. The primary hard drive on the TFS server (not the build agent) was completely full. After sending a request to our infrastructure team to add more storage to the primary hard drive on the virtual server that hosts our TFS implementation, the builds started working again.
When training indoors with the Zwift software, the main route is called “Zwift Island”. As such, the term “Zwift Island Rig” has caught-on as a way to describe one’s setup for using Zwift. Technophobes might may find using Zwift a bit of a challenge as it does involve considerable technical expertise to get it running smoothly. My Zwift rig is hardly pretty to look at, but it works for now and is a work-in-process as I learn what works and what doesn’t.