To make a bug report please head over to: https://app.betahub.io/projects/pr-5642738318
Once you have signed in, on the right hand side you can use the "report bug" button to be able to fully report the bug you've encountered. Thank you.
Interested in volunteering to help moderate for the Forums? Please fill out an application here: https://dbd.game/moderator-application
Kill Switch update: We have temporarily Kill Switched the Forgotten Ruins Map due to an issue that causes players to become stuck in place. The Map will remain out of rotation until this is resolved.

http://dbd.game/killswitch

PC - Weave Attunement Display Error

HankeryDankery
HankeryDankery Member Posts: 2
edited September 2024 in Bug Reporting

SUMMARY OF THE ISSUE: The icon that allows you to know if you are being inflicted by the perk Weave Attunement will be permanently affixed onto your screen as survivor without any way to get rid of it. I believe the issue is caused by losing the oblivious status effect early after gaining it, ie, with Vigil.

ADDED NOTES: I believe Vigil is causing this because I am normally playing in a group, and I'm the one routinely using the perk, and also the only one ever getting hit with this bug.

PLATFORM: PC

STEP BY STEP INSTRUCTIONS ON HOW THE ISSUE OCCURED:
1.) Killer with the perk Weave Attunement.
2.) Survivor loses their item, and then picks it back up becoming inflicted with Oblivious from Weave Attunement.
3.) Survivor is running vigil, or a nearby survivor is running vigil.
4.) Oblivious status effect ends on the survivor afflicted by Weave Attunement.

VIDEO: My friend and I went into a custom game after a live game to try and replicate the glitch, but it is my most recent live game.
Link: https://youtu.be/lbEokdfOpVc

PLAYER LOGS:

Post edited by EQWashu on
2
2 votes

Duplicate · Last Updated

Thank you for taking the time to report this. Please upvote, or add any additional information, to the initial report here: https://forums.bhvr.com/dead-by-daylight/discussion/428322/weave-attunement-icon-bug#latest

This discussion has been closed.