- 11,207
- Adrian, Mich.
- cargorat323
- CargoRatt
27.834
53.617
1'15.417
Submitted...accepted.
53.617
1'15.417
Submitted...accepted.
That's actually present on most if not all weeks. Since we do not have complete splits in the live timing screen, we're forced into this workaround. The splits, therefore, are not exact in my opinion. My T3 times are typically slightly slower than the one we grab using this method, and I assume that would be the case for most drivers.On another note of inconsequential value I have noticed something peculiar in the timing when running this trial. It goes something like this: My posted time for the first sector is 27.700. This was taken directly from the replay. It doesn't matter if you stop the replay before and arrow to the point or stop the replay after and arrow back to the point. It always shows 27.700. But when driving in the trial using the replay as the ghost, if for example, I crossed the first sector point at 27.884, it shows on the screen that I am .169 behind my ghost time. This would indicate that my sector time would have been 27.715 not 27.700. Should it not indicate that I am .184 behind? Should I be using the new common core math instead of traditional math? Strange!
The deadline is not for another ~48 minutes, don't forget about summer time, while GMT is based on non-summer time.
Also, I can see your submission in the Admin only list that's visible in the Fetchbot.
Also, so everyone can be assured of competing on a level playing field, I NEVER look at that list until I've sent my final submission.
Mmmmhmmmm I'm actually kind of curious how they show up on your end. Is there some sort of file that fetchy generates of all the times submitted? Probably none of my business, but I think things like that are fascinating.Also, so everyone can be assured of competing on a level playing field, I NEVER look at that list until I've sent my final submission.
Methinks since we view the replay, which is 60 frames per second, it cannot stop between frames. So it stops where "during this frame, we hit the marker". GT5 was probably 50 / 60 depending on region or so.The splits, therefore, are not exact in my opinion.
Now you know what it's like to be me when I chase youOh my god my T4 was far worse than expected.
I could have spent every waking hour on this track and I'd still have been a solid 2 seconds behind you.Maybe I should spend a little longer than one hour next time.
Time to kick him out of D3Top 10 on a combo where everybody went crazy and pushed hard. That's impressive.
On another note, I'm still having problems uploading and checking replays. Could someone give me the exact steps to go through to get this done, my retarded ass seems to be missing something. There used to be a step by step guide somewhere, but again, my dumbass can't seem to find that either. Thanks, and again, great job everyone....its an honor to compete with such an elite bunch of people.