From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102955] HyperZ related rendering issue in ARK: Survival Evolved
Date: Sat, 23 Sep 2017 23:25:05 +0000 [thread overview]
Message-ID: <bug-102955-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2432 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102955
Bug ID: 102955
Summary: HyperZ related rendering issue in ARK: Survival
Evolved
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: e.singularitycat@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 134449
--> https://bugs.freedesktop.org/attachment.cgi?id=134449&action=edit
The back buffer of apitrace frame 1017, showing red lines along what looks like
primitive edges.
Hi,
I've been poking "ARK: Survival Evolved", trying to get it playable.
The game is notoriously buggy, particularly under Linux, however the biggest
issue I've had seems to be a Mesa/Radeon bug.
Blocky "pixelated" lines are drawn across what look like edges (see attached).
These lines are most frequently red, black or cyan in colour, and seem to
disappear when the scene complexity is lower (like when looking at the floor or
an area with no foliage or rocks).
Setting R600_DEBUG=nohyperz resolves the issue.
I've tested an apitrace of the game on both Mesa git, and 17.2.1 on a desktop
with a POLARIS10 (RX580 8GiB), running the latest amd-staging-drm-next kernel,
and on a laptop with both Intel integrated graphics and a HAINAN (Sun XT?
8670M), running a stock Archlinux kernel.
Both AMD cards have this rendering issue with HyperZ enabled. The Intel card
renders without this particular problem (if slowly), and llvmpipe (eventually)
renders without issue too.
Apitrace (~600MiB!):
https://drive.google.com/open?id=0B6RX1ZACoaJ5UmhDWDM3ZC03eUk
Desktop:
Linux 4.13.0-rc5-43dd6fde5df4 #3 SMP PREEMPT Thu Sep 21 19:15:33 BST 2017
x86_64 GNU/Linux
Mesa 17.3.0-devel (git hash #52ed3bca91ff13217378196d6800ca7113641a63)
libdrm 2.4.83, LLVM 5.0.0
Laptop:
Linux 4.12.13-1-ARCH #1 SMP PREEMPT Fri Sep 15 06:36:43 UTC 2017 x86_64
GNU/Linux
Mesa 1.7.12,
libdrm 2.4.83, LLVM 5.0.0
The corruption does look somewhat like that of this bug, but applied to terrain
as well. https://bugs.freedesktop.org/show_bug.cgi?id=74784
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4360 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:[~2017-09-23 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 23:25 bugzilla-daemon [this message]
2017-09-23 23:32 ` [Bug 102955] HyperZ related rendering issue in ARK: Survival Evolved bugzilla-daemon
2017-10-01 7:13 ` bugzilla-daemon
2017-10-02 16:01 ` bugzilla-daemon
2017-10-03 21:31 ` bugzilla-daemon
2017-10-06 8:19 ` bugzilla-daemon
2017-10-10 21:51 ` bugzilla-daemon
2017-10-27 8:50 ` bugzilla-daemon
2019-07-21 18:17 ` bugzilla-daemon
2019-09-25 18:00 ` 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-102955-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.