It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
The Witcher 2[Bug] Getting hit even without contact(15 posts)(15 posts)
(15 posts)
Pages:
1
This is my favourite topic
Posted June 26, 2011
So far I have seen this happen occasionally when enemy charges at you or when large monster execute flailing/swinging attacks. This is dangerous on Hard because getting hit (or getting staggered) once is enough for you to die from subsequent enemy combo moves.

This one.... was caught on tape (see pics).

I would like to hear what the rest of you think about this. Do you experience this as well? Do you think this is an intended design (!!?)

Edit: For your viewing pleasure
http://www.youtube.com/v/FShZfp4LlRU&loop=1&autoplay=1
For still shots of this, see this post.
Attachments:
shield_charge_1.jpg (264 Kb)
shield_charge_2.jpg (205 Kb)
shield_charge_3.jpg (248 Kb)
shield_charge_4.jpg (266 Kb)
Post edited July 13, 2011 by vAddicatedGamer
Posted June 26, 2011
Yes, it also happened to me a few times and at I also remember that once Geralt hit a harpy that was too far to reach by sword.
Posted June 26, 2011
Hit detection is a common problem in many games. TW2 is no buggier than many others in this respect. Mortal Kombat is notorious for it too. It's the subject of a lot of more or less successful attempts to improve, currently, as we get more CPU and GPU power to throw at the problem.

The problem is that you have characters and weapons represented by hit boxes, and when an intersection occurs, a hit is declared. The hit boxes are simple approximations, to make the computing burden acceptable. To the extent that the hit boxes exceed the dimensions of the animation, phantom hits occur. Illustration: http://farm5.static.flickr.com/4006/4655351624_43d834817d_b.jpg
Post edited June 26, 2011 by cjrgreen
Posted June 26, 2011
avatar
cjrgreen: Hit detection is a common problem in many games. TW2 is no buggier than many others in this respect. Mortal Kombat is notorious for it too. It's the subject of a lot of more or less successful attempts to improve, currently, as we get more CPU and GPU power to throw at the problem.

The problem is that you have characters and weapons represented by hit boxes, and when an intersection occurs, a hit is declared. The hit boxes are simple approximations, to make the computing burden acceptable. To the extent that the hit boxes exceed the dimensions of the animation, phantom hits occur. Illustration: http://farm5.static.flickr.com/4006/4655351624_43d834817d_b.jpg
I don't really understand the picture (do I look at the filled boxes? what does the unfilled boxes signifiy?) but I understand what you mean by hit detection. Can it be improved via a patch or something. The thing is, with relatively long stagger time in TW2, this can be very problematic towards survival.
Posted June 26, 2011
Yeah, hit detection is the least of the game's problems. It is an occasional issue though.
Posted June 26, 2011
Hit Detection!! Have you ever player Witcher_1?? You were more than half dead before the cut-scene was finished!! They have really improved it with this one. There's more of a problem with delayed to non-existant responce from the buttons/keyboard then anything else. I pity those who play on Insane!!
Posted June 26, 2011
avatar
Gidzin: Hit Detection!! Have you ever player Witcher_1?? You were more than half dead before the cut-scene was finished!! They have really improved it with this one. There's more of a problem with delayed to non-existant responce from the buttons/keyboard then anything else. I pity those who play on Insane!!
I know what you are saying about TW1 (although I didn't spend nearly as much time on it). Thing is, in TW1 you don't get as much control over dodge-rolling, the pace is slower, it is less action-oriented, and you can drink potion in battle so it is not as punishing.

In TW2, getting hit although clearly you are not supposed to (as shown in the screenshots) staggers you and potentially brings all those keyboard issues into play, resulting in death.
Post edited June 26, 2011 by vAddicatedGamer
Posted June 27, 2011
Added some pictures to show an instance in Chapter 3 where the imprecision in the hit detection results in instant death(s).
Attachments:
hit_detection_11.jpg (284 Kb)
hit_detection_12.jpg (283 Kb)
hit_detection_13.jpg (310 Kb)
hit_detection_14.jpg (258 Kb)
hit_detection_21.jpg (275 Kb)
hit_detection_22.jpg (258 Kb)
hit_detection23.jpg (344 Kb)
Post edited June 27, 2011 by vAddicatedGamer
Posted June 27, 2011
Until someone told me Yrden worked on the boss, this is the kind of thing that made the Draug fight annoying. Definitely not playing on insane anytime soon because of it hehe.
Posted July 09, 2011
avatar
aimlessgun: Until someone told me Yrden worked on the boss, this is the kind of thing that made the Draug fight annoying. Definitely not playing on insane anytime soon because of it hehe.
There's the occasional hitbox problem, then there are hitbox problems a mile wide. Being half-way across the screen and still getting hit is not acceptable.
Posted July 09, 2011
avatar
3DMaster: There's the occasional hitbox problem, then there are hitbox problems a mile wide. Being half-way across the screen and still getting hit is not acceptable.
Sounds pretty serious, is it even worse than the ones I posted on the 8th post? Do you have a screenshot of this? I usually record the gameplay in FRAP, then play the video and snap the screenshot from there.
Posted July 13, 2011
Damn, I've seen hit detections go awry, but this one topples them all...
Attachments:
hit_detection_31.jpg (227 Kb)
hit_detection_32.jpg (228 Kb)
hit_detection_33.jpg (252 Kb)
hit_detection_34.jpg (162 Kb)
Posted July 13, 2011
avatar
vAddicatedGamer: Damn, I've seen hit detections go awry, but this one topples them all...
Clearly, Aryan has some crazy psychic powers... :D
Posted July 13, 2011
avatar
vAddicatedGamer: Added some pictures to show an instance in Chapter 3 where the imprecision in the hit detection results in instant death(s).
Hm, not only Aryan is too far to hit Geralt but he is also facing in a different direction. It looks like there is more than hit detection involved, like the engine not getting right the relative position of the fighters. I hope CDP guys are watching this.
Posted July 13, 2011
It looks like the kind of behaviour you might encounter in online games, but there's no latency to take into consideration in TW2, so I agree it's an issue that they need to look into.
Pages:
1
This is my favourite topic
Community
The Witcher 2[Bug] Getting hit even without contact(15 posts)(15 posts)
(15 posts)