Bug: Paik's EMG-X Scanner Not counting Enemies Spotted towards Mastery Progress
Product: Battlefield 2042
Platform:Steam-PC
Please specify your platform model. PC
AMD or Nvidia Model Number Nvidia GTX 1080 Ti
Enter RAM memory size in GB 16 GB RAM size
Are you using any software with an overlay? Yes
If yes, can you list them here? Nividia Geforce Experience Overlay
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? Breakthrough
Please select your region North America
On which server did this happen? Official Public server
When did this happen? (dd.mm.yy hh:mm) 25/11/21 13:07
Summarize your bug Paik's Mastery is not being tracked properly, Enemies Scanned is not tracking, Only Assists.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Play in either Multiplayer or Solo/Co-Op, check your progress with Paik's EMG scanner by either going to your badge section of your player card, or check under loadout customization for the Specialist on your progress. Run into a group of enemies with the scanner on, If multiple enemies are scanned, check progress on the scanner if its tracking Enemies Scanned.
What happens when the bug occurs? The Scanner is not Tracking Enemies Scanned towards Paik's Specialist Mastery, it only tracks Kill Assists when the scanner is on, and in range of an enemy.
What should be happening instead? The EMG-X scanner should be tracking Enemies Scanned and counting towards the mastery rank.
Got a bug regarding Paik's EMG-X scanner not tracking Enemies Spotted with the gadget, I had already tried validating the files and even reinstalling the game and testing this a few times already. And it just keeps happening no matter what I do.
So, I have a few screenshots to prove whats happening, As the requirements for Tier 1 are just "Assists and Enemies spotted with the EMG-X Scanner" Which means, Enemies Spotted should suffice, but it does not, it only tracks assist kills with the scanner.
EDIT AS OF 3/12/2021 @ 4:06 AM EDT: The bug is still existing even after the most recent patch that just launched today, did some additional testing just to make sure.
