From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66067] Trine 2's fragment normal buffer is mixtextured on Radeon HD 6770 (Juniper)
Date: Fri, 04 Jul 2014 06:25:25 +0000 [thread overview]
Message-ID: <bug-66067-502-BmKN5Ggnti@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66067-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 687 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66067
--- Comment #17 from smoki <smoki00790@gmail.com> ---
Yes just checked out your trace and got the same screenshot... yes sorry you
are right, but seems to me radeonsi was having a more black even than this
seems like onother bug which got fixed on top of this bug (Sylvain from comment
14 may confirm that with radeonsi). It was like this
https://bugs.freedesktop.org/attachment.cgi?id=99363 and now is much better,
but not complitely correct yet.
Sorry it is just that radeonsi is now in the same state as r600 to actually
have this bug you describe :).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1614 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-07-04 6:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 5:46 [Bug 66067] New: Trine 2 color problems on Radeon HD 6770 (Juniper) bugzilla-daemon
2013-06-23 5:46 ` [Bug 66067] " bugzilla-daemon
2013-06-23 5:47 ` bugzilla-daemon
2013-06-23 16:45 ` bugzilla-daemon
2013-06-23 18:20 ` bugzilla-daemon
2013-07-05 5:30 ` bugzilla-daemon
2013-07-05 5:30 ` bugzilla-daemon
2013-07-05 5:31 ` bugzilla-daemon
2013-07-06 5:59 ` bugzilla-daemon
2013-07-29 18:48 ` [Bug 66067] Trine 2's fragment normal buffer is mixtextured " bugzilla-daemon
2013-09-17 23:25 ` bugzilla-daemon
2013-09-17 23:26 ` bugzilla-daemon
2013-09-18 0:52 ` bugzilla-daemon
2013-09-18 1:37 ` bugzilla-daemon
2013-09-18 1:55 ` bugzilla-daemon
2013-09-18 4:16 ` bugzilla-daemon
2013-09-21 1:09 ` bugzilla-daemon
2014-02-08 20:57 ` bugzilla-daemon
2014-04-15 5:47 ` bugzilla-daemon
2014-05-05 15:27 ` bugzilla-daemon
2014-07-04 3:13 ` bugzilla-daemon
2014-07-04 4:18 ` bugzilla-daemon
2014-07-04 6:25 ` bugzilla-daemon [this message]
2014-07-04 11:27 ` bugzilla-daemon
2014-07-04 11:52 ` bugzilla-daemon
2014-07-04 12:45 ` bugzilla-daemon
2014-07-09 8:53 ` bugzilla-daemon
2014-07-09 8:54 ` bugzilla-daemon
2014-07-09 10:54 ` bugzilla-daemon
2014-07-09 12:16 ` bugzilla-daemon
2014-07-09 13:39 ` bugzilla-daemon
2014-07-09 23:09 ` bugzilla-daemon
2014-07-10 0:03 ` bugzilla-daemon
2014-12-13 5:26 ` bugzilla-daemon
2014-12-13 5:38 ` bugzilla-daemon
2014-12-13 9:21 ` bugzilla-daemon
2015-09-13 20:02 ` bugzilla-daemon
2015-09-13 22:47 ` bugzilla-daemon
2015-09-30 13:04 ` bugzilla-daemon
2016-02-13 1:02 ` bugzilla-daemon
2016-02-13 3:57 ` bugzilla-daemon
2016-02-13 4:02 ` bugzilla-daemon
2016-02-13 4:29 ` bugzilla-daemon
2016-02-13 18:01 ` bugzilla-daemon
2019-09-18 19:04 ` 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-66067-502-BmKN5Ggnti@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).