5 replies to this topic

[ecued]

i have a Jeager A with 2 guass rifles. i was just in a match chasing a thunder bolt missing both arms, all tore up. he was running directly in front of me, about 250M, never moved left or right an inch. i fired not 1, not 2, not 3, but 4 twin guass rounds directly into its back, he never varied direction, not only did it not die, it didn't even take damage. he wasn't disconnected because after the 4th shot, he turned around and killed me. i see this kind of thing all the time. i know what causes it, i just would like an official statement from the firm. and no, that doesn't mean some born again 10000 poster with an opinion, who thinks that just because they talk about mechwarrior all day, makes them a player. thanks.

Edited by ecued, 04 April 2014 - 02:53 PM.

[Opus]

armor bot

[Klappspaten]

Im not quite sure, but I guess you would have a bigger chance to get an answer if you would send a support request.

[Redshift2k5]

Short answer: because he wasn't really where you thought he was

longer answer; hit detection is not perfect, and if your ping was high/unstable, his ping was high/unstable, or the server simple missed a chunk of data then the things you see and the things that actually happen on the server stop being the same thing. No game has perfect hit detection, there are always wrinkles and edge cases and occasional errors. some games display this with lots of warping/teleporting, MWO generally has less warping and more mystery no-reg hits. Shit happens.

[S3dition]

ecued, on 04 April 2014 - 02:48 PM, said:

I demand an answer from the developers not the players. But I post on the forums instead of asking through support.

Hmm. Dunno what your problem could be. Did you try turning it off and on again?

Edited by S3dition, 04 April 2014 - 04:20 PM.

[Heffay]