From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108641] Interlaced dark lines in XCOM2 (UE3.5) on Aruba and Turks
Date: Sat, 03 Nov 2018 12:18:44 +0000 [thread overview]
Message-ID: <bug-108641-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1009 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108641
Bug ID: 108641
Summary: Interlaced dark lines in XCOM2 (UE3.5) on Aruba and
Turks
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: steelwinged@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 142355
--> https://bugs.freedesktop.org/attachment.cgi?id=142355&action=edit
in-game screenshot
Game engine rendering outputs are interlaced with dark lines on r600.
Tested on: 7660G (Aruba) and 7670M (Turks) with Mesa 18.2.4.
Renderdoc captures have been uploaded here:
https://www32.zippyshare.com/v/G74cEAp5/file.html
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2562 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-11-03 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 12:18 bugzilla-daemon [this message]
2018-11-04 11:19 ` [Bug 108641] Interlaced dark lines in XCOM2 (UE3.5) on Aruba and Turks bugzilla-daemon
2018-12-16 15:41 ` bugzilla-daemon
2019-08-04 17:06 ` bugzilla-daemon
2019-08-04 17:07 ` bugzilla-daemon
2019-08-05 19:27 ` bugzilla-daemon
2019-08-05 19:27 ` bugzilla-daemon
2019-08-07 5:08 ` [Bug 108641] Shader causes Interlaced dark lines on R600g in XCOM2 bugzilla-daemon
2019-09-18 19:26 ` 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-108641-502@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).