Gladiator bug

[XCAL1BRO]

I've been trying to beat Gladiator on nightmare for a few hours now, and am consistently getting through first stage without any headaches, but the second stage felt impossible.
Decided to look up "No damage" vid on youtube to see if i'm doing something wrong, and apparently I'm not, the game does!
There are 2 sets of attack on 2nd stage where gladiator can get staggered right after he stops spinning his flail: 1 from afar, and for another he gets close range. But on the current PC version of the game the second attack is bugged: the sound queue for counter is heard the moment he STARTS spinning his flail, not STOPS. There is no counter window for this attack, therefore he can't be staggered, and those attacks are damn near impossible to avoid, so say goodbye to most of your health, after which one more long range attack is enough to finish you off.
That issue wasn't present in PS4 version, on which "No damage" fight was recorded. Every time the flail starts spinning, as soon as it stops there is counter window.
UN seems impossible right now, when there is literally no way to avoid the most damaging combo. When really lucky I can get maybe 60% through stage 2, but it really isn't worth the headache.
I'm gonna take a break, play something else for a week or 2, hopefully it's gonna get fixed soon.

[Achselis]

Took me 3 UN attempts to kill him and i agree, his stagger seems to be very inconsistent, sometimes completly ignoring damage after the sound queue.

[DarkMan]

Thanks for the heads up... yea, I'm working through UN at the moment so will wait for hopeful patch update to finish. Dang... bummer that that is.

[Judge Lazar]

I had a ♥♥♥♥♥ of a time on that second part as well.

If he gets too close while spinning his flail you don't get an opening to attack. Like not a bug, it's just an instant smash that ♥♥♥♥♥ you up. You have to stay far enough away. He does not freeze like normal enemies when you glory kill or chainsaw fodder either so only do it if he's far away and don't worry about the opening to attack for that cycle, just get away from him.

When he slams his flails down and has you pinned between them with the wavy fire lines, hit him with lock on bursts with the rocket launcher it does HUGE amounts of damage when he's in that phase. Also be aware that when the yellow walls disappear, you will still take damage if you touch his flail chains too soon. When he flashes green dodge out of the way and make some distance. You CAN hit him there, I did it once on accident, but it's better to just GTFO. You should be able to kill him in 3 or 4 cycles if you hit him with the rockets on that phase.

If you're having a really hard time dodging the wavy fire lines you can hold your weapon wheel key to slow down time and get a better idea where you need to be standing. It's cheese and not perfect but it gives at least a slight bit of leeway there.

[XCAL1BRO]

Originally posted by Judge Lazar:

I had a ♥♥♥♥♥ of a time on that second part as well.

If he gets too close while spinning his flail you don't get an opening to attack. Like not a bug, it's just an instant smash that ♥♥♥♥♥ you up...

I made this post only after I made certain that there is a bug.
https://www.youtube.com/watch?v=VCTAJtoEMDM&t=292s
Here is the link to vid I was referring to. The attack is at 4:25. You can clearly see that even when he is getting close there is a counter opening when he drops flail. When I tried I heard counter opening sound going off WAY too soon. It's a bug. If you get lucky he will only do this attack once or twice, and you can survive that, as long as you're able to evade all of his other attacks and deal damage fast. But it doesn't make it any less sucky.

[Judge Lazar]

That's just his normal opening, you can tell because he stops moving a second before he drops his guard and far enough away. What I'm talking about there's no sound because there's no opening, he just hits you. I think the sound being jacked up is on your end. Can't find anyone with the same issue. Not trying to argue about it or say you're wrong, I dunno what to tell you.