AMD OpenGL Weirdness

[escape209]

With any of the VS 2015 builds, I experience multiple issues, one of which is this really strange "drunk vision" effect, which sort of looks like a really bad motion blur effect. This doesn't happen with the VS 2013 builds

I wasn't using shade boost here. This is with stock settings.

Notice how a lot of the normally opaque textures, such as the EA Trax display, have become translucent. The drunk vision effect is also very noticeable in the sign in the top-left.

In addition to this, software mode usually just doesn't display anything at all. All these issues happen with both the AppVeyor VS 2015 builds and my own VS 2015 build, and none of them happen in either DX9 or DX11.

[gregory38]

Could you find the first build that have this behavior. It feels like a variable badly initialized due to the recent deferred init.

[FlatOutPS2]

So, which AMD GPU are you using and is your driver version completely up to date?

[escape209]

@FlatOutPS2 I'm using a Radeon HD 7770. I can't download the latest drivers at the moment because my internet connection is being throttled to death. I should be able to test it again later today.

[escape209]

It now seems like the AppVeyor builds are no longer affected, but my own VS 2015 builds, even with the very latest master, seem to still be affected.

[bositman]

Try doing a clean and then a rebuild on the GSdx solution

[escape209]

@bositman Alright, so now the AppVeyor builds seem to be affected by the issue again! It doesn't seem to happen on the first run of an AppVeyor build, but it does on every run thereafter.

EDIT: I'll also mention that, for some reason, when PCSX2 isn't the active window, the blur effect goes away. I have no idea why that happens.

[escape209]

EDIT 2: This also seems to be happening with the VS 2013 AppVeyor builds. Again, no idea why.

[ssakash]

Could you try and find the build which introduced the issue ? git bisect might help.

[escape209]

1.4.0 stable still has the issue. 1.2.1 stable makes the display driver crash and my screen fill with garbage as soon as the game gets to the first loading screen.

[mirh]

Could it be a problem with shader cache?

[gregory38]

It is easy, the bug is either from AMD's driver or from the bad AMD's driver ;)

So wipe-out your driver and reinstall it

[escape209]

@gregory38 I uninstalled and reinstalled my drivers, but nothing's changed :(

[mirh]

With DDU?

[gregory38]

Did you try an older version of the driver? Be sure you have no running application in background

[escape209]

@gregory38 I reverted to Catalyst 15.3, but still no change.

[mirh]

Better if you switch to 16.8.2

[escape209]

@mirh It's still broken on 16.8.2.

[mirh]

1.2.1 stable makes the display driver crash

Uhhh, then I guess congratulation for having won the "Find pcsx2 TDR award".
Seriously, I don't really think it's related to your issue (which btw, I couldn't reproduce on my Burnout 3 copy) but you may want to bisect in which build driver crashes stop to manifest, then help ppsspp guys in helping AMD helping users.

[mirh]

@DPersonalized Can you take a gsdump?

[gregory38]

Based on AMD record, I will mark this bug as external. Otherwise it is potentially a gsdx.ini issue.

[mirh]

Speaking of which.. I have a very strange OGL-only issue in #1842. That triggers god only knows when, and seems to be carried by save-states then (that doesn't seem very far from the "uncertainty" we have here)
I could send you gs dumps when you have time.

[mirh]

Any update on this? Does #2125 change anything in this regard?

[escape209]

This was an issue with AMD drivers, I believe, and it was certainly fixed at some point this year or even late last year.

[mirh]

So.. Runs >1 works good in your system then?
I'm not quite sure why only you was getting the problem, but if you can't reproduce it anymore, you can close.