Rashad Combat axe headshot registration

[Spad]

It is abnormally hard to hit the heads with this weapon with the heavy melee (overhead hit).

Even in the Arkanium with non moving ogryn targets it’s not possible to hit the heads consistently.

Please make it like the Antax combat axe which has pretty much the same set of moves but does actually hit the heads normally.

[kevin.a.babcock]

I see this as acknowledged and I had hoped it would be in the latest hotfix, but it was not. Please fix in the next round of hotfixes. I can land 1/6 headshots on a static Crusher in Psykanium, unlike Antax at 6/6. The heavy overhead appears to be the same animation.

Edit: it’s not just heavies that are affected. It’s weakpoint registration for light and heavy attacks. This makes the “Finesse” trait only useful for attack speed and crit damage, but not weakspot damage.

[Ralendil]

Next patch?

[gordonz88]

Fatshark forgor

[Ralendil]

Again not FIXED

[gordonz88]

This is really really sad. Conceptually, I feel like the Rashad has its place as a faster but weaker Antax Mk V. But, like you said, it’s literally useless without consistent headshot registration. If we want to play combat axe, the Antax is literally our only option because the Achlys combos are also straight up unuseable (and that’s saying something, as I generally believe the majority of weapons have a usabable combo for most situations).

Fatshark, PLS.

[kevin.a.babcock]

I have found that I can hit more headshots with the Rashad when I position the screen so that the Crusher’s head is on the bottom edge of my monitor 1/3 of the way to the left or right from center (the opposite direction from where the top of the heavy swing begins). It’s basically looking straight up (you can more reliably - not 100% - connect with noggin at the bottom of your swing). Not ideal, to say the least.

[gordonz88]

Yup. Some weapons in Vermintide 2 were like this, and from my testing it seems to be due to a unreasonable wide and boxy weapon hitbox (especially the “handle/shaft”) that hits the shoulder or body of the enemy first. Looking straight up is sometimes the only way to semi-reliably hit headshots, but that’s a ridiculous thing to have to do.

[Ralendil]

Again… not fixed.

[zaygr]

SgtAngua comments on And yet again the Rashad Mk II has not been fixed… (reddit.com)

Someone found the hit priorities. It’s probably the same thing that affects a lot of Ogryn weapons and the Plasmagun too.

Antax:

local hit_zone_priority = {
[hit_zone_names.head] = 1,
[hit_zone_names.torso] = 2,
[hit_zone_names.upper_left_arm] = 3,
[hit_zone_names.upper_right_arm] = 3,
[hit_zone_names.upper_left_leg] = 3,
[hit_zone_names.upper_right_leg] = 3

Achlys:

local hit_zone_priority = {
[hit_zone_names.head] = 1,
[hit_zone_names.torso] = 1,
[hit_zone_names.upper_left_arm] = 2,
[hit_zone_names.upper_right_arm] = 2,
[hit_zone_names.upper_left_leg] = 2,
[hit_zone_names.upper_right_leg] = 2

Rashad:

local hit_zone_priority = {
[hit_zone_names.head] = 2,
[hit_zone_names.torso] = 1,
[hit_zone_names.upper_left_arm] = 3,
[hit_zone_names.upper_right_arm] = 3,
[hit_zone_names.upper_left_leg] = 3,
[hit_zone_names.upper_right_leg] = 3

[Ralendil]

Lol.
Thanks for your post… but if it is the problem…It means that FS could fix the problem so quick and let this bug since december 22th without trying even to fix it…

[zaygr]

If it’s deliberate (which would be doubly weird because Rashad has the best weakspot damage of the three) it may be that they were going for a finesse combat axe where you only get the headshot damage if you only hit the head… but the way it turned out is that it’s unintuitive and frustrating to play with.

[Ralendil]

well, it is more than unintuitive if when you hit the head you… don’t hit the head.
As I said, with this weapon, BM doesn’t really work.

[zaygr]

The unintuitive part is definitely if the cleave even touches any other part of the enemy it invalidates the headshot because of the priority list. It’s a really bad way of doing it.

If they wanted to do it properly it needs to take into account hit order too. Like head → body will always be a headshot but body → head probably won’t unless you had enough cleave or something. Plasmagun should be checking if the head or torso is behind the arm or leg because it definitely has enough cleave, etc.

Melee games like Overgrowth, For Honour, Mordhau and Chivalry have struggled with multi-part-hit-on-single-target hit detection for years and they all implement different ways of doing it.

[Ralendil]

Totally agree with you…

But for now, I ask them that Head is put has 1 in priority.

[Spad]

I wish someone from Fatshark would give any comment on this subject. I would understand if its not a priority but… this is clearly easily fixable, and at this point seems to be a deliberated choice and not an acknowledged bug. So which one is it? A bug that is taking 6+ months to change 1 number in the code?