Wed Jan 07, 2015 2:25 am by strop
ah ok. I now get 2:21.62, which, when I run the ventilation slider up to maximum, matches your times posted. That's the tricky thing about testing for tournament purposes and all that, as it affects different cars differently depending on what their fixtures are and whether the extra drag on the course affects it or not (for Daytona, it definitely does due to the Tri Oval).
This is absolutely not a complaint, as I'm actually even pleasantly surprised that the inferior Not-Golf Mk I body is doing so well (a 5 minute build with a not-CRX body with double-wishbone fronts goes about 1% faster, which is significant), but given the result in round 1, I was slightly surprised by the result in round 2 hence my enquiry.
There's something to be said about tweaks to the course, what was the tweak? Were the cambers decreased in some areas? The reason I ask, is because in most other tournaments, unless there's something known to be inaccurate/wrong with the track, if a car runs a "triedtocomparevaluewithnil" error on the track, we more commonly assume that it actually crashed on track and failed to finish the race, which is most often due to inadequate traction or too much lift (4 minutes into my not-CRX build, I had the aero wrong and the excessive lift on the rear created that very same error). This might be difficult to anticipate if the tracks aren't announced, but IMHO it would be left to the responsibility of the entrant to ensure their tune would be safe enough for all tracks encountered, and that such errors would have to be counted as a DNF... but of course this would be most properly left to the discretion of the tournament host.