https://bugs.freedesktop.org/show_bug.cgi?id=76919
Priority: medium Bug ID: 76919 Assignee: dri-devel@lists.freedesktop.org Summary: Random junk at the bottom of non-multiple-of-4 compressed textures (original or mipmapped) Severity: normal Classification: Unclassified OS: All Reporter: bugspam@moreofthesa.me.uk Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/r600 Product: Mesa
Created attachment 96745 --> https://bugs.freedesktop.org/attachment.cgi?id=96745&action=edit Example image (with mipmaps), the height of which triggers the problem
There seems to be a problem with some compressed textures. When the height of the image (more specifically, of the mipmap level used) is not a multiple of 4, it appears that the bottom part of the image – as rendered – contains random junk, apparently set at image load time.
The example image will show the problem at its original size. I've also played with its height (initially 570px): increasing it to a multiple of 4 would remove the problem if it's rendered using the full-size version, but since when reduced by one level the height is again not a multiple of 4, the problem re-appears. Setting the full-size height to 576px moves the problem down further.
(We're using http://crunch.googlecode.com/svn/trunk/ for image (de)compression.)
https://bugs.freedesktop.org/show_bug.cgi?id=76919
Darren Salt bugspam@moreofthesa.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 (AMD64) OS|All |Linux (All) Version|unspecified |10.1
https://bugs.freedesktop.org/show_bug.cgi?id=76919
--- Comment #1 from Tapani Pälli lemody@gmail.com --- I don't know details of the problem here but I got interested and went to read the spec ..
EXT_texture_compression_s3tc specification states in "Implementation Note":
"If the width or height is not a multiple of four, there will be 4x4 blocks at the edge of the image that contain "extra" texels that are not part of the image."
I'm not sure though what should happen if one samples/reads such texel.
https://bugs.freedesktop.org/show_bug.cgi?id=76919
Darren Salt bugspam@moreofthesa.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #96745|text/plain |application/octet-stream mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=76919
--- Comment #2 from Darren Salt bugspam@moreofthesa.me.uk --- I'm not sure either, but I'd (naïvely) expect the image height not being a multiple of 4 not to matter.
https://bugs.freedesktop.org/show_bug.cgi?id=76919
--- Comment #3 from Darren Salt bugspam@moreofthesa.me.uk --- Turns out that the bug also affects the right edges of textures.
(Evergreen, in case there's something hardware-specific about this.)
https://bugs.freedesktop.org/show_bug.cgi?id=76919
Tapani Pälli lemody@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lemody@gmail.com
--- Comment #4 from Tapani Pälli lemody@gmail.com --- Are you able to reproduce this bug with simple program using a standard dds file? If this is possible, please attach such example.
https://bugs.freedesktop.org/show_bug.cgi?id=76919
--- Comment #5 from Eero Tamminen eero.t.tamminen@intel.com --- Bug 86747 (on Intel GPU) could also be due to DXT texture mipmap levels not being multiple of 4.
https://bugs.freedesktop.org/show_bug.cgi?id=76919
Tapani Pälli lemody@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO
--- Comment #6 from Tapani Pälli lemody@gmail.com --- please attach a test case
https://bugs.freedesktop.org/show_bug.cgi?id=76919
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |MOVED
--- Comment #7 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/503.
dri-devel@lists.freedesktop.org