From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99136] Blood Effects Total War: Warhammer
Date: Sun, 18 Dec 2016 05:19:38 +0000 [thread overview]
Message-ID: <bug-99136-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99136
Bug ID: 99136
Summary: Blood Effects Total War: Warhammer
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: eutychios23@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Enabling blood effects in total war:warhammer(linux native) v1.40,corrupts
graphics for units in battles,temporary workaround is to disable them.My gpu is
r7 240 with Mesa 13.0.2 on gallium 0.4 compiled with llvm 3.9 my distro is
archlinux x86_x64.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2226 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:[~2016-12-18 5:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 5:19 bugzilla-daemon [this message]
2016-12-20 19:50 ` [Bug 99136] Blood Effects Total War: Warhammer bugzilla-daemon
2017-01-20 14:33 ` bugzilla-daemon
2017-01-20 15:21 ` bugzilla-daemon
2017-01-20 15:23 ` bugzilla-daemon
2017-01-20 15:32 ` bugzilla-daemon
2017-01-20 15:39 ` bugzilla-daemon
2017-01-20 16:10 ` bugzilla-daemon
2017-01-20 16:27 ` bugzilla-daemon
2017-01-31 20:39 ` bugzilla-daemon
2017-01-31 20:39 ` bugzilla-daemon
2017-01-31 20:49 ` bugzilla-daemon
2017-02-02 9:35 ` bugzilla-daemon
2017-02-04 5:57 ` bugzilla-daemon
2017-02-04 5:58 ` bugzilla-daemon
2017-02-05 13:07 ` bugzilla-daemon
2017-02-06 6:40 ` bugzilla-daemon
2017-02-06 6:42 ` bugzilla-daemon
2017-02-06 6:46 ` bugzilla-daemon
2017-02-06 6:46 ` bugzilla-daemon
2017-02-06 6:47 ` bugzilla-daemon
2017-02-06 9:31 ` bugzilla-daemon
2017-02-07 10:38 ` bugzilla-daemon
2017-02-07 14:48 ` bugzilla-daemon
2017-02-09 10:40 ` bugzilla-daemon
2017-02-09 13:08 ` bugzilla-daemon
2017-02-09 21:38 ` bugzilla-daemon
2017-02-10 10:43 ` bugzilla-daemon
2017-02-13 10:02 ` bugzilla-daemon
2017-02-16 13:21 ` bugzilla-daemon
2017-02-16 13:42 ` bugzilla-daemon
2017-02-16 13:45 ` bugzilla-daemon
2017-02-17 2:21 ` bugzilla-daemon
2017-02-21 19:50 ` bugzilla-daemon
2017-02-21 19:51 ` bugzilla-daemon
2017-02-23 0:23 ` bugzilla-daemon
2017-02-23 19:17 ` bugzilla-daemon
2017-02-23 22:32 ` bugzilla-daemon
2017-02-24 19:18 ` bugzilla-daemon
2017-02-26 8:33 ` bugzilla-daemon
2017-03-15 13:56 ` bugzilla-daemon
2017-03-20 3:49 ` bugzilla-daemon
2017-03-22 16:56 ` [Bug 99136] Blood Effects corrupt graphics in " bugzilla-daemon
2017-04-05 20:14 ` bugzilla-daemon
2017-05-04 11:41 ` bugzilla-daemon
2017-05-23 16:48 ` bugzilla-daemon
2017-07-25 19:18 ` 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-99136-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).