From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43504] New: tex2D() artifacts (tiling related?) on AMD RV670
Date: Sat, 03 Dec 2011 21:12:15 +0000 [thread overview]
Message-ID: <bug-43504-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=43504
Bug #: 43504
Summary: tex2D() artifacts (tiling related?) on AMD RV670
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: kam1kaz3@gmail.com
Created attachment 54101
--> https://bugs.freedesktop.org/attachment.cgi?id=54101
Screenshot showing problem
This is what I'm doing:
1) render scene to render target texture A
2) render quad on screen to show RTT A data
When on the second step, I am using a fragment shader that calls tex2D() to
retrieve the RTT color data, however I get artifacts as shown on the attached
screenshot.
Whenever I restart the application, I get different corruption. I'm not sure
the problem is when reading from the texture, or writing on it.
If I output colors without using tex2D() it all works fine.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-12-04 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 21:12 bugzilla-daemon [this message]
2011-12-04 5:23 ` [Bug 43504] render to texture artifacts (tiling related?) on AMD RV670 bugzilla-daemon
2011-12-04 5:26 ` bugzilla-daemon
2011-12-04 5:33 ` 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-43504-502@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.