- No text -

It wasn't just something laggy on your end. I was in 3rd and clearly saw you a sparrow length in the lead.

I actually remember a similar thing happening last year to me, so not sure it's a new thing.

Below is incontrovertible video evidence that Destiny sports an unfair, non-gate-related Rubberbanding effect that cost me the win when there is no reason it should have. Everyone agreed on the spot that something was very wrong and that I should have won. Whatever they fixed yesterday for Kahzgul must have broken something for me. :(

http://xboxdvr.com/gamer/Ragashingo/video/24654886

Something is definitely wonky there, not disputing that, but I don't think it has anything to do with any suspected rubberbanding. Seems more like the netcode just can't handle (reliably) such close finishes. The time spread between 1st and 2nd is less than 2-tenths of a second.

- No text -

Not sure if sarcasm. That is odd, and definitely something laggy, or just broken timing, or whatever. But that is not rubber-banding. If Xenos had visibly shot past you (on an identical sparrow), that would have been. But his visible position here didn't match the finish timing that was shown on the board.

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.

Or, here's another. As others have said, this happened last year as well, and it tended to be with close finishes, within a couple tenths of each other. One idea I remember being floated at that time was that it might be calculating sparrow position in the same way it calculates player position in normal Destiny, where, until it receives specific position information, it estimates position based on last known position/velocity. That's the same thing that can create the illusion of laggy players teleporting, walking into walls, and that kind of stuff. The thing is, even if players don't APPEAR laggy to a human players eye, a system like that could feasibly have minute differences. Maybe even enough to cause a discrepancy with how players appeared to finish, if they were extremely close to start with.

As I've said before, if you want to see what actual unfair rubber-banding looks like, play the original Need for Speed: Underground. Howl with rage as, mere feet from the finish, a big heavy car screams past your tiny cornering machine THROUGH A CORNER, at speeds that it clearly should NOT be able to do. Stare at the screen dumbfounded as the rubber-banding that was supposed to merely catch them up with you (in the name of "exciting" races) instead continues to catapult them down the track at ludicrous speed for half a lap after they've passed you. And BTW, all that happened in a single player game, so no network-related excuses! :P

Remember last night where I saw you finish before me yet in the standings I was ahead of you? Same thing basically.

The same exact thing happened to us last night - in the same exact spot and on the same exact map. DestroyoBoy and I were fighting for position (although in our case it was for 3rd IIRC), and I had a flawless run those final several hundred yards and he still somehow "pulled ahead" and placed higher than me -- which really confused me for a moment because he never came that close to overtaking me on my screen and I only noticed once I saw the leaderboard.

Yup, same thing happened to me recording the rampancy.net podcast.

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.

Don't worry Rag, 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.