From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100593] corruption in total war warhammer when using mesa 17.1 - git
Date: Thu, 06 Apr 2017 06:38:32 +0000 [thread overview]
Message-ID: <bug-100593-502-Lvbjz2lyPG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100593-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100593
--- Comment #1 from tarpoon@gmx.de ---
Some additional information:
Quickest way to see the problem: Go to Options / Graphics / Advanced /
Benchmark and start the benchmark
The Oibaf PPA also has a problem lately but a different looking one (I'll add
another screenshot). A few weeks ago the driver from Oibaf was working just
fine in the game.
The performance seems to be unaffected by the problems.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1323 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 prev parent reply other threads:[~2017-04-06 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 20:45 [Bug 100593] corruption in total war warhammer when using mesa 17.1 - git bugzilla-daemon
2017-04-06 6:38 ` bugzilla-daemon [this message]
2017-04-06 6:40 ` bugzilla-daemon
2017-04-08 9:19 ` bugzilla-daemon
2017-04-08 22:30 ` bugzilla-daemon
2017-04-10 7:19 ` bugzilla-daemon
2017-04-10 9:28 ` bugzilla-daemon
2017-04-14 11:01 ` bugzilla-daemon
2017-04-17 11:23 ` bugzilla-daemon
2017-04-22 12:02 ` bugzilla-daemon
2017-05-26 16:37 ` bugzilla-daemon
2017-05-26 17:29 ` 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-100593-502-Lvbjz2lyPG@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