From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 44757] New: one wrong triangle on the balls in foobillard
Date: Fri, 13 Jan 2012 16:42:10 +0000 [thread overview]
Message-ID: <bug-44757-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=44757
Bug #: 44757
Summary: one wrong triangle on the balls in foobillard
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: aaalmosss@gmail.com
The balls are rendered in two passes: the first one with the base image, and
the second one with a spheremap (the "shininess"). The second pass is wrong for
one triangle, it is too bright. It's always the same one, but the balls have
random rotation initially. I checked it with apitrace, and after the first pass
the framebuffer looks good, but not after the second pass (glCallList(21) draws
the ball).
It is not the same as bug 3267, because the spheremap is applied, but
incorrectly. There is a distance-based LOD of the balls, and not all detail
levels have this problem, just detail=4 and detail=7. You can set this
somewhere around the line "if( detail<0 ) detail=0;" ball.c.
The problem is reproducible on r300g, r600g, llvmpipe, but not on nvidia blob.
I couldn't find any obvious error in the application's code, but I'm not very
experienced in OpenGL.
--
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-01-13 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 16:42 bugzilla-daemon [this message]
2012-01-13 16:44 ` [Bug 44757] one wrong triangle on the balls in foobillard 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-44757-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.