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

PC - Equipped cosmetics return to default after previewing/equipping a different cosmetic piece

Lenny197
Lenny197 Member Posts: 297
edited July 2022 in Bug Reporting
https://youtu.be/UVxbhrn-S0Y

DESCRIPTION:

This bug causes it to be difficult for people who want to mix and match cosmetics in the store when you cannot preview cosmetic pieces without it returning to default. And equipping a cosmetic piece causes the same thing so we have to go back to the loadout and equip it again.

Steps to reproduce:

Step 1 : Boot the game

Step 2 : Equip cosmetics for survivors or killers

Step 3 : Go to the store

Step 4 : Click on a cosmetic piece and notice how the other pieces turn to default

Step 5: Equip a cosmetic piece and return to the survivor lobby

Step 6: Open loadout to see that the pieces are still equipped but it's somehow default

ADDITIONAL INFORMATION

  • Character played: Any characters
  • Frequency of the issue: Always
DeadByDaylight.log


Post edited by Lenny197 on
11
11 votes

Acknowledged · Last Updated

Comments

  • Tsukah
    Tsukah Member Posts: 390

    Happens on consoles as well

  • wayhaught
    wayhaught Member Posts: 5

    Every time I wanna try on a new cosmetic piece with an outfit I already own I can’t. I’ve stopped buying cosmetics at all because I can’t preview if they’d look good with other pieces or not. Until this gets fixed I’m not buying anything for this game anymore, because I don’t want to waste auric cells or shards on a cosmetic if I can’t tell it will look good with other things. Very frustrating.

  • Lenny197
    Lenny197 Member Posts: 297
    https://forum.deadbydaylight.com/en/discussion/comment/3102848#Comment_3102848

    It said that this was acknowledged but I reported this on patch 6.1.1 now we're at 6.1.2/6.1.3 and a small bug like this hasn't even been fixed yet.