<div dir="ltr">On 4 June 2013 18:20, Anuj Phogat <<a href="mailto:anuj.phogat@gmail.com" target="_blank">anuj.phogat@gmail.com</a>> wrote: <div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> This patch enables ext_framebuffer_multisample_blit_scaled extension on intel h/w >= gen6. Note: Patches for piglit tests to verify this functionality are out for review on piglit mailing list. Tests pass for all of the scaling factors from 0.1 to 2.4. Comment from Paul Berry on my previous implementation: "I have some concerns about the image quality of the method you've implemented. As I understand it, the primary use case of this extension is to allow the client to do multisampled rendering at slightly less than screen resolution (e.g. 720p instead of 1080p), and then blit the result to the screen in one step while keeping most of the quality benefits of multisampling. Since your implementation is effectively equivalent to downsampling and then blitting using GL_NEAREST filtering, my fear is that it will lead to blocky artifacts that are severe enough to negate the benefit of multisampling in the first place. Before we turn this extension on in the Intel driver, I'd like to look at a comparison of: (1) your technique (2) downsampling followed by scaling with GL_LINEAR filtering (3) The nVidia implementation, in GL_SCALED_RESOLVE_FASTEST_EXT mode (4) The nVidia implementation, in GL_SCALED_RESOLVE_NICEST_EXT mode (5) Just rendering the image directly to the single-sampled destination buffer" My latest implementation uses bilinear filtering and addresses all of the above concerns. It produces images which are free from blocky artifacts and show big improvement in visual quality. Here is a link to an image comparing the rendering quality on Intel and NVIDIA drivers: <a href="https://www.dropbox.com/s/m90lqqrj2vjps3g/scaled-blit.png" target="_blank">https://www.dropbox.com/s/m90lqqrj2vjps3g/scaled-blit.png</a> Piglit tests to verify the implementation can be found at: <a href="https://github.com/aphogat/piglit.git" target="_blank">https://github.com/aphogat/piglit.git</a> Branch: blit-1 Accuracy tests: ext_framebuffer_multisample-blit-scaled-glsl ext_framebuffer_multisample-negative-blit-scaled Visual quality test: ext_framebuffer_multisample-blit-scaled While generating these images I came across a bug in NVIDIA's proprietary OpenGL 4.3 linux driver. While doing glBlitFramebuffer() driver ignores scissor operation. >From OpenGL 4.3 specification: "When values are written to the draw buffers, blit operations bypass most of the fragment pipeline. The only fragment operations which affect a blit are the pixel ownership test, the scissor test, and sRGB conversion (see section 17.3.9). Color, depth, and stencil masks (see section 17.4.2) are ignored." </blockquote><div> </div><div>Yeah, I've noticed bugs in this area before. IIRC nVidia fails the "clip-and-scissor-blit" piglit tests. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Signed-off-by: Anuj Phogat <<a href="mailto:anuj.phogat@gmail.com">anuj.phogat@gmail.com</a>> --- src/mesa/drivers/dri/intel/intel_extensions.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/mesa/drivers/dri/intel/intel_extensions.c b/src/mesa/drivers/dri/intel/intel_extensions.c index 5cb2fa3..23bc757 100644 --- a/src/mesa/drivers/dri/intel/intel_extensions.c +++ b/src/mesa/drivers/dri/intel/intel_extensions.c @@ -94,6 +94,7 @@ intelInitExtensions(struct gl_context *ctx) if (intel->gen >= 6) { ctx->Extensions.EXT_framebuffer_multisample = true; ctx->Extensions.EXT_transform_feedback = true; + ctx->Extensions.EXT_framebuffer_multisample_blit_scaled = true; ctx->Extensions.ARB_blend_func_extended = !driQueryOptionb(&intel->optionCache, "disable_blend_func_extended"); ctx->Extensions.ARB_draw_buffers_blend = true; ctx->Extensions.ARB_ES3_compatibility = true; -- 1.8.1.4 </blockquote></div> </div></div>