M3 infrared scope is crashing bf5

[Compiling_Code]

Same problem on Ryzen 3700x + AMD RX 470.

[RLAgito]

@REMREM45DICE is so smart they dont test on the 3rd biggest or now probably the best hardware development company in the world..AMD. intel and nvidia fanboys confirmed lol

[Exec_Wintermute]

@REMREM45 Same Problem. Ryzen 3600 and 5700 XT.

[EA_Atic]

Hello everyone, 

We are still investigating but we need some more information. When the game is crashing using M3 infrared scope could you add a time stamp when its happening. 

We need (example below): 

• 2:45 Pm GMt+1 - game crashed using M3 infrared scope. 

Thanks again and keep the Dxdiag coming it helps a lot! 

/Atic 

[RLAgito]

It happens right when pressing right-click to look through the scope.

[nietschieten]

It immediately happens when you right click to zoom with the infrared scope.. Every time.. Its predictable

[MoonUtonight]

It is an AMD system based problem. I am running a AMD R2700 w/AMD Radeon VII. And this issue persists. Apparently EA/Dice are not going to do anything to fix the problem. Perhaps they are anti AMD. Do not even equip this weapon unless you are only going to be hip shooting it. The scope zoom is the problem. Intes. Nvidia users are fine. Its just AMD systems that are not able to use this weapon.

[MoonUtonight]

Nope. EA people asking the same tired questions: post a DXdiag. Or check this or that.....it is an AMD system related problem. Which means it is up to EA/Dice to fix it.

[MoonUtonight]

Dude, it happens as soon as a player (on AMD system) tries to use the scope. Come on...TEST is on an AMD based system and see for yourself instead of obfuscating and delaying.

[AngryDwarf-x]

@EA_Atic 

This looks like a Direct X 12 issue on AMD Radeon drivers, Everyone ive seen complain has an AMD graphics card. i switched to direct x 11 and able to use the the gun with no issues.

switch back to direct X 12 and it crashes. i can understand the frustration several people are expressing at the seeming lack of testing, as this is a very easy to replicate issue and could have been found before the update released.