From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72685] [radeonsi hyperz] Artifacts in Unigine Sanctuary
Date: Mon, 11 Aug 2014 08:56:39 +0000 [thread overview]
Message-ID: <bug-72685-502-1ldIERYzdG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72685-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72685
--- Comment #23 from smoki <smoki00790@gmail.com> ---
(In reply to comment #22)
> And he said chips handle these cases, no driver need to somhow check for
> those. I gueesed that maybe that "Stencil op fail or zfail is not KEEP" is
> culprit but who knows :)
>
> http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2012/10/Depth_in-
> depth.pdf#6
> http://amd-dev.wpengine.netdna-cdn.com/wordpress/media/2012/10/Depth_in-
> depth.pdf#10
I mean that one for an artifacts we have in some apps :)
"Unfortunately the conventional method can get artifacts if the shadow volume
intersects the near clipping plane (if front plane capping is not used, that
is), which has made the Z-fail method the algorithm of choice for most deve
lopers."
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1923 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-08-11 8:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 17:24 [Bug 72685] New: [radeonsi] artifacts and/or GPU crashes with htile bugzilla-daemon
2013-12-13 18:40 ` [Bug 72685] " bugzilla-daemon
2013-12-13 22:07 ` bugzilla-daemon
2013-12-13 22:10 ` bugzilla-daemon
2013-12-17 22:14 ` bugzilla-daemon
2013-12-18 2:31 ` [Bug 72685] [radeonsi hyperz] Artifacts in Unigine Sanctuary bugzilla-daemon
2013-12-18 22:58 ` bugzilla-daemon
2013-12-18 22:59 ` bugzilla-daemon
2013-12-18 23:00 ` bugzilla-daemon
2013-12-18 23:22 ` bugzilla-daemon
2013-12-18 23:27 ` bugzilla-daemon
2013-12-19 1:17 ` bugzilla-daemon
2014-01-22 12:02 ` bugzilla-daemon
2014-01-22 12:04 ` bugzilla-daemon
2014-01-22 13:15 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-05-17 14:06 ` bugzilla-daemon
2014-05-17 14:07 ` bugzilla-daemon
2014-05-19 3:54 ` bugzilla-daemon
2014-05-20 19:36 ` bugzilla-daemon
2014-05-22 21:19 ` bugzilla-daemon
2014-05-26 17:32 ` bugzilla-daemon
2014-08-11 6:30 ` bugzilla-daemon
2014-08-11 8:21 ` bugzilla-daemon
2014-08-11 8:33 ` bugzilla-daemon
2014-08-11 8:56 ` bugzilla-daemon [this message]
2014-08-16 16:58 ` bugzilla-daemon
2014-08-17 11:40 ` bugzilla-daemon
2014-08-17 14:00 ` bugzilla-daemon
2014-08-17 14:04 ` bugzilla-daemon
2014-08-17 14:45 ` bugzilla-daemon
2014-08-18 1:23 ` bugzilla-daemon
2014-08-24 13:44 ` bugzilla-daemon
2014-08-25 8:51 ` bugzilla-daemon
2014-09-01 19:32 ` 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-72685-502-1ldIERYzdG@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.