dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104602] [apitrace] Graphical artifacts in Civilization VI on RX Vega
Date: Tue, 12 Mar 2019 10:44:49 +0000	[thread overview]
Message-ID: <bug-104602-502-lvShLXXwlh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104602-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]

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

oliver.triebel@haspa.de changed:

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

--- Comment #19 from oliver.triebel@haspa.de ---
I also confirm success on Ryzen 2200g system.

Steam launch property `R600_DEBUG=nir %command%`
fixed texture flickering/artifacts in CIV6 (that appeared on strategic map).


olly@ryzen-pc1:~$ uname -a
Linux ryzen-pc1 5.0.0-050000-generic #201903032031 SMP Mon Mar 4 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
olly@ryzen-pc1:~$ glxinfo | grep "OpenGL version"
OpenGL version string: 4.5 (Compatibility Profile) Mesa 18.3.3
olly@ryzen-pc1:~$ lspci -nnk | grep -i VGA -A2 
38:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
[1002:15dd] (rev c8)
    Subsystem: Micro-Star International Co., Ltd. [MSI] Vega [Radeon Vega 8
Mobile] [1462:7a39]
    Kernel driver in use: amdgpu
olly@ryzen-pc1:~$ lsb_release -a
No LSB modules are available.
Description:    Ubuntu 18.04.2 LTS

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2908 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

  parent reply	other threads:[~2019-03-12 10:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 15:58 [Bug 104602] Graphical artifacts in Civilization VI on RX Vega bugzilla-daemon
2018-01-20 13:04 ` bugzilla-daemon
2018-01-20 13:10 ` bugzilla-daemon
2018-01-22  6:33 ` bugzilla-daemon
2018-01-24  2:37 ` [Bug 104602] [apitrace] " bugzilla-daemon
2018-03-18 22:44 ` bugzilla-daemon
2018-03-18 22:47 ` bugzilla-daemon
2018-04-09 12:15 ` bugzilla-daemon
2018-04-09 13:26 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2018-09-16 16:11 ` bugzilla-daemon
2018-09-21  3:28 ` bugzilla-daemon
2018-09-21 10:36 ` bugzilla-daemon
2018-09-21 12:25 ` bugzilla-daemon
2018-09-22  1:18 ` bugzilla-daemon
2018-10-05 10:50 ` bugzilla-daemon
2018-10-05 10:57 ` bugzilla-daemon
2018-11-01  0:30 ` bugzilla-daemon
2018-11-01  0:37 ` bugzilla-daemon
2018-11-01  6:39 ` bugzilla-daemon
2018-12-01 11:26 ` bugzilla-daemon
2019-03-12 10:44 ` bugzilla-daemon [this message]
2019-08-01 14:09 ` bugzilla-daemon
2019-08-01 14:13 ` bugzilla-daemon
2019-08-16 18:17 ` bugzilla-daemon
2019-08-19 19:28 ` bugzilla-daemon
2019-08-19 23:06 ` bugzilla-daemon
2019-08-20  4:13 ` bugzilla-daemon
2019-08-23  3:50 ` 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-104602-502-lvShLXXwlh@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;
as well as URLs for NNTP newsgroup(s).