From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69689] FBO with GL_RGBA16F texture format silent drawing corruption
Date: Fri, 15 Nov 2013 01:29:20 +0000 [thread overview]
Message-ID: <bug-69689-502-Ik3IFkNLFo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69689-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69689
--- Comment #10 from Grigori Goronzy <greg@chown.ath.cx> ---
This does not work because glBlitFramebuffer fails, since it is trying to blit
between FBOs with different pixel formats. This isn't allowed, check for
instance the OpenGL 3.3 core specification, section 4.3.2 or the
EXT_framebuffer_multisample specification. They unambiguously state that read
and draw framebuffer must have the same pixel format for blits that involve
multisample framebuffers.
As far as I can see, this is not a problem with Mesa, but rather with your
OpenGL compliance.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1478 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
next prev parent reply other threads:[~2013-11-15 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 2:25 [Bug 69689] New: FBO with GL_RGBA16F texture format silent drawing corruption bugzilla-daemon
2013-09-23 14:01 ` [Bug 69689] " bugzilla-daemon
2013-09-24 6:17 ` bugzilla-daemon
2013-09-24 21:18 ` bugzilla-daemon
2013-10-02 3:48 ` bugzilla-daemon
2013-11-12 14:52 ` bugzilla-daemon
2013-11-12 15:00 ` bugzilla-daemon
2013-11-13 6:11 ` bugzilla-daemon
2013-11-13 6:12 ` bugzilla-daemon
2013-11-13 6:16 ` bugzilla-daemon
2013-11-15 1:29 ` bugzilla-daemon [this message]
2013-11-15 3:29 ` 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-69689-502-Ik3IFkNLFo@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).