From da192b50b246af80b87050ac75848dfac3c0afb0 Mon Sep 17 00:00:00 2001 From: Bas Nieuwenhuizen Date: Thu, 28 Dec 2017 00:19:28 +0100 Subject: radv: Use correct framebuffer size for partial FS resolves. 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 --- src/amd/vulkan/radv_meta_resolve_fs.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/amd/vulkan/radv_meta_resolve_fs.c') diff --git a/src/amd/vulkan/radv_meta_resolve_fs.c b/src/amd/vulkan/radv_meta_resolve_fs.c index b937c12ec11..f34e387a07d 100644 --- a/src/amd/vulkan/radv_meta_resolve_fs.c +++ b/src/amd/vulkan/radv_meta_resolve_fs.c @@ -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); -- cgit v1.2.3