summaryrefslogtreecommitdiffstats
path: root/src/video_core/renderer_vulkan/vk_blit_screen.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* vulkan: Silence more -Wmissing-field-initializer warningsLioncash2020-08-031-0/+1
|
* Merge pull request #4324 from ReinUsesLisp/formatsbunnei2020-07-211-2/+2
|\ | | | | video_core: Fix, add and rename pixel formats
| * video_core: Rearrange pixel format namesReinUsesLisp2020-07-131-2/+2
| | | | | | | | | | | | Normalizes pixel format names to match Vulkan names. Previous to this commit pixel formats had no convention, leading to confusion and potential bugs.
* | vk_blit_screen: Make use of designated initializers where applicableLioncash2020-07-131-334/+384
|/ | | | | Now that we make use of C++20, we can use designated initializers to make things a little nicer to read.
* vk_blit_screen: Initialize all members in VkPipelineViewportStateCreateInfoReinUsesLisp2020-04-151-0/+2
| | | | | | | | | | | | When the dynamic state is specified, pViewports and pScissors are ignored, quoting the specification: pViewports is a pointer to an array of VkViewport structures, defining the viewport transforms. If the viewport state is dynamic, this member is ignored. That said, AMD's proprietary driver itself seem to read it regardless of what the specification says.
* renderer_vulkan: Drop Vulkan-HppReinUsesLisp2020-04-111-211/+412
|
* vk_blit_screen: Address feedbackReinUsesLisp2020-01-201-13/+15
|
* vk_blit_screen: Initial implementationReinUsesLisp2020-01-201-0/+625
This abstraction takes care of presenting accelerated and non-accelerated or "framebuffer" images to the Vulkan swapchain.