Holographic sights(1x scope) for stg44 bad performance

[4ilk]

Product: Battlefield V
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number nvidia geforce 1060 6g
Enter RAM memory size in GB 16g
Are you using any software with an overlay? No
Which part of the game is the issue happening in? Multiplayer
Which part of the mode? TDM
Please select your region Asia
On which server did this happen? all
When did this happen? (dd.mm.yy hh:mm) 25.8.2019.18.3
Summarize your bug Holographic sight for stg44 is bad. Has white noises on it.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Use Holographic sight for stg44 or other guns with the same type of 1x scope. Set color to (255, 0, 0) pure red. Set halo to 100% or 200%.
What happens when the bug occurs? The sight seems mixed dynamic pixels of red and white .And the texture of the sight seems low quality and resolution.
What should be happening instead? High quality sight.

‌

The original issue and discussions I created here.

https://answers.ea.com/t5/Technical-Issues/Holographic-sights/m-p/8149361/highlight/false#M17583

[4ilk]

my holographic sights look disgusting.these two images show the sights with halo at 100% and 200%.these white pixes are strange.

my graphic setting is all very low.

[IIPrest0nII]

@4ilk 

Any changes if you set graphics settings to high?

[4ilk]

No change. I try to set every single slot to high or very high. No one makes any difference. The circle shape holographic sight is ok, just this one looks not good.

[IIPrest0nII]

Let's see if deleting Settings folder will make any changes. Go to My Documents>>Battlefield V and delete Settings folder. If this doesn't help, then I assume this is a bug and should be reported here: https://answers.ea.com/t5/Bug-Reports/bd-p/battlefield-v-bug-reports-en

[4ilk]

Nothing changed. I tried to delete settings. And also tried to reset all settings.

The sight's default color is close to yellow, and that is the only color makes the sight seems ok.

I will try to report it as a bug.

Thanks for helping.