Delay on using Quell

Warhammer 40,000: Darktide Bugs
1

Issue Description:
Reaching 100% peril multiple times within a short time will cause a 2-3 seconds delay before you’re able to use quell.

Steps to Reproduce:
Reach 100% peril multiples times in a short time.

Platform:
Steam

Reproduction Rate:
100%

Upload Supporting Evidence:
After every brain burst, i hold R, but as you can see, there is a VERY LONG delay before it starts quelling.

Same thing happens if you use a staff instead.

4 Likes
2

I too experience this, good catch on the increasingly longer delay between ulting and quell actually firing off.

1 Like
3

100% reproduceable. Bug currently makes Psyker a lot less effective than before. Please update on expected timeline of fix, or at least if intended clarify intentions. Appreciate the support <3

2 Likes
4

Happens consistently after hitting 100% twice in a row. So if you quell and go back to 100% twice in a row, the third time will stick.

2 Likes
5

Muah, it is not guaranteed.

I can only, reliably make this bug occur on BB and Force Sword (Push Attack). It does prevent quelling for all weapons as well as hand if you hit the threshold on Force Sword or BB.

Staffs do not trigger this, at least not Purgatus or Surge, haven’t tested Voidstrike.

1 Like
6

Wrong, it does happen with staff and also happens with force sword.

And yes it happens as I described it. Hitting 100% multiple times in a row. A guy on steam forums gave more details. How the new Brain Blast Psyker Quell Mechanic SEEMS to work :: Warhammer 40,000: Darktide The Mourningstar - General Discussions

1 Like
7

It happens with BB and with Force Sword Push Attacks.

I’ve just done several tests on Surge and Purgatus and they will still quell even if you hit 100% several times in a row. Staffs are not affected by this.

If you do, however, swap from BB/Force Sword to quell on staff - yes, it is affected too. But staffs functions as normal otherwise.

1 Like
8

It happens on Trauma staff, so only some staffs it seems

1 Like
9

And Voidstrike…

It definitely smells like a bug that happens if you go too far beyond peril and is likely an issue with the new fix to peril quelling…

2 Likes
10

Also happens with Purgatus, if you just charge up the secondary beyond 100%, quell a little and then charge over 100% again without firing the staff it will happen.

This can also be replicated on Surge

1 Like
11

This makes it feel like you are lagging and your controls are not responding, which if working as intended is just pure Heresy in a first person shooter environment.

12

I want to also point out how much harder this makes the “Brain burst 5 different specials in 12 seconds Penance.” Especially when brain burts damage is so bad at later levels that it takes multiple bursts to kill most specials.

1 Like
13

It happens with surge and purgatus staff if you charge but don’t attack. Charge to 100%, quell, Charge to 100% quell, charge to 100% try quelling.

2 Likes
14

The fact that the devs haven’t acknowledged this as a bug yet is very telling.

I have no words.

1 Like
15

It happens with surge and purgatus staff if you charge but don’t attack. Charge to 100%, quell, Charge to 100% quell, charge to 100% try quelling.

Confirmed as well. It can be even worse if you try to quell while holding the charge. Quickly release right click → quell before the animation goes to neutral can lock you in the charge animation for a few seconds, then it will go to neutral and still block you from quelling for a few seconds.

1 Like
16

You think they should just remove Psyker at this point if they want to make it this Unpleasant to play. They only Added Psyker so they could make it 4 classes not 3.

17

Yes, but that is a super fringe case problem, you wouldn’t keep charging your staff to 100% if you can’t fire it before 97%.

In any case, your report needs to be structured like the below, otherwise they have no clue what is going on, what could be the cause and where to start looking:

Issue Description:

  1. Brain Burst can on subsequent quells after reaching 100% peril every time stop responding to active quelling in which it appears to be unresponsive.
  2. Force Sword can on subsequent quells after reaching 100% peril every time by push attacking stop responding to active quelling and hangs for a few seconds.
  3. Voidstrike and Trauma Staff can on subsequent active quelling after reaching 100% peril every time after an attack stop resonding to active quelling and hangs for a few seconds…
  4. All Staffs can on subsequent quells after reaching 100% peril by charging (but not attacking) every time stop responding to active quelling and hangs for a few minutes.

Steps to Reproduce:

  1. Hit 100% Peril with Brain Burst → Quell to 97% peril → Brain Burst again → Quell to 97% peril → Brain Burst again → Quell.
  2. Hit 100% Peril with Force Sword Push Attack → Quell to 99% peril → Push Attack Again → Quell to 99% peril → Push Attack again → Quell.
  3. Hit 100% Peril with Voidstrike of Trauma Staff secondary attacks → Quell to 90% peril → Hit 100% peril again with a Secondary attack → Quell to 90% peril → Hit 100% peril with a secondary attack → Quell.
  4. Charge any staff to 100% peril → Quell to 99% peril → Charge to 100% peril → Quell to 99% peril → Charge to 100% peril

Reproduction Rate:
Frequent

Supporting Evidence:
A video of each use case and how to reproduce it.

Bug Reports needs to be extremely specific otherwise they are unholy useless and it may seem super redundant and you need to be honest. It is not always that it does it, but it does it frequently.

Don’t get me wrong, I find this extremely annoying as well that it slipped through the QA… Honestly, I don’t know what their QA is doing, but they’re certainly not trying to break the game as they ought to be trying.

18

Dude, the released the patch 1 hour before Swedes go home from work, by the time this was discovered - an hour later. They would already have packed their bags and gone home for the day. Just keep this at the top and also…

Yo @Aqshy
We seem to have a problem.

19

Yup, we’re aware and it’s been passed to the team. Thanks!

20

Thanks a bunch =)!

Sorry for the ping, but people were getting… conspiratorial :slight_smile:

1 Like