Currently, in The Division 2, it happens that hits are not registered. Enemies take no damage. Massive is on it.
This is the issue: For some time now, there have been increasing complaints that damage in The Division 2 is problematic. It happens that you empty an entire magazine into the enemy, but they take no damage.
According to Massive, this is a problem with “hit registration”, meaning the game does not register that you are shooting bullets at the NPC enemy.
When this problem occurs, no damage is calculated, and no damage numbers are displayed. This is frustrating and diminishes the gaming experience. All platforms (PS4, Xbox One, PC) are affected.
What is Massive doing about the problem?
These are the efforts: Last week, Massive made changes in the background to mitigate the problem. According to initial feedback, this measure was successful – the damage issues occur less frequently – however, they are not completely resolved yet.
Therefore, the developers now ask you to provide further information about the problem. Should you find yourself in a situation where you shoot an entire magazine at NPC enemies without the damage being registered, you may provide your Ubisoft username and platform username here in the Ubisoft forum and describe during which activity the problem occurred.
This way, they aim to pinpoint what is causing the poor hit registration.
What does the community say? A look at the comments shows that the issue is still very current and requires investigation.
- “The fact that bullets are not registered is still a problem. I unloaded an entire magazine of an M60 into a red NPC, and only the last bullets were registered,” wrote a user a few hours ago.
- “I experienced several [of these issues] yesterday,” writes another.
- Activities mentioned particularly include PvE content like Roosevelt Island and the raid, but also the Dark Zone. Damage reportedly sometimes does not count against PvP enemies either.
- With specialization weapons like the crossbow or grenade launcher, the issue is still reported frequently.
- A user is glad this problem is finally being addressed. Sometimes he was unsure whether he was lagging or if it was really a game problem.
- Additionally, several agents refer to a new sound problem that has occurred in the last few days. According to Massive, they are also currently collecting feedback on that.
Have you also encountered this problem? In what situations did it occur?
