New Recon K31/43 rifle doing Zero damage

@flyinghorse101 All set ups its just random whether it works or not i can link a vid of the bug happening before the patch that it acts the same as that bug. They definitely fixed the accuracy but not the hit reg for the gun its a toss up whether it works or not.

https://answers.ea.com/t5/Bug-Reports/The-effect-of-high-power-optics-of-K31-43-does-not-occur/td-p/9278944/jump-to/first-unread-message

Another topic about this. 

If you have quick aim + 6x scope it doesn't work. With other specs it works.

Yeah and the worst part is that my rifle is rank 3 and i cant respec. G * G

Product: Battlefield V
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number GTX 2060
Enter RAM memory size in GB 16GB
Are you using any software with an overlay? Yes
If yes, can you list them here? Nvidia, Discord, Origin.
If you disable this software, does that have any effect? No
Which part of the game is the issue happening in? Multiplayer
Which part of the mode? Conquest
Please select your region Europe
On which server did this happen? All of them.
When did this happen? (dd.mm.yy hh:mm) June 4th 2020 and after
Summarize your bug Generally, I think it is a hit detection bug, but might be something else. First, when I picked the K31/43 up it was a level 4 with the bayonet, and I love bayonet-type weapons. I found it cool that it had a scope and iron sights to go along with it, the perfect Scout weapon. But the more I used it I noticed something, the bullets almost never registered. No matter how easy of a target it was. I get kills with it I do, and my aim is not as horrible as you think. The reason why I'm calling it a bug is because 1. It plays the headshot sound but no hitmaker. 2. It shows the enemy character flinching with blood coming out of them but now hiit marker. 3. Hitting them a 2nd or 3rd time doesn't kill them, which is weird considering its a two-hit weapon. 4. I know it's not skill-related because no other sniper acts this way. Never seen flinching with blood and no-hit market. Hopefully, this is something that you're already considering fixing or at least know about.
How often does the bug occur? Occasionally (10% - 49%)
Steps: How can we find the bug ourselves? I'd say place a sniper with the K31/43 in a good position using the Scope. And have one or more testers in the enemy team run around and try to hit them. Do this at a reasonable distance. And you can see the bug. also if possible record in slow-motion, so it's easier to spot the error.
What happens when the bug occurs? Enemy player shows signs of damage but no hitmaker, nor damage actually occurs. Usually happens with scoped on the K31&43
What should be happening instead? The enemies should be hit, with blood accompaning by a hitmarker and a possible spot if you use the correct class. As well as a headshot hitmarker when the head is hit.

‌

I usually play Conquest on the bigger maps. And when my team is losing I always go Scout to sneak behind enemies and then place a beacon and then we surround them. I've used the Pistol Carbine in the past until I noticed the K31/43 has an iron sight and scope mode on it. And I thought it would be much better. Which it is, when it works like 50% of the time. Because most of the hits, I actually do hit never register. No hit sound, marker no nothing. I know I hit because I see the blood and the flinching. In my report, I go more into detail about the issue. 

I can confirm that even with the latest BF5 update, i can't shoot anyone and damage them if i have the 6x integral scope specialisation on K31/43 rifle. I hope it will get fixed, since the latest update was said to potentially be the last one for BF5.

Anyways, no hit reg (until changing weapons, bugged for the entire round) for me has also rarely occured on other guns, randomly. For example, the Trench carbine (which happened to have a 3x scope when it randomly happened) of recon kit. Maybe it means something, as many previous updates I never seen this issue, on any gun, so it might have been some update that bugged something.

In the case of K31/43, the issue disappears immediately as soon i remove the specialisation of 6x integral scope.

It's not possible to ever hit anything with it, so it should be easy to reproduce for the devs..