From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109179] Surviving Mars - Graphical artifacts on game map
Date: Sun, 30 Dec 2018 05:24:40 +0000 [thread overview]
Message-ID: <bug-109179-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109179
Bug ID: 109179
Summary: Surviving Mars - Graphical artifacts on game map
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: stalkerg@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
The system is Gentoo, this problem tested on the latest stable version of
mesa/llvm/kernel and latest git versions.
It's a very popular report for game developers
https://forum.paradoxplaza.com/forum/index.php?threads/surviving-mars-graphical-artifacts-on-game-map-linux.1121318/
Affectect all amdgpu cards, my own is vega56.
With R600_DEBUG=nir this bug is gone but I my system start unstable and time to
time GPU hangs occurred.
I suppose it's same problem as with Civ VI
https://bugs.freedesktop.org/show_bug.cgi?id=104602
I will try Arceri patch to check it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2884 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-12-30 5:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 5:24 bugzilla-daemon [this message]
2019-07-18 3:50 ` [Bug 109179] Surviving Mars - Graphical artifacts on game map 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-109179-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.