Please check if your issue has already been reported first!

When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
The second iteration of 2v8 is now LIVE - find out more information here: https://forums.bhvr.com/dead-by-daylight/kb/articles/480-2v8-developer-update

[PC] Oni unable to activate blood Fury if power gauge reaches 100 charges

Kingjaffad
Kingjaffad Member, Alpha Surveyor Posts: 49
edited July 2020 in Bug Reporting

Platform: PC

Version: 4.0.2

Description: The Oni is unable to activate blood Fury if power gauge reaches 100 charges passively. Whereas normally the power gauge's passive would stop at 98 charges, the Oni can now reach 100 charges passively. Doing so however will lock the Oni out of using their power, despite pressing the active ability button. The only way to undo this affect is to hit a survivor with your primary attack.

Steps to Reproduce:

Step 1: Start a match while playing as the Oni

Step 2: Obtain blood orbs, but do not absorb enough to fully charge the gauge. (You may also wait for the gauge to fill passively, I am simply recommending you atleast fill the gauge halfway or three quarters to save some time.)

Step 3: Let the gauge passively charge up to 100 charges. The gauge will appear full, the text prompt will appear at the bottom of the screen along with the audio prompt. But attempting to activate the power by pressing the active ability button will result in nothing happening.

Step 4: To fix this, simply hit a healthy survivor with your primary attack. This does not seem to work with injured survivors, since the action would not offer any progress to the power gauge.


Attached with this report is a short recording of an Oni match where I replicate and demonstrate the issue.

https://youtu.be/-gNoId2LgsA

1
1 votes

Acknowledged · Last Updated

Comments

  • SciTutor
    SciTutor Member Posts: 4

    Was going to make this exact post, but for PS4. So, just gonna leave a comment here and say this bug also applies to PS4 for whoever reviews this.