<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wine's d3d8/9 visual tests fail on i965" href="https://bugs.freedesktop.org/show_bug.cgi?id=77312#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wine's d3d8/9 visual tests fail on i965" href="https://bugs.freedesktop.org/show_bug.cgi?id=77312">bug 77312</a> from <a class="email" href="mailto:andrey.simiklit.1989@gmail.com" title="andrii simiklit <andrey.simiklit.1989@gmail.com>"> andrii simiklit</a> <pre>I made a mistake, this isn't a mesa issue. According to ARB_framebuffer_object spec: "- If the attachment sizes are not all identical, rendering will be limited to the largest area that can fit in all of the attachments (i.e. an intersection of rectangles having a lower left of (0,0) and an upper right of (width,height) for each attachment) - If the attachment sizes are not all identical, the values of pixels outside the common intersection area after rendering are undefined." So this is rather a wine issue. ************************ * depth * * * *********** * * color * * * * * * * * ************************ Because it does not expect that depth buffer will be modified outside the scissors area which is equal to intersection area. But Mesa feels free to do everything with pixels(depth) outside the intersection area even to clean them. Gallium behaves here in another way it just leaves a depth buffer outside the intersection untouched.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>