List of bugs for Nurse

Steam - PC

1) Blinking randomly stops working and gives an infinite audio loop as if you were charging your blink. This forces you to let go of M2 and wait a few seconds before being able to use it again. (Sometimes it will randomly blink a short distance)

2) Randomly after blinking you are not immediately M1 at times and you have to wait a second before M1'ing again.

3) When attempting to blink up (knowing its an empty space above me) sometimes you'll continue to just blink straight.

4) When attempting to blink through an object (ie a pallet or wall) sometimes it just refuses to blink through it and you end up blinking right into the wall/pallet.

1 if not all of these issues usually occur every match.

Tagged: Pending

Comments

  • Oh yeah. I was told by a Dev; not naming names. They're "aware' of the bugs but they arent sure how to recreate them. Like how can you not recreate bugs that every single nurse player encounters over and over and over again?

  • @Ivaldi said:

    https://forum.deadbydaylight.com/en/discussion/comment/1928069#Comment_1928069

    Oh yeah. I was told by a Dev; not naming names. They're "aware' of the bugs but they arent sure how to recreate them. Like how can you not recreate bugs that every single nurse player encounters over and over and over again?

    Because it's not specific and it's not detailed in the explanation on how it happens. It doesn't happen every game, it happens in some games. If I knew the exact thing that causes it I would write the steps to reproduce it.

    Let's put it like this. You have a piece of code that is used for the Nurses blink and there are a few codes running simultaneously with it (concurent actions or as programmers refer to as threads). So basically, if one piece of code intercepts the other (lets say the Nurse gets stunned and the process has to aknowledge it the codes get simultaneously activated), that just might be the cause of it, but it has to happen at a specific time when it occurs. The code for Nurses blink might get stuck in a loop because of it, so they know where the problem is and they can fix it.

    But if they don't know what caused it, they don't know where to fix it. Reworking the code for the Nurse blink doesn't make sense cause it can screw up other stuff and the best they can do is patch it when they find the problem. And the problem can be anyware. It might be the add-on combination, it might be the perk combination, it might be the offering combination, it might be the animation interaction.

    So let's do some math: you have 25 killers which means 25x3 = 75 killer perks + perks that aren't associated with each killer. Let's stick to killer perks only. You chose one out of 75, you still have 74 more to choose for second. You chose another perk and then you are left with 73 choices for the third. Repeate the same process for the forth and you can choose 1 out of 72 choices. So there are in total 75x74x73x72= 29.170.800 combinations. And you have to take into account that you don't want to repeat the perks in a different order so you have to divide with 1x2x3x4 = 24. So you get a total of 29.170.800/24 = 1.215.450 killer perk combinations that need to be tested. So add to the numbers survivor perks, add-ons & offerings and the numbers just go higher. It's not efficient, nor easy to test this for every issue reported, beacuse of the number of combination and that's why they didn't figure the issue out. Which is why if you don't know what causes it, it's very hard to figure out.

    If you know the cause of it, it's easier to patch and that's why they ask for instructions on how to reproduce it. And they also have the logs (which non of us attached) that detail the order of actions that happened, so they can follow up the the course of action that led to the issue.

  • @sharkster13 said:

    https://forum.deadbydaylight.com/en/discussion/comment/1930353#Comment_1930353

    Because it's not specific and it's not detailed in the explanation on how it happens. It doesn't happen every game, it happens in some games. If I knew the exact thing that causes it I would write the steps to reproduce it.

    Let's put it like this. You have a piece of code that is used for the Nurses blink and there are a few codes running simultaneously with it (concurent actions or as programmers refer to as threads). So basically, if one piece of code intercepts the other (lets say the Nurse gets stunned and the process has to aknowledge it the codes get simultaneously activated), that just might be the cause of it, but it has to happen at a specific time when it occurs. The code for Nurses blink might get stuck in a loop because of it, so they know where the problem is and they can fix it.

    But if they don't know what caused it, they don't know where to fix it. Reworking the code for the Nurse blink doesn't make sense cause it can screw up other stuff and the best they can do is patch it when they find the problem. And the problem can be anyware. It might be the add-on combination, it might be the perk combination, it might be the offering combination, it might be the animation interaction.

    So let's do some math: you have 25 killers which means 25x3 = 75 killer perks + perks that aren't associated with each killer. Let's stick to killer perks only. You chose one out of 75, you still have 74 more to choose for second. You chose another perk and then you are left with 73 choices for the third. Repeate the same process for the forth and you can choose 1 out of 72 choices. So there are in total 75x74x73x72= 29.170.800 combinations. And you have to take into account that you don't want to repeat the perks in a different order so you have to divide with 1x2x3x4 = 24. So you get a total of 29.170.800/24 = 1.215.450 killer perk combinations that need to be tested. So add to the numbers survivor perks, add-ons & offerings and the numbers just go higher. It's not efficient, nor easy to test this for every issue reported, beacuse of the number of combination and that's why they didn't figure the issue out. Which is why if you don't know what causes it, it's very hard to figure out.

    If you know the cause of it, it's easier to patch and that's why they ask for instructions on how to reproduce it. And they also have the logs (which non of us attached) that detail the order of actions that happened, so they can follow up the the course of action that led to the issue.

    I use double recharge add-ons with pop/bbq/discordance/corrupt and literally reproduce this bug every single match.

  • @Ivaldi said:

    https://forum.deadbydaylight.com/en/discussion/comment/1933041#Comment_1933041

    I use double recharge add-ons with pop/bbq/discordance/corrupt and literally reproduce this bug every single match.

    Which double recharge add-ons specifically?

  • What do you mean which? There's literally only two.. Fragile Wheeze and Dark Cincture