I do not think there is poor hit detection.

[Gudenrath]

Never seen this in my 5 years playing RO1, but I have experienced it a couple of times in RO2. One time was almost exactly like the example shown in the video. And it was while having good ping (below 100). I don't get it very often though (less than 1 time in every 10 games).

The main problem I think is that players can bandage their way out of a rifleshot to the torso area. It should at the very least cause a bleed out.

[realninja]

I think there needs to be an animation for when a character is hit ,so u c an clearly see it

[MarioBava]

Originally Posted by Reise

He doesn't even get the kill, genius.

The only thing he hits is the guy's arm with his last shot.

If the torso hit was lethal, or actually happened, he would've gotten the kill. Instead the dude across from him with the MP40 actually finished him first. Check the assist point.

Ok, I rewatched the vid and you're right, he gets the assist not the kill, which by the way still means he hit his target, AND it also means the other guy's hits were registering. A better example of bad hit detection would've showed no assist points.

Also, torso hit does not always mean lethal in this game. Vital organ hits or bleedout hits absent bandaging do. I just guessed it was a killing shot because the guy died immediately, without checking the kill notice. It probably did cause a bleed, and the torso hit might've been ultimately lethal by rapid bleedout if there hadn't been another friendly shooting at him for the kill, but we don't know because the other guy's bullet is the one that almost simultaneously got the kill.

So again, where is the proven problem in that vid?

p.s. don't mistake me for saying there are no hit detection issues. I'm fairly sure I've experienced them myself, so I'm not saying that. I'm just saying what looks like it to one person might not always even be it.

[|716ID| Hptm.Popov]

Originally Posted by shorelinetrance

Typical Red Orchestra 2 Gameplay. - YouTube

sup guys?

http://3.bp.blogspot.com/_5aUJfjvYbl...ame%5B1%5D.jpg

[Das Bose]

Originally Posted by Reise

Are you serious? lol

It's happening in that video. From that range his rifle should have dropped him on the first shot, yet he empties almost his entire mag into the guy to no effect. There are no hit sounds or anything.

I dunno how it gets any clearer than that.

I just had an instance now with my ppsh on commissars house. I was on one side of a low wall and there were 2 Axis on the other side running towards my position.

I fired a long controlled ( supported on the wall ) burst at the closest guy ( about 2 rifle lengths away ) who immediately stopped and took aim at me, fired and missed. Surprised I fired another controlled burst directly at center mass from what was now 1 rifle length away, with the second Axis guy also in my field of fire I fired again, emptying my magazine.

The second guy then shot me once with his pistol, killing me.

Straightaway I asked the guys if they were nearly dead e.t.c and it turns out I hit nothing, not even a clip or a graze on either of them, and I can pick off running players @ 100+ meters no problem at all with the ppsh, as I'm sure a lot of you can.

The server wasn't struggling and neither was my pc or connection, which leads me to believe there is indeed an issue.

It's happened lots of times before, but this was the most extreme with an entire clip missing two stationary targets at basically point blank range, with the weapon held steady on target throughout.

There were no impact sounds or blood splats e.t.c.

[Josef Nader]

@MarioBava

You don't think that he would have died a lot sooner with both a semi-auto and an SMG pumping rounds into him from that range? Both the semi and the SMG were firing for 2-3 seconds before he dropped. It only takes one hit to trigger the bleed-out animation, yet he kept fighting like a champ until one of the SMG guy's rounds decided to register. You get kill assists for suppressing enemies too. Perhaps rifle guy put him into full suppression (with the help of SMG guy) and SMG guy got the lucky hit to register?

[Karnatakapunk]

@MarioBava

This guy just dont want to see it period.
Done talking into blind deaf people, who compare the game to a holly bible, and people canot blasfeming it by pointing it flaws.
Hope, tripwire spend more time on these type of things ( hit detection) then on stupidity stats and unlocks...

[derbefrier]

Originally Posted by shorelinetrance

Typical Red Orchestra 2 Gameplay. - YouTube

sup guys?

Heh that's what we are talking about.

[MarioBava]

Originally Posted by Karnatakapunk

@MarioBava

This guy just dont want to see it period.
Done talking into blind deaf people, who compare the game to a holly bible, and people canot blasfeming it by pointing it flaws.
Hope, tripwire spend more time on these type of things ( hit detection) then on stupidity stats and unlocks...

Sorry, but I said I've seen hit detection problems. Just not clear in that video. It's not about comparing the game to a holy bible, you just make your point of view look bad by such exaggerations.

[MarioBava]

Originally Posted by Josef Nader

@MarioBava

You don't think that he would have died a lot sooner with both a semi-auto and an SMG pumping rounds into him from that range? Both the semi and the SMG were firing for 2-3 seconds before he dropped. It only takes one hit to trigger the bleed-out animation, yet he kept fighting like a champ until one of the SMG guy's rounds decided to register. You get kill assists for suppressing enemies too. Perhaps rifle guy put him into full suppression (with the help of SMG guy) and SMG guy got the lucky hit to register?

I know there's problems with this, I'm just not sure of this video in particular. I don't know how many leg and arm hits will kill in the game. I know one is enough to start you bleeding and you'd die if you didn't bandage. All I know is that what I saw from the pov of the vid is several leg and arm hits, several misses, 1 torso hit then death then another torso hit. I can't see the aiming of the other player so I can't see where he is hitting or how often.

I don't know what the bleeding animation looks like, I'm only familiar with the "slow death" animation.

[MarioBava]

Originally Posted by derbefrier

Heh that's what we are talking about.

I'd think bayos and bullets would be different issues, but maybe they are related.

[WaltherPPK77]

Perhaps some part of the hit detection issues have to do with auto-reload or clicking the mouse really fast. Take a look at the video below and watch how strange the bullet impacts are.

Auto-reload is on and I'm playing with bots on a public server. 100 ping.

I did post this in The Bug Report also.

Red Orchestra 2 AVT unlimited ammo auto-reload bug - YouTube

[Josef Nader]

Originally Posted by MarioBava

I'd think bayos and bullets would be different issues, but maybe they are related.

I don't know about RO2, but most FPSs use the same gun mechanics to do melee. It's basically just an invisible bullet with a very short range and a different firing animation.

[6S.Manu]

I dont have Fraps but I just tested with my teammates. I've screenshots.

It's true: a bandaged part of body can't be wounded again... (2 magazines of pphs is not enough)

But also rifle's shots penetrate brick walls (the one of the church in Spartanovka) and you can kill through the wall of Obj A in Commissar's House firing from inside to outside (but not the opposite) using Pistols!!!

This game is a Mess!

Edit2: MG34 set up for 400m hits perfectly at 250m...

[PapaGreg]

PLease, no news from DEV about this problem ???

Please, this hit detection is so poor in cqb, need a fix !

[Stahlhelmii]

Originally Posted by PapaGreg

PLease, no news from DEV about this problem ???

Please, this hit detection is so poor in cqb, need a fix !

QFT. This is a BIG, game-breaking issue that many of us have been absolutely plagued with since the first day of beta.

[Synesthesia]

"nothing is wrong" dev post coming in 3... 2...

[Josef Nader]

Quoting myself from the other thread about this:

Originally Posted by Josef Nader

The reason TWI don't have any answers for us is because we can't reproduce it with any consistency. It's impossible to fix a bug if you don't know how it works.

Until we can replicate the hit detection issue, TWI doesn't stand a chance in hell at fixing it.

It's like if your cell phone shocked you at random intervals for no apparent reason regardless of the circumstances. The manufacturer looked at it and says that they can't figure out why it would do something like that, and you don't know how to make it happen on command so they can figure out how to fix it.

[PapaGreg]

The fact is this : Hit detection sucks . anybody who played this game now it : in CQB so bad detection.

Thats not to the player to proof the fact, DEV just have to play in close range to see it. But are they capable to fix it ? i doubt

Anyway, if hit detection isnt fixed . this game will never be played for a long time.

[Stahlhelmii]

Originally Posted by Synesthesia

"nothing is wrong" dev post coming in 3... 2...

Hmmmmm ... no "nothing is wrong" post ... nor any post acknowledging it. Why am I getting the horrible feeling it's just being ignored because they can't fix it?