|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Buster Friently
Rosen Association
2157
|
Posted - 2014.04.03 18:03:00 -
[1] - Quote
I'm willing to bet that, for a given class of weapons, the "hit detection" code is shared. So, for instance, all the hitscan weapons probably share the same "hit detection" code. They are therefore, probably all messed up right now, it's just more noticeable when using certain weapons because of the use case of the weapon.
In short, it's highly likely that hit detection is screwed across the board.
|
Buster Friently
Rosen Association
2157
|
Posted - 2014.04.03 18:07:00 -
[2] - Quote
Cody Sietz wrote:Buster Friently wrote:I'm willing to bet that, for a given class of weapons, the "hit detection" code is shared. So, for instance, all the hitscan weapons probably share the same "hit detection" code. They are therefore, probably all messed up right now, it's just more noticeable when using certain weapons because of the use case of the weapon.
In short, it's highly likely that hit detection is screwed across the board.
Seems possible, though I don't know how code works. So I'll take your word for it at th very least.
Well, I haven't seen this game's code, but trust me when I say that programmers never rewrite anything that they don't absolutely have to.
|
Buster Friently
Rosen Association
2158
|
Posted - 2014.04.03 18:17:00 -
[3] - Quote
Cody Sietz wrote:Buster Friently wrote:Cody Sietz wrote:Buster Friently wrote:I'm willing to bet that, for a given class of weapons, the "hit detection" code is shared. So, for instance, all the hitscan weapons probably share the same "hit detection" code. They are therefore, probably all messed up right now, it's just more noticeable when using certain weapons because of the use case of the weapon.
In short, it's highly likely that hit detection is screwed across the board.
Seems possible, though I don't know how code works. So I'll take your word for it at th very least. Well, I haven't seen this game's code, but trust me when I say that programmers never rewrite anything that they don't absolutely have to. Do you think they could correct it with a hot fix? Or would this have to be in a patch?
I have no real idea here, but this may depend on whether the issue is found to be clientside or serverside (or both).
It's highly likely that there isn't a known solution yet. It could be anything from a coding error to network lag to hardware issues realy.
|
|
|
|