RadeonSI Adds Workaround To Deal With Incorrect Rendering In Counter-Strike: GO

[czz0]

I have hundreds of hours on CSGO with an RX580 using mesa and never experienced this.

[skeevy420]

Michael

setting the AMD_DEBUG=zerovram environment variable.

Unless they're running it from git, it's still R600_DEBUG with Mesa 19.0 and under.

[schmidtbag]

If it is a driver specific issue why they are adding a game specific workaround in the driver?

The workaround is game specific but the actual fix isn't (at least not to my understanding). The article mentions other games that can be affected by it and I'm sure there are more. The thing is, most games were coded in a manner where this problem wasn't exploited/noticeable. It's generally a non-issue, but just because it's rare, that doesn't necessarily mean the game itself is at fault.

[agd5f]

Because it's a driver-specific issue, not a game-specific issue. It's really just coincidence that CS:GO happens to make it noticeable.

OpenGL makes no guarantees about the value of uninitialized buffers. If an app relies on some specific value, it's relying on implementation specific behavior.

[zoomblab]

Because it's a driver-specific issue, not a game-specific issue. It's really just coincidence that CS:GO happens to make it noticeable.

If it is a driver specific issue why they are adding a game specific workaround in the driver?

[skeevy420]

That's weird, I'm using R7 250, Fedora, Gnome and haven't noticed any serious issues with GLAMOR.
This might be a hardware issue imo.

Oh no, I was agreeing with boxie about it being rock solid.

[zxy_thf]

Ditto with my 580, Manjaro, and KDE.

That's weird, I'm using R7 250, Fedora, Gnome and haven't noticed any serious issues with GLAMOR.
This might be a hardware issue imo.

[schmidtbag]

Why doesn't Valve fix the game?

Because it's a driver-specific issue, not a game-specific issue. It's really just coincidence that CS:GO happens to make it noticeable.

[jf33]

Why doesn't Valve fix the game?

[aufkrawall]

Considering how this seems to be a default behavior of the hardware, I'm actually a bit surprised the problem doesn't come up more often.

Makes me wonder:
I don't really know the best way to describe this, but y'know how sometimes for the first 1-2 seconds of launching a game (with Mesa drivers) you get a full screen of artifacting? Sometimes I can see glimpses of images or textures that were obviously loaded from another program/game, which leads me to believe this because the VRAM isn't zero'd-out and the GPU, for whatever reason, is just drawing whatever is in its buffer as it waits for the game to render the first frame.
It's not really a problem to me. It's a little ugly but I'm just curious if this is directly related.

This probably is the application's fault, like in this case:

https://bugs.freedesktop.org/show_bug.cgi?id=110448