| commit | 3aa566610c7b6b3ef7d4d2668534d340437ad886 | |
| author | Henri Verbeet <hverbeet@codeweavers.com> | |
| Fri, 9 Apr 2021 10:31:12 +0000 (9 12:31 +0200) | ||
| committer | Alexandre Julliard <julliard@winehq.org> | |
| Fri, 9 Apr 2021 18:37:14 +0000 (9 20:37 +0200) | ||
| tree | d90133b9df03846c4071d320d67a588a16ec23d6 | treesnapshot (tar.gz zip) |
| parent | e4721f0c1e85aacc1770080cfec77d85f75587f2 | commitdiff |
wined3d: Use the client area dimensions instead of the backbuffer dimensions for the Vulkan swapchain.
Often these are the same, and even when not, the minimum/maximum image extents
will often end up forcing the swapchain dimensions to be the same as the
client area. However, some implementations will allow the swapchain to be
created with dimensions different from the client area, but then return
VK_SUBOPTIMAL_KHR from vkQueuePresentKHR().
Signed-off-by: Henri Verbeet <hverbeet@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
Often these are the same, and even when not, the minimum/maximum image extents
will often end up forcing the swapchain dimensions to be the same as the
client area. However, some implementations will allow the swapchain to be
created with dimensions different from the client area, but then return
VK_SUBOPTIMAL_KHR from vkQueuePresentKHR().
Signed-off-by: Henri Verbeet <hverbeet@codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard@winehq.org>
| dlls/wined3d/swapchain.c | diffblobblamehistory |