From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64471] Radeon HD6570 lockup in Brütal Legend
Date: Sun, 12 May 2013 06:27:30 +0000 [thread overview]
Message-ID: <bug-64471-502-aGCIXa9fho@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64471-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64471
--- Comment #3 from Zoltán Böszörményi <zboszor@pr.hu> ---
Yes, it does. Thanks.
Now it doesn't lock up but the reflection of fire(? it must be fire,
considering the surroundings) on the face of the hero is wrong. It looks
metallic and can be described as bad rendering. (It is a different bug.)
I had these set previously, but I can see they are gone from the r600g sources:
$ set | grep R600
R600_ENABLE_S3TC=1
R600_STREAMOUT=1
R600_TILING=1
Now, which R600_DEBUG options do you suggest running the game with, so I can
provide you with more in-depth information?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1498 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-05-12 6:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 13:02 [Bug 64471] New: Radeon HD6570 lockup in Brütal Legend bugzilla-daemon
2013-05-11 13:02 ` [Bug 64471] " bugzilla-daemon
2013-05-11 19:36 ` bugzilla-daemon
2013-05-12 6:27 ` bugzilla-daemon [this message]
2013-05-12 6:47 ` bugzilla-daemon
2013-05-24 17:08 ` bugzilla-daemon
2013-05-29 3:29 ` [Bug 64471] Radeon HD6570 lockup in Brütal Legend with HyperZ bugzilla-daemon
2013-05-29 3:30 ` bugzilla-daemon
2013-06-10 22:43 ` bugzilla-daemon
2013-08-05 9:01 ` bugzilla-daemon
2013-10-30 14:14 ` bugzilla-daemon
2013-10-31 2:51 ` bugzilla-daemon
2013-10-31 2:53 ` bugzilla-daemon
2013-11-12 11:19 ` bugzilla-daemon
2013-12-25 16:10 ` bugzilla-daemon
2014-01-23 20:39 ` bugzilla-daemon
2014-02-06 16:50 ` bugzilla-daemon
2014-02-07 17:58 ` bugzilla-daemon
2014-02-10 21:19 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-02-17 21:09 ` bugzilla-daemon
2014-02-18 6:42 ` bugzilla-daemon
2014-02-18 6:48 ` bugzilla-daemon
2014-02-18 7:32 ` bugzilla-daemon
2014-02-18 15:36 ` bugzilla-daemon
2014-02-18 16:05 ` bugzilla-daemon
2014-08-24 13:40 ` bugzilla-daemon
2014-08-25 19:07 ` bugzilla-daemon
2014-09-01 19:35 ` bugzilla-daemon
2014-12-29 21:34 ` bugzilla-daemon
2014-12-29 23:00 ` bugzilla-daemon
2014-12-30 10:00 ` bugzilla-daemon
2014-12-31 1:30 ` bugzilla-daemon
2015-02-07 13:43 ` 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-64471-502-aGCIXa9fho@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).