Quote
. . . a delay that l am getting between the moment i hit a button and the moment that the game reacts . . .
It's not quite unplayable, but it's maddening to click and have nothing happen. Especially when I'm driving an Atlas in a close brawl; the Atlas is already slow to turn, but when I hit a key to turn and nothing - and I mean
nothing - happens besides the mech continuing in a straight line, it provokes some cussing. Emphasis, the
Atlas doesn't just turn slowly, it doesn't turn at all, but just keeps moving in a straight line for anywhere from 3 to 5 seconds or more.
Likewise with aiming - I move the mouse up or down, and the reticle *just* *doesn't* *move* - the delay here is anywhere from a half second to maybe 3 or 4 times that long, which is plenty of time to miss a shot opportunity.
This doesn't happen continuously, but it seems most common after I've played a couple of matches in a row (memory leak?) and when the screen is crowded with other mechs.
update: Just tried another match. My ping was in the high 60ms range, others were considerably higher. All was well until combat was joined, and with several mechs from both sides in close combat, controls became unresponsive - delay > 1 second before the mech responded to ANY input. This seems to be a factor since the most recent patch.
Edited by Dunark, 03 February 2013 - 07:00 PM.
0
