:P

http://xboxdvr.com/gamer/BLACKSTAR%20BSP/video/24951748

Don't worry Raga, they're on a 30 tick so there's no way you lost by more than .1 seconds without seeing the guy in front of you.

Wait, no, Bungie netcode is wonky as hell.

It's okay, SRL is still really fun.

Really don't think it was netcode on this one. We had a good race with multiple lead changes and we were all communicating with each other. Xenos saw and commented on my overtaking him on the mancannon jumps but neither of us thought anything was wrong. Down near the finish line a few seconds later both the people behind me confirmed that they were behind me from their perspectives. I don't think there was any visual wonkyness going on.

My guess is that lap timing does or doesn't start until you cross the start / finish line for the first time and somehow I can complete the three laps a little quicker but in total take longer.. somehow. And that this is made worse... again, somehow... by my usual method of waiting a good 5 - 10 seconds to start the race to give myself a clean opening line...

I really need to record entire races and see if I can't track this down more specifically... Its confusing, but I'm kinda interested to see just what is going wrong.

Wait, no, Bungie netcode is wonky as hell.

It's okay, SRL is still really fun.

So could you technically sit for a moment and give everyone a little time before starting and have a clear line?

I'm not sure. There seems to be some advantage in doing this in that you're less likely to get bumped off the line at the first gate, but if I was right I should be able to wait as long as I want and still win as long as I have the fastest time.

That seems not to be true.

Which is why I'd much rather a staggered start clock based race so this wouldn't happen and you would not be bouncing like ping-pong balls off the other racers either.

Not all the starting positions are equally close to the starting line. I think the race times each individual racer from the moment they cross the start line, until they cross the finish line in the 3rd lap.

I consistently am getting notices that I am in the lead even when one or even two racers are in front of me, and it's more than just lag-- I actually am ahead of them, but they reached the first gate ahead of me and their current time is slower than mine.

So could you technically sit for a moment and give everyone a little time before starting and have a clear line?

I consistently am getting notices that I am in the lead even when one or even two racers are in front of me, and it's more than just lag-- I actually am ahead of them, but they reached the first gate ahead of me and their current time is slower than mine.

I think that the times are accurate but the visual display of competitors is not. I don't see how it could be. The difference between being in front or behind someone is just a couple milliseconds. Even really good ping times are going to be greater than that difference. Also consider that at 30 frames per second, each frame is 33 milliseconds. The tiniest bit of lag is going to cause a discrepancy between where your Xbox thinks the competitor is and where he/she actually is - but we all get scored on our actual completion time.

That's the funniest part. Even on MY screen Ragashingo was ahead of me.

One possibility might be that finishing order is based purely on the time taken to complete the course, rather than on actually looking at where the sparrows are physically located in relation to each other. And maybe through some wonkiness they somehow manage to misidentify the moment a player started or finished.

I just had two races in a row where I was visually in third place but got scored as being fourth, one of them was a 0.002 second difference.

I think that the times are accurate but the visual display of competitors is not. I don't see how it could be. The difference between being in front or behind someone is just a couple milliseconds. Even really good ping times are going to be greater than that difference. Also consider that at 30 frames per second, each frame is 33 milliseconds. The tiniest bit of lag is going to cause a discrepancy between where your Xbox thinks the competitor is and where he/she actually is - but we all get scored on our actual completion time.

I made a fairly good time on Infinite Descent (4:10). I was in the lead for the first lap then I made one screw up and spent the rest of the race trying to catch up to the leader. Couldn't do it, even though I made no further mistakes. He maintained his lead for two laps and I never saw him again. I really could have used some rubber banding then.