From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100239] Incorrect rendering in CS:GO
Date: Thu, 08 Aug 2019 20:53:43 +0000 [thread overview]
Message-ID: <bug-100239-502-UjEPrdsrgx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100239-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2609 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-08 20:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 20:35 [Bug 100239] Incorrect rendering in CS:GO bugzilla-daemon
2017-03-16 21:05 ` bugzilla-daemon
2017-03-22 16:54 ` bugzilla-daemon
2017-03-22 18:56 ` bugzilla-daemon
2017-04-27 19:39 ` bugzilla-daemon
2017-04-29 8:52 ` bugzilla-daemon
2017-04-29 12:22 ` bugzilla-daemon
2017-05-01 3:44 ` bugzilla-daemon
2017-05-01 12:16 ` bugzilla-daemon
2017-05-06 14:59 ` bugzilla-daemon
2017-05-10 23:44 ` bugzilla-daemon
2017-05-13 8:32 ` bugzilla-daemon
2017-12-16 16:04 ` bugzilla-daemon
2018-04-02 11:02 ` bugzilla-daemon
2018-07-07 21:11 ` bugzilla-daemon
2018-07-07 21:12 ` bugzilla-daemon
2018-07-08 9:30 ` bugzilla-daemon
2018-07-08 10:27 ` bugzilla-daemon
2018-11-25 9:52 ` bugzilla-daemon
2019-01-10 9:44 ` bugzilla-daemon
2019-05-03 1:20 ` bugzilla-daemon
2019-05-03 6:08 ` bugzilla-daemon
2019-05-06 4:31 ` bugzilla-daemon
2019-05-06 23:43 ` bugzilla-daemon
2019-08-08 20:53 ` bugzilla-daemon [this message]
2019-08-08 20:59 ` bugzilla-daemon
2019-08-09 8:40 ` bugzilla-daemon
2019-09-14 12:45 ` bugzilla-daemon
2019-09-17 2:09 ` bugzilla-daemon
2019-09-25 17:58 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100239-502-UjEPrdsrgx@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox