Black Flickering on 2D Engine

Hi. I have the same issue and its making me crazy to find out whats wrong. Sometimes i think my pc is broken or something, cause I cant find a solution for this..

I have this also and its super annoying . my testing has shown it appears to be related to the advertising boards , the matches where they fail to load (they stay black) i have no flickering at all .

 

please add option to to disable the annoying advertising boards .

Hello, this is a known issue we're currently investigating. 

Can you please attach your DxDiag file, you can see how in the link below:

https://support.sega.com/hc/en-gb/articles/9997195057553-How-to-find-my-system-DxDiag-system-information

45 minutes ago, Zachary Whyte said:

Hello, this is a known issue we're currently investigating. 

Can you please attach your DxDiag file, you can see how in the link below:

https://support.sega.com/hc/en-gb/articles/9997195057553-How-to-find-my-system-DxDiag-system-information

I have attached mine.

DxDiag.txt

dxdiag attatched  as requested

DxDiag.txt

Thank you for the DxDiag files.

If any of you are using a dual monitor setup, would you mind temporarily unplugging one of your monitors and seeing if the issue still occurs, thank you.

 

10 minutes ago, Zachary Whyte said:

Thank you for the DxDiag files.

If any of you are using a dual monitor setup, would you mind temporarily unplugging one of your monitors and seeing if the issue still occurs, thank you.

 

I just tried this to no avail. Tried both monitors seperatly with different connectin types. Nothing worked.

Thank you for the update, we'll continue to investigate. 

Here is mine.

DxDiag.txt

Are we any closer to figuring out what might be causing this? I appreciate it's likely a difficult issue to get a hold of but I don't think I can start a new save with 2D being out of action. It does feel more and more like this issue won't be solved in this game cycle which is a shame. I'm only hoping it won't be repeated with future editions. 

Hello @durrrunfortunately we've been unable to reproduce this issue internally.

As this is affecting a small number of Users we believe it's likely an issue caused by specific setups. So this means we're not truly in a position to make changes to address it.

We apologies for this inconvenience.