[Mesa-dev] [Bug 96943] [gallium] glCopyPixels is affected by enabled texture state

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 15 18:20:32 UTC 2016


--- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Roland Scheidegger from comment #1)
> The piglit test is probably wrong (I didn't really look), at least different
> results based on enabled texturing don't surprise me. This is one of the
> more weird "features" of glCopyPixels(), glDrawPixels() and friends.
> From the respective man pages:
> "Texture mapping, fog, and all the fragment operations are applied before
> the fragments are written to the frame buffer." So if you don't disable
> texturing, you'll get texturing on top of your copied pixels (which just
> represent the primary color), in whatever way the shader specified (albeit
> the texture coords should be constant IIRC).

OK, so in that case, any time that a texture unit is enabled, we should be
falling back to the drawpixels-style shader? (The multiply, btw, is coming from
the texture combine logic, which defaults to "combine" aka "multiply".)

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160715/0a5292c1/attachment.html>

More information about the mesa-dev mailing list