dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33762] New: Framebuffer Depth textures (Shadow mapping) - FBO-EXT
Date: Mon, 31 Jan 2011 07:37:55 -0800 (PST)	[thread overview]
Message-ID: <bug-33762-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Framebuffer Depth textures (Shadow mapping) - FBO-EXT
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: s3734770@mail.zih.tu-dresden.de


I'm running a depth map demo that uses fbo depth maps as a render target. The
fbo (EXT) is filled with static stuff (like a mask that is moved over the
screen). So the contents i drawed into the buffer (the depth component is bound
to the buffer) are ignored

I don't know if this feature is in progress or if you know what is missing in
the driver.
If you have no clue, I can offer the following things after a request:
 - Pics of the artifacts
 - Videos that show that the depth texture is not updated
 - Explanation how i set up the FBO/Renderbuffer

The thing works with fglrx.

Extensions I used:
Framebuffer_EXT
Renderbuffer_EXT (for depth store)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-01-31 15:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 15:37 bugzilla-daemon [this message]
2011-01-31 15:40 ` [Bug 33762] Framebuffer Depth textures (Shadow mapping) - FBO-EXT bugzilla-daemon
2011-01-31 15:47 ` bugzilla-daemon
2011-01-31 16:38 ` bugzilla-daemon
2011-01-31 16:39 ` bugzilla-daemon
2011-01-31 17:41 ` bugzilla-daemon
2011-01-31 17:42 ` bugzilla-daemon
2011-01-31 20:04 ` bugzilla-daemon
2011-02-01  0:25 ` bugzilla-daemon
2011-02-01  7:45 ` bugzilla-daemon
2011-02-01  8:05 ` bugzilla-daemon
2011-02-01  8:15 ` bugzilla-daemon
2011-02-01  8:16 ` bugzilla-daemon
2011-02-01  8:19 ` bugzilla-daemon
2011-02-01  8:23 ` bugzilla-daemon
2011-02-01  8:26 ` bugzilla-daemon
2011-04-07  8:20 ` 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-33762-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