What a wild and wacky month August turned out to be! So many
changes took place in the way we run and score races that you almost needed a program to keep up with it all. FTC (Failed To Connect) became a new buzz word, as matching issues plagued us throughout the month. SCEA’s regularly scheduled server maintenance wreaked havoc on organized racing for a while, and continues to be a sporadic issue at press time. Optimists see it as preparations for the release of the full game while pessimists look on it as nothing more than continued incompetence. Either way, the effects were felt throughout the month.
July ended with a discussion on the boards about how TPRA tracks race results and declares an overall points winner. It had been pointed out that quite a bit of emphasis was placed on how often a driver entered events (quantity) versus how well he finished in the events he did enter (quality). The bottom half of the leader board was littered with names of drivers we all knew to be excellent racers but we’re handicapped by missing events throughout the month. And the opposite was true as well as the upper ranks contained a lot of Division 3 drivers (no offense!) who garnered a lot of points by running in everything that got posted.
So, quantity over quality was an issue as was qualifying. There were drivers who could qualify well, thus picking up extra points by being placed in a higher division. Something needed to be done to balance out the equation. Some way that would reward a good qualifying effort, regular participation (quantity), and most importantly, good performance on the track (quality), all in an effort to reveal the “best“ drivers.
That’s a lot of “qua” words to deal with, but the race officials went after the problem with a vengeance. As you may recall, the month of August began with an announcement of a test event. A new system had been devised and needed to be