From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 53884] New: gl_FragCoord gets corrupted in some camera angles
Date: Tue, 21 Aug 2012 14:42:33 +0000 [thread overview]
Message-ID: <bug-53884-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=53884
Bug #: 53884
Summary: gl_FragCoord gets corrupted in some camera angles
Classification: Unclassified
Product: Mesa
Version: 8.0
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: curaga@operamail.com
Created attachment 65891
--> https://bugs.freedesktop.org/attachment.cgi?id=65891
Screenshot of the issue, bad camera angle
In certain camera angles, gl_FragCoord.xy seem to have bogus/corrupted values.
I tried to make a simple example but couldn't, so uploading an apitrace of the
bigger app and screenshots. The apitrace is 60mb XZ-compressed, that's why the
need to use a third-party service - upload limits here.
This shader:
void main() {
gl_FragColor = vec4(gl_FragCoord.xy / vec2(640, 480), 0.0, 0.0);
}
should always create values from 0 to 1 in a window of that size. In the
apitrace the only difference is that the size is passed in an uniform.
This bug happens on both r600g and llvmpipe. I didn't have the patience to wait
for softpipe to render it. I don't have anything else on this machine to
compare to (swrast, blobs).
Mesa 8.0.3
Linux 3.2.23
--
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:[~2012-08-21 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:42 bugzilla-daemon [this message]
2012-08-21 14:43 ` [Bug 53884] gl_FragCoord gets corrupted in some camera angles bugzilla-daemon
2012-08-21 14:46 ` bugzilla-daemon
2012-08-21 18:59 ` 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-53884-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox