Nonse hit detection- will be ever fix?

[Kafein]

http://www.youtube.com/watch?v=3AIWodyQvq4

I don't know about shield forcefield, but what I see in this video is fucked up and got me killed more than it should *mad*

[cmp]

Gave a look to the Warband code, it doesn't even care if you have a shield when checking for agent-agent collision.
Basically it's an engine quirk that has always been there, for some reason it got noticed only after the shield forcefield change, and the change got the blame.
Sigh.

This thread gives me the impression everytime we report bugs devs ignore it because they think we are trying to bullshit them.

I don't think you're trying to bullshit me, I think you are drawing conclusions based on insufficient evidence. See above in this very post.

[Christo]

There is no definitive way to "fix" it, because technically it isn't even a bug. It can be tuned and masked by software (which we will continue to try improving), but in the end there'll always be a hardware/network factor.

Most of the time the cause is not serverside. Nonetheless, there are both clientside and serverside improvements planned. If it's caused by a slow/interleaved/noisy connection, there's nothing we can do about it.

visitors can't see pics , please register or login

[Kafein]

Gave a look to the Warband code, it doesn't even care if you have a shield when checking for agent-agent collision.
Basically it's an engine quirk that has always been there, for some reason it got noticed only after the shield forcefield change, and the change got the blame.
Sigh.

I don't think you're trying to bullshit me, I think you are drawing conclusions based on insufficient evidence. See above in this very post.

Well that's cool, but even in the absence of connection, the agent-agent collision is still fucked up and the forcefield nerf still has what I would call unwanted effects on non-round shields

Also for nitpicking, apart from the the thread's topic, I wasn't actually blaming any change

[Tomeusz]

You shooting targer standing 1 metre from you, full focus and arrow miss, but when guy chase you with 1h sword, swing have 3 metre reach, yeah thix is nothing about bugs, but internet connection... .

[cmp]

Also for nitpicking, apart from the the thread's topic, I wasn't actually blaming any change

I was referring to Digglez.

I don't think you're trying to bullshit me, I think you are drawing conclusions based on insufficient evidence. See above in this very post.

You shooting targer standing 1 metre from you, full focus and arrow miss, but when guy chase you with 1h sword, swing have 3 metre reach, yeah thix is nothing about bugs, but internet connection... .

On the other hand, I think this one is trying to bullshit me. Protip: exaggerating heavily in bug reports is a really bad idea.

[Havoco]

Because it doesn't. Ghost reach is when a weapon hitbox is longer than the visual model. If a weapon has ghost reach, it will be noticeable every time you attack.
What people call ghost reach is caused by client-server delays, server-client delays, and synchronization approximation. What you see looks like there's ghost reach, but what the server "sees" (and most other clients probably) is perfectly fine.

So how much does the additional weapons/armors/submods/patches contribute to this? I've also noticed a significant increase in the ghost projectiles for the past two years.

[cmp]

Ghost projectiles is an entirely different thing than ghost reach. I haven't looked into that well enough to draw a conclusion.

[Minx]

Ghost projectiles is an entirely different thing than ghost reach. I haven't looked into that well enough to draw a conclusion.

Please do, nothing more frustrating than a direct hit passing directly through someone. Sadly though I think its latency related as when my ping goes up the more it seems to occur. 

[Miley]

Nonse? What's that? (will it ever be fixed*)

[Vkvkvk]

Because it doesn't. Ghost reach is when a weapon hitbox is longer than the visual model. If a weapon has ghost reach, it will be noticeable every time you attack.
What people call ghost reach is caused by client-server delays, server-client delays, and synchronization approximation. What you see looks like there's ghost reach, but what the server "sees" (and most other clients probably) is perfectly fine.

Right, any way to fix that? I mean I understand that netcodes and ping aren't things that can really be fixed easily or at all but that kind of unsync between client-server/server-client is getting worse and worse.

As I'm no dev, I don't know about the inner workings of WSE or anything like that in details so if I'm wrong, feel free to call me stupid but isn't adding all that new WSE stuff  just straining the servers even more by having to calculate more things at once, effectively making phenomenons like Ghost Reach happen more often? I've been playing cRPG exactly 2 years now (Give or take a few days) and my playstyle has never changed, it's always been about me going high athletic builds just so I could dance just outside of someone's reach and attack them when they were already commited to an attack, making it so that they couldn't block if I timed it right. That playstyle is unfortunately getting harder and harder because of said phenomenon, I used to be able to do it with great results a year and a half back so I don't see why I would somehow become worse in my best playstyle when I've gotten absolutely better in everything else by miles.

[cmp]

The thing is, if it was the server's fault (i.e. WSE or engine related) we would be all experiencing it, with no exceptions. I can't speak for others, but I haven't seen anything like that, which makes me think it's not the server after all.

[Kafein]

I was referring to Digglez.

Why u no always quote people 

That would would also prevent me from ridiculing myself with writing brainfarts.

[KaMiKaZe_JoE]

I have had no problems, you all just suck.

[Banok]

would be nice if the game had proper weapon tracers instead of area of effect attacks to stop ghost reach and such. pvkii and wotr have it.