<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - read pixels of MSAAx8 surface stretched horizontally/vertically" href="https://bugs.freedesktop.org/show_bug.cgi?id=97568#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - read pixels of MSAAx8 surface stretched horizontally/vertically" href="https://bugs.freedesktop.org/show_bug.cgi?id=97568">bug 97568</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>As I mentioned on IRC, I strongly believe this is due to the following issue: <a href="https://trello.com/c/jzBpfrzL/134-resolve-on-transfer-map-upscale-on-transfer-unmap">https://trello.com/c/jzBpfrzL/134-resolve-on-transfer-map-upscale-on-transfer-unmap</a> Basically we're supposed to do a resolve on transfer_map, return the resolved image, and if any of it is changed, copy back at unmap time while up-scaling. We do none of that right now, and 8x MSAA is laid out in a 4x2 grid for each pixel, so it makes sense that the output would be "scaled up" that way.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>