From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71326] [r600g] Texture artifacts when viewed from a distance in WoW
Date: Sun, 09 Mar 2014 22:00:49 +0000 [thread overview]
Message-ID: <bug-71326-502-LQBj39mCpm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71326-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 869 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71326
--- Comment #44 from Chris Rankin <rankincj@googlemail.com> ---
Created attachment 95474
--> https://bugs.freedesktop.org/attachment.cgi?id=95474&action=edit
Fragment of apitrace from 32 bit WoW on HD6450 (40/40)
This trace can be reconstructed via the following command:
$ cat wine.trace.xz.* > wine.trace.xz
Its SHA1SUM should be: efd80aefa86a65d4e8d1c43cfdd231361414b4bd
This texture corruption is now visible on a HD6450 as well as my HD4670 AGP.
The corruption is also visible when I replay this trace on my HD4890, although
my HD4890 itself renders WoW correctly.
Interestingly, my HD4890 replays this trace far more quickly than the HD6450
does. And the HD6450 occasionally renders what appears to be a completely blank
frame.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1871 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:[~2014-03-09 22:00 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 23:39 [Bug 71326] New: [r600g] Texture artifacts when viewed from a distance in WoW bugzilla-daemon
2013-11-06 23:40 ` [Bug 71326] " bugzilla-daemon
2013-11-06 23:41 ` bugzilla-daemon
2013-11-07 16:57 ` bugzilla-daemon
2013-11-07 20:46 ` bugzilla-daemon
2014-03-09 20:46 ` bugzilla-daemon
2014-03-09 20:47 ` bugzilla-daemon
2014-03-09 20:49 ` bugzilla-daemon
2014-03-09 20:52 ` bugzilla-daemon
2014-03-09 20:54 ` bugzilla-daemon
2014-03-09 20:56 ` bugzilla-daemon
2014-03-09 20:58 ` bugzilla-daemon
2014-03-09 21:00 ` bugzilla-daemon
2014-03-09 21:02 ` bugzilla-daemon
2014-03-09 21:03 ` bugzilla-daemon
2014-03-09 21:05 ` bugzilla-daemon
2014-03-09 21:07 ` bugzilla-daemon
2014-03-09 21:08 ` bugzilla-daemon
2014-03-09 21:10 ` bugzilla-daemon
2014-03-09 21:11 ` bugzilla-daemon
2014-03-09 21:13 ` bugzilla-daemon
2014-03-09 21:15 ` bugzilla-daemon
2014-03-09 21:16 ` bugzilla-daemon
2014-03-09 21:18 ` bugzilla-daemon
2014-03-09 21:20 ` bugzilla-daemon
2014-03-09 21:22 ` bugzilla-daemon
2014-03-09 21:23 ` bugzilla-daemon
2014-03-09 21:25 ` bugzilla-daemon
2014-03-09 21:29 ` bugzilla-daemon
2014-03-09 21:31 ` bugzilla-daemon
2014-03-09 21:33 ` bugzilla-daemon
2014-03-09 21:34 ` bugzilla-daemon
2014-03-09 21:35 ` bugzilla-daemon
2014-03-09 21:37 ` bugzilla-daemon
2014-03-09 21:38 ` bugzilla-daemon
2014-03-09 21:40 ` bugzilla-daemon
2014-03-09 21:41 ` bugzilla-daemon
2014-03-09 21:43 ` bugzilla-daemon
2014-03-09 21:44 ` bugzilla-daemon
2014-03-09 21:46 ` bugzilla-daemon
2014-03-09 21:47 ` bugzilla-daemon
2014-03-09 21:49 ` bugzilla-daemon
2014-03-09 21:50 ` bugzilla-daemon
2014-03-09 21:51 ` bugzilla-daemon
2014-03-09 22:00 ` bugzilla-daemon [this message]
2014-03-09 22:01 ` bugzilla-daemon
2014-03-09 22:01 ` bugzilla-daemon
2014-03-09 22:02 ` bugzilla-daemon
2014-03-09 22:02 ` bugzilla-daemon
2014-03-09 22:02 ` bugzilla-daemon
2014-03-09 22:02 ` bugzilla-daemon
2014-03-09 22:03 ` bugzilla-daemon
2014-03-09 22:03 ` bugzilla-daemon
2014-03-09 22:03 ` bugzilla-daemon
2014-03-09 22:04 ` bugzilla-daemon
2014-03-09 22:04 ` bugzilla-daemon
2014-03-09 22:11 ` bugzilla-daemon
2014-03-09 23:57 ` bugzilla-daemon
2019-09-18 19:11 ` 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-71326-502-LQBj39mCpm@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