Yet another “World Tour” event on the iRacing.com Simulation has descended into chaos, with multiple server issues and software bugs plauging what is supposed to be one of the biggest online racing events of the entire year. Today’s Reader Submission comes from Anthony P., who has done a fantastic job chronicling the sequence leading to the sub-par experience iRacing users have dealt with today.
As has seemingly become the norm, another major iRacing event has resulted in major issues. A day before the event had even begun, iRacing members were debating the likeliness of the website having problems. As you can see from the poll, not many had faith in the site.
As was expected, iRacing went down for many users. This led to hundreds of drivers who had been practicing for weeks not being able to register for the race in the 30 minute window that was allotted. Threads began to flood the iRacing forums:
iRacing finally addressed the community announcing that another race would start a few hours later, followed by the advice “join early”.
With that issue finally resolved, what else could go wrong? Well aside from the official race broadcast featuring a common bug that resulted in large swaths of the track being devoid of any lighting, the race was once again ruined for dozens of users due to other iRacing bugs.
The Corvette C7 Daytona Prototype is a relatively new addition to the iRacing lineup. Despite being on the service for over four months, bugs were never fixed with the cars damage model. A light tap to the car, which could result in minor cosmetic damage and change nothing about the cars handling or speed, would commonly give it a black flag. This forces the driver to pit in and take repairs within 3 laps or be disqualified from the race. As it happens, not only was this bug featured in the Daytona 24 but another bug that resulted in black flags not being cleared on repair/pit-in. This didn’t just set teams back a few laps but was outright kicking them out of the race. NASCAR Whelen Modified driver Dalton Baldwin took to the forums in anger.
iRacing were aware of the issues with the car, and announced that they wouldn’t be making any changes to the DP over a week before the race.
That has to be the end of all the bugs, right? Roughly 11 hours into the race, drivers were no longer able to join the race session in order to execute a driver swap.
This led to many drivers being unable to join the race until the issue was resolved and missing scheduled driver swaps. There is still no public post from iRacing addressing this issue. It’s currently 14 hours into the (originally scheduled) Daytona 24 race and things have seemingly calmed down. However to add insult to injury, one of iRacing’s newest features, dynamic tracks, don’t seem to be functioning properly as marbles aren’t forming on the track.
But in all seriousness, I know when I ran the 2.4 Hours of Daytona back in 2013, we had similar problems. I remember the servers went down right as the initial sessions kicked off, but not everybody lagged out, so some users were able to run in sessions with a total of four cars, reeling in massive iRating gains like you wouldn’t believe. As a result, the hastily scheduled alternative sessions screwed some people over, as they hadn’t planned to be at their computers waiting for iRacing to fix their shit all Saturday afternoon. A recurring theme that we regurgitate throughout iRacing articles on PRC.net, these hiccups were somewhat acceptable in 2013, but three years later, it’s frustrating even as a bystander to see it all go horribly awry. You have these hardcore fanboys running around the various sim racing forums proclaiming the gospel of iRacing, only to see this so-called unparalleled online functionality come crumbling down at a critical moment.