dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57842] New: r200: Culling is broken when rendering to an FBO
Date: Mon, 03 Dec 2012 15:12:57 +0000	[thread overview]
Message-ID: <bug-57842-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1781 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=57842

          Priority: medium
            Bug ID: 57842
          Assignee: dri-devel@lists.freedesktop.org
           Summary: r200: Culling is broken when rendering to an FBO
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: stefandoesinger@gmx.at
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/r200
           Product: Mesa

Created attachment 70972
  --> https://bugs.freedesktop.org/attachment.cgi?id=70972&action=edit
Test case

When rendering to an FBO with culling enabled, the r200 driver discards all
geometry. As soon as GL_CULL_FACE is enabled, nothing is drawn. The glCullFace,
glFrontFace and primitive orientation don't seem to make a difference. When
rendering to a glx front or back buffer, culling behaves correctly.

The attached test case shows the issue. It creates an FBO, clears it with a
blue color, and then draws a front- and back facing triangle in red and green
respectively, and culls front-facing primitives. Afterwards the FBO texture is
drawn to the window. The expected result is that the green triangle shows up.
The actual result is a solid blue window.

I've had a quick look at the driver source code. r200FrontFace swaps front- and
back facing geometry because the driver renders everything upside down on FBOs.
This code doesn't seem to have any effect on this bug. What seems to trigger it
is not inverting the viewport in r200UpdateWindow(), but I don't understand
why.

The test case can be compiled with gcc fbo.c -o fbo -lGL -lglut , and started
by simply running the binary without any parameters.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3194 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

             reply	other threads:[~2012-12-03 15:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 15:12 bugzilla-daemon [this message]
2012-12-04 20:20 ` [Bug 57842] r200: Culling is broken when rendering to an FBO bugzilla-daemon
2012-12-04 20:57 ` bugzilla-daemon
2012-12-05  8:50 ` bugzilla-daemon
2012-12-05  8:51 ` bugzilla-daemon
2012-12-23 23:41 ` bugzilla-daemon
2012-12-24  0:19 ` bugzilla-daemon
2012-12-24  1:04 ` bugzilla-daemon
2012-12-24  1:16 ` bugzilla-daemon
2012-12-24  1:36 ` bugzilla-daemon
2012-12-24  2:18 ` bugzilla-daemon
2012-12-24  2:22 ` bugzilla-daemon
2012-12-24  3:02 ` bugzilla-daemon
2012-12-24  3:38 ` bugzilla-daemon
2012-12-30 22:32 ` bugzilla-daemon
2013-01-02 22:42 ` bugzilla-daemon
2013-01-03  5:14 ` bugzilla-daemon
2013-01-03 14:17 ` bugzilla-daemon
2013-01-03 18:31 ` 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-57842-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;
as well as URLs for NNTP newsgroup(s).