Devs just watch this and explain please.

lmao, you both clearly are killers main, and i get that, but his weapon didn't even touched my butt... it ended right behind the wall. If you say it's a hit, good for you but i suggest a pair glasses. No offence...

Well i could have been in his range, but a "hit" with a melee is when the weapon collider reach MY collider, and there is no hit whatsoever there.

Well i say that because i'm a dev too and working with Unreal i know how the things works. Of course the collider don't change, but it's easy fixable. If devs puts colliders in joints instead of having a "fixed" box on the model, then the hit would be physically registered on the model. Very easy to do and doesn't change anything in performance.

Yeah i can get the delay based on net data inconsistent flux, but there are tons of ways to fix this. If you make a game with 2 different perspectives, then you have to think a solution good for both type of players, because if play surv you're in third person, if you play killer you're in first. That doesn't bother killers, but survs yes.

Ok so, this is what i've understood so far from this discusssion:

1) It seems that killers main are happy how the things are because they can have hits for free to satisfy their somewhat needs. Good. They see "a butt tap" where there is clearly a WALL between my butt and his melee weapon (that hits just the air), the empty space in the middle and me. Aaaaight. Seems logic at first sight but fail.

2) Pings issues, delay issues, p2p, lags. Blabberish. I played Unreal Tournament (made with Unreal Engine in the '99) when multiplayer games were played with a 56k/s baud modem (so well far from the high speed internet we have nowadays) and hits were just perfect. No lag, no ping issues, no nothing. It was P2P and was PERFECT. That is the main reason why Unreal Engine is considered great for multiplayer supported games. Characters had active colliders directly attached to joints. So if you pointed at the arm, the character were registering a hit (melee or shoot) in that precise arm. Period. I'm a developer too. I know what i'm talking about. This is just a failure in game/concept design.

3) Killers are Behavior Interactive favourite pets, and i understand that: they sell killers, so marketing wise this is pure logic, and they don't wanna bother them too much. If killers cry because they are not able to manage 4 potatoes on the playground, Behavior Interactive give them something to be happy with, like hatchets passing straight through colliders or characters or very arguable vault/lunges. Good.

4) If you have 2 distinct perspectives (killer first person and surv third person) sorry but you have to find a way to be fair and correct with both categories. If the killer, from his perspective "hits" your butt, then from surv perspective should be visually the same, or at least very close. Just for fairness and correctness, not just for whim. I love this game, really, it's a good idea (not original but good), but that doesn't make too much sense.

5) A "cone"?! Really? Devs explained million times that and you just accept their explainations as part of a "game mechanic", just because it comes from the devs? Really? If you think so it's becuse you don't know that there are many way to fix this, easily! As Behavior Interactive developers knows very well (at least i hope they do) there is another way to register "hits" and it is a Physic Raycast. Basically it's a ray starting from an origin point placed on the killer that register every collision and returns back what it get. Is it a surv? Register a hit on the surv. It's a wall? Then register a hit in the wall. No "invisible cones" whatsoever. It's a shooting weapon? Define a range for it with a Raycast. It's a melee weapon, like for example a hammer? Attach the hit registerer directly to the hammer. Easy and it's also performance wise. So a hit it's a hit for both and nobody have something to complain anymore. Characters joints (arms and body) can be manipulated via C++ with active Inverse Kinematic thoward surv joints when Raycast register a hit. No rocket science here. Just normal trigonometry.

6) I love the game, i have almost 700 hours so i can consider myself a fan of the game, but what i've learned from my degree in game design, is that there are no issues that are unsolvable, and your job is to solve issues when you sell a game. This is not a "free-2-play". You pay for it and for every DLC. And there is also a "rank system". Why put a rank system in a game that register hits in a arguable fashion? That makes even more less sense.

I stated that i'm a developer too. I develop games everyday for different studios. I know how things works, and the picture you linked shows the old way to do this kind of stuff. Character must have colliders on bones/joints to register hits in the right spot, like this:

This is how is registered hit collisions in usual multiplayer games. Can you imagine playing COD, hitting the head, while you're shooting 2 feets right above his head? The picture you linked shouldn't be the "hit" capsule but the Unreal's standard character controller. That is the "motor" controller that drives your movements and shouldn't be used to register any hit. And btw, colliders capsule are scalable, so the dimensions of character is totally irrelevant.

My friends are the people i know personally. I didn't insult them, and i said "no offence", and they started the conversation being witty, telling me that "was a legit hit in the butt" while, "visually" it is not. I said "killers main" because for killers main the game is perfect how it is. With every killer main you speak, the game has no defect. It's pure. I play killer also, and i know how difficoult it is, but hatchets throug walls? Really? Is acceptable? Ok. I just stated that this is a problem and the fix is easy. Less than a couple of hour of work, and everybody is happy.

The "lag, ping, delay" stuff is just blabberish. If you've played Unreal Tournament in '99 you should know that the game was working great on 56k/s baud modems. 56k/s!!! Way more far than the actual high speed internet! And Unreal Tournament was just perfect and made it the perfect game at that time. Perfect synch of the players on the map, perfect hits, and that is why Unreal Engine is well known for his great multiplayer support. Moreover Unreal Tournament had collisions on every bone/joint of the character! Because a "head hit" should be a "head hit", not just a swing in the air! Probably here we are referring to an arguable final game polishing design. I mean poor game finalization. If you play other Unreal Engine titles, you don't see this stuff.

If you like the game how it is, ok, fine. I have no problem with that, i'm just saying that if you have 2 different perspectives, first person and third person, there are tons of ways to fix it. I'm not the only one who complain about "weird hits" and the devs explaination doesn't have to be accepted just because they say it has to be in that way, because isn't totally true.

I'm not assuming, but there should be colliders on the melee weapon to register an actual hit. The conical area is responsible for many of the "weird hits" that happens in game, and doesn't make any sense to design it that way, unless you don't give a f* about your product, because there more precise methods to do it without compromising the performance. There are many titles made with Unreal Engine, and this is the only one that after almost 4 years shows so many bugs and lack of optimization i ever seen.