Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Vk Async pipeline compilation | ameerj | 2020-08-16 | 1 | -1/+1 |
| | |||||
* | General: Tidy up clang-format warnings part 2 | Lioncash | 2020-08-13 | 1 | -14/+14 |
| | |||||
* | Merge pull request #4150 from ReinUsesLisp/dynamic-state-impl | bunnei | 2020-07-07 | 1 | -0/+54 |
|\ | | | | | vulkan: Use VK_EXT_extended_dynamic_state when available | ||||
| * | renderer_vulkan/wrapper: Add VK_EXT_extended_dynamic_state functions | ReinUsesLisp | 2020-06-27 | 1 | -0/+54 |
| | | |||||
* | | renderer_vulkan: Update validation layer name and test before enabling | ReinUsesLisp | 2020-06-22 | 1 | -0/+4 |
|/ | | | | | | | Update validation layer string to VK_LAYER_KHRONOS_validation. While we are at it, properly check for available validation layers before enabling them. | ||||
* | vulkan/wrapper: Remove noexcept from GetSurfaceCapabilitiesKHR() | Lioncash | 2020-06-20 | 1 | -1/+1 |
| | | | | | | | Check() can throw an exception if the Vulkan result isn't successful. We remove the check so that std::terminate isn't outright called and allows for better debugging (should it ever actually fail). | ||||
* | {maxwell_3d,buffer_cache}: Implement memory barriers using 3D registers | ReinUsesLisp | 2020-04-28 | 1 | -0/+10 |
| | | | | | | | | | | | | | Drop MemoryBarrier from the buffer cache and use Maxwell3D's register WaitForIdle. To implement this on OpenGL we just call glMemoryBarrier with the necessary bits. Vulkan lacks this synchronization primitive, so we set an event and immediately wait for it. This is not a pretty solution, but it's what Vulkan can do without submitting the current command buffer to the queue (which ends up being more expensive on the CPU). | ||||
* | Merge pull request #3677 from FernandoS27/better-sync | bunnei | 2020-04-23 | 1 | -0/+20 |
|\ | | | | | Introduce Predictive Flushing and Improve ASYNC GPU | ||||
| * | vk_fence_manager: Initial implementation | ReinUsesLisp | 2020-04-22 | 1 | -0/+20 |
| | | |||||
* | | renderer_vulkan: Integrate Nvidia Nsight Aftermath on Windows | ReinUsesLisp | 2020-04-14 | 1 | -2/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds optional support for Nsight Aftermath. It is enabled through ENABLE_NSIGHT_AFTERMATH in cmake. A path to the SDK has to be provided by the environment variable NSIGHT_AFTERMATH_SDK. Nsight Aftermath allows an application to generate "minidumps" of the GPU state when a device loss happens. By analysing these on Nsight we can know what a game was doing and why it triggered a device loss. The dump is generated inside %APPDATA%\yuzu\log\gpucrash and this directory is deleted every time a new instance is initialized with Nsight enabled. To enable it on yuzu there has a to be a driver and device capable of running Nsight Aftermath on Vulkan. That means only Turing based GPUs on the latest stable driver, beta drivers won't work for now. It is manually enabled in Configuration>Debug>Enable Graphics Debugging because when using all debugging capabilities there is a runtime cost. | ||||
* | | renderer_vulkan: Remove Nvidia checkpoints | ReinUsesLisp | 2020-04-13 | 1 | -6/+0 |
| | | |||||
* | | renderer_vulkan: Catch device losses in more places | ReinUsesLisp | 2020-04-13 | 1 | -18/+7 |
|/ | |||||
* | renderer_vulkan/wrapper: Add vkEnumerateInstanceExtensionProperties wrapper | ReinUsesLisp | 2020-04-01 | 1 | -0/+3 |
| | |||||
* | renderer_vulkan/wrapper: Add command buffer handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+192 |
| | |||||
* | renderer_vulkan/wrapper: Add physical device handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+40 |
| | |||||
* | renderer_vulkan/wrapper: Add device handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+95 |
| | |||||
* | renderer_vulkan/wrapper: Add swapchain handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+7 |
| | |||||
* | renderer_vulkan/wrapper: Add fence handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+17 |
| | |||||
* | renderer_vulkan/wrapper: Add device memory handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+15 |
| | |||||
* | renderer_vulkan/wrapper: Add pool handles | ReinUsesLisp | 2020-04-01 | 1 | -0/+15 |
| | |||||
* | renderer_vulkan/wrapper: Add buffer and image handles | ReinUsesLisp | 2020-04-01 | 1 | -0/+16 |
| | |||||
* | renderer_vulkan/wrapper: Add queue handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+25 |
| | |||||
* | renderer_vulkan/wrapper: Add instance handle | ReinUsesLisp | 2020-04-01 | 1 | -0/+17 |
| | |||||
* | renderer_vulkan/wrapper: Address feedback | ReinUsesLisp | 2020-03-28 | 1 | -3/+24 |
| | |||||
* | renderer_vulkan/wrapper: Add owning handles | ReinUsesLisp | 2020-03-27 | 1 | -0/+18 |
| | |||||
* | renderer_vulkan/wrapper: Add pool allocations owning templated class | ReinUsesLisp | 2020-03-27 | 1 | -0/+81 |
| | |||||
* | renderer_vulkan/wrapper: Add owning handle templated class | ReinUsesLisp | 2020-03-27 | 1 | -0/+144 |
| | |||||
* | renderer_vulkan/wrapper: Add destroy and free overload set | ReinUsesLisp | 2020-03-27 | 1 | -0/+28 |
| | |||||
* | renderer_vulkan/wrapper: Add dispatch table and loaders | ReinUsesLisp | 2020-03-27 | 1 | -0/+137 |
| | |||||
* | renderer_vulkan/wrapper: Add exception class | ReinUsesLisp | 2020-03-27 | 1 | -0/+30 |
| | |||||
* | renderer_vulkan/wrapper: Add ToString function for VkResult | ReinUsesLisp | 2020-03-27 | 1 | -0/+3 |
| | |||||
* | renderer_vulkan/wrapper: Add Vulakn wrapper and a span helper | ReinUsesLisp | 2020-03-27 | 1 | -0/+83 |
The intention behind a Vulkan wrapper is to drop Vulkan-Hpp. The issues with Vulkan-Hpp are: - Regular breaks of the API. - Copy constructors that do the same as the aggregates (fixed recently) - External dynamic dispatch that is hard to remove - Alias KHR handles with non-KHR handles making it impossible to use smart handles on Vulkan 1.0 instances with extensions that were included on Vulkan 1.1. - Dynamic dispatchers silently change size depending on preprocessor definitions. Different files will have different dispatch definitions, generating all kinds of hard to debug memory issues. In other words, Vulkan-Hpp is not "production ready" for our needs and this wrapper aims to replace it without losing RAII and exception safety. |