|
Search the News Archive |
Spoilers are currently disabled. (All newsposts are visible.) |
November 18, 2004 Link to this post
If it's not one thing...
You fix some stuff, you break other stuff. There's a forum thread over at bungie.net where people are screaming about new-found lag in XBL Halo 2 matches. I know nothing about the specifics of yesterday's autoupdate - but it seems to me that if you decrease the testing you do to find the best match, bandwidth-wise, for a game (which HAS to be the case; after all, the total time taken has dropped dramatically), you MUST be allowing for more leeway in the matches found... which means you've increased the opportunity for things like lag. If we get any more specific/technical info about this subject from anyone at Bungie, we'll be sure to pass it along! (Thanks, Wraith.) Update: Chris Butcher has replied in the original thread, explaining the mechanics of the change in the matchmaking code; the search for 'best host' is unchanged, but the search for 'best game' (which happens first) has been greatly speeded up by expanding the number of games being seeded. According to Chris, this means there's nothing that was changed that should manifest as laggier games; his best guess is just that last night was worse than usual for general internet connectivity, but they're going to be closely monitoring the situation for the next few days. (Thanks, Sketch.) (Louis Wu 13:39:07 UTC)
