radv: Use correct framebuffer size for partial FS resolves.
authorBas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Wed, 27 Dec 2017 23:19:28 +0000 (00:19 +0100)
committerBas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Wed, 27 Dec 2017 23:30:47 +0000 (00:30 +0100)
Framebuffer is from 0,0, not (dst.x, dst.y).

Fixes: 69136f4e633 "radv/meta: add resolve pass using fragment/vertex shaders"
Reviewed-by: Dave Airlie <airlied@redhat.com>
src/amd/vulkan/radv_meta_resolve_fs.c

index b937c12ec11bb20df55a6338f277e40fa5015bc7..f34e387a07d70f397a9e91b4dab65d2609f6ff1a 100644 (file)
@@ -540,8 +540,8 @@ void radv_meta_resolve_fragment_image(struct radv_cmd_buffer *cmd_buffer,
                                               .pAttachments = (VkImageView[]) {
                                               radv_image_view_to_handle(&dest_iview),
                                       },
-                                      .width = extent.width,
-                                      .height = extent.height,
+                                      .width = extent.width + dstOffset.x,
+                                      .height = extent.height + dstOffset.y,
                                       .layers = 1
                                }, &cmd_buffer->pool->alloc, &fb);