We have temporarily disabled The Houndmaster (Bone Chill Event queue) and Baermar Uraz's Ugly Sweater Cosmetic (all queues) due to issues affecting gameplay.

Visit the Kill Switch Master List for more information on these and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
The Dead by Daylight team would like your feedback in a Player Satisfaction survey.

We encourage you to be as honest as possible in letting us know how you feel about the game. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.

Access the survey HERE!

Killer sensitivity is too high (even at 0%), while the Survivor one is perfect.

ScoobyDoo
ScoobyDoo Member Posts: 20
in Feedback and Suggestions

Hello!

So, here's my story: now that Dead by Daylight supports the Linux devices (and I thank the developers for that ♥) I got back into one of my most favourite games! However, I quickly noticed that the sensitivity is too high for me and thus I decided to lower it in the Game Settings. I ended up setting it 0% for both Survivor and Killer. And for Survivor it worked perfectly, I can comfortably play without any problem. But the Killer one is still way too high, to the point where I have to change my mouse DPI when I play the Killer role. And, while it solves the problem, I'm not quite satisfied with this.

Which brings me to the question: is there any way to adjust the Killer sensitivity (beyond the Game Options slider) to circumvent the issue?

Thank you in advance!

Best Answer

  • ScoobyDoo
    ScoobyDoo Member Posts: 20
    Answer ✓

    Update:

    I remembered that I used to have vsync disabled back in the days, and thus I've decided to do the same now. I copied the launch options from another game that I play via Steam on Linux (which is «PROTON_NO_ESYNC=1 PROTON_NO_VSYNC=1 gamemoderun %command%»). And now the Killer sensitivity is perfectly fine. I'm not exactly a tech savvy person, so I can't say how it fixed the issue, but it did. So, I suppose there's that :)

Answers