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

Vedran Miletić vedran@miletic.net changed:

What |Removed |Added ---------------------------------------------------------------------------- Blocks| |77449

Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=77449 [Bug 77449] Tracker bug for all bugs related to Steam titles

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

--- Comment #3 from Bruno Jacquet (Xaapyks) maxijac@free.fr --- Hello,

I have the same problem on my RX 480 and current mesa git. I produced an apitrace but it is ~734MiB and trimming seems to be corrupting it, I might be doing something wrong. How should I share and eventually trim/extract only the relevant part from the trace?

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

--- Comment #5 from Bruno Jacquet (Xaapyks) maxijac@free.fr --- I took another apitrace, which I uploaded here : http://dl.free.fr/u43NDpptG But when I replay my traces (glretrace), I notice : - Graphical corruptions when I open the ingame console or when a map is loaded (which is NOT a problem I seen during normal runtime). The menu is fine. - The scope bug (this report subject) is not visible from the replayed trace on my end...

Maybe it is an apitrace bug from my side? Not sure if I may report this to the apitrace project, this happens in apitrace from git too.

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

--- Comment #7 from Bruno Jacquet (Xaapyks) maxijac@free.fr --- Thank you very much Michel, indeed masking this extension produces a correct trace that can be replayed to reproduce the scope bug.

So here is a new apitrace showing the bug : http://dl.free.fr/oD7tgoSw9

For reference, the outside of the scope is supposed to be slightly blurred. Random screenshot found on google images to show the expected rendering : http://misc.team-aaa.com/perso_skullgun/MaJCSGO/Augscope.jpg

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

Grazvydas Ignotas notasas@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |notasas@gmail.com

--- Comment #9 from Grazvydas Ignotas notasas@gmail.com --- Created attachment 131302 --> https://bugs.freedesktop.org/attachment.cgi?id=131302&action=edit bo clear hack, needs 4.9 kernel at least

This seems to be the same problem as with DOOM Vulkan, some buffer is not cleared when it should be. It still needs to be investigated wether it's game's fault or radeonsi's though...

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

--- Comment #11 from network723@rkmail.ru --- There is no corruption on scope with current mesa git + llvm 6.0 on TAHITI. I don't have RX480 anymore, so I can't test it with POLARIS.

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

--- Comment #13 from Bruno Jacquet (Xaapyks) maxijac@free.fr --- Created attachment 140499 --> https://bugs.freedesktop.org/attachment.cgi?id=140499&action=edit issue on 18.1.3

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

--- Comment #15 from network723@rkmail.ru --- (In reply to Bruno Jacquet (Xaapyks) from comment #14)

Unfortunately this is not resolved on RX480 and mesa 18.1.3. I attached a screenshot of the issue.

I confirm this is happening on mesa-git + RX560. Unfortunately, the hardware is not mine, so I cannot test it with bo clear hack. There is also some texture corruption ob de_nuke, but i'm not sure if it's related to this bug: https://i.imgur.com/tjfI2uY.jpg. If someone can test these with bo clear hack please do it, I can't do it myself as I'm still waiting for the refund money for my dead RX480 :(

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

--- Comment #17 from network723@rkmail.ru --- Still happens with Mesa git master 9fc1ce258cf956d21a9d4940a3c10c5547d93408, Polaris10 only, Oland and Tahiti are not affected.

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

--- Comment #19 from Timothy Arceri t_arceri@yahoo.com.au --- If you run steam from the command line with:

R600_DEBUG=zerovram steam

Does that fix the issue for you?

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

--- Comment #21 from Timothy Arceri t_arceri@yahoo.com.au --- (In reply to network723 from comment #20)

(In reply to Timothy Arceri from comment #19)

...

Does that fix the issue for you?

Yes, it does fix scope rendering for me. Is any negative performance impact to be expected with that flag?

Potentially but it's unlikely to be noticeable.

Also, is it doing effectively same thing as patch from comment #9?

Yes.

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

Bruno Jacquet (Xaapyks) maxijac@free.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |---

--- Comment #23 from Bruno Jacquet (Xaapyks) maxijac@free.fr --- Since my last message I upgraded my GPU, I now have a Vega 64, and in mesa 19.1.3 I still have the issue, the AUG scope is being all garbled with black patches.

mesa 19.1.3 appears to have a cherry-pick of the commit (825ca9e42eacd305a63f63c61fbbe6348b0266aa) and I checked, I do have the conf in my filesystem:

$ grep -A2 "Counter-Strike Global Offensive" /usr/share/drirc.d/00-mesa-defaults.conf <application name="Counter-Strike Global Offensive" executable="csgo_linux64"> <option name="radeonsi_zerovram" value="true" /> </application>

So I'd say the issue is still there.

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

--- Comment #25 from Michel Dänzer michel@daenzer.net --- (In reply to Bruno Jacquet (Xaapyks) from comment #23)

So I'd say the issue is still there.

Maybe you have a ~/.drirc or other drirc file which gets picked up and disables radeonsi_zerovram? (E.g. due to ever starting the old "driconf" application with a driver which supported the option)

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

--- Comment #27 from Timothy Arceri t_arceri@yahoo.com.au --- (In reply to Bruno Jacquet (Xaapyks) from comment #26)

(In reply to Michel Dänzer from comment #25)

...

(In reply to Bruno Jacquet (Xaapyks) from comment #23)

...

So I'd say the issue is still there.

Maybe you have a ~/.drirc or other drirc file which gets picked up and disables radeonsi_zerovram? (E.g. due to ever starting the old "driconf" application with a driver which supported the option)

~/.drirc and /etc/drirc do not exist on my fs. /usr/share/drirc.d only contains 00-mesa-defaults.conf which is not modified from what the mesa build provides and is packaged in Arch.

strace seems to confirm it is not loading any other "drirc" file any and I don't have any "*MESA*" or "*GL*" env var.

I just tested the trace from comment 16 on my Vega 64 and using the environment variable fixed the issue for me. Do you have an old kernel? radeonsi_zeroram=true will do nothing on pre 4.9 kernels.

If you have at least 4.9 can you try closing steam then running it from the command line with:

radeonsi_zeroram=true steam

And then run CS:GO. This should force the setting even if your system is not picking up the right config file.