anonymous/yuzu - yuzu is the world's most popular, open-source, Nintendo Switch emulator — started by the creators of Citra. It is written in C++ with portability in mind,

	Commit message (Collapse)	Author	Files	Lines
2020-04-22	vk_fence_manager: Initial implementation	ReinUsesLisp	1	-0/+20

2020-04-14	renderer_vulkan: Integrate Nvidia Nsight Aftermath on Windows	ReinUsesLisp	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.
2020-04-13	renderer_vulkan: Remove Nvidia checkpoints	ReinUsesLisp	1	-6/+0

2020-04-13	renderer_vulkan: Catch device losses in more places	ReinUsesLisp	1	-18/+7

2020-04-01	renderer_vulkan/wrapper: Add vkEnumerateInstanceExtensionProperties wrapper	ReinUsesLisp	1	-0/+3

2020-04-01	renderer_vulkan/wrapper: Add command buffer handle	ReinUsesLisp	1	-0/+192

2020-04-01	renderer_vulkan/wrapper: Add physical device handle	ReinUsesLisp	1	-0/+40

2020-04-01	renderer_vulkan/wrapper: Add device handle	ReinUsesLisp	1	-0/+95

2020-04-01	renderer_vulkan/wrapper: Add swapchain handle	ReinUsesLisp	1	-0/+7

2020-04-01	renderer_vulkan/wrapper: Add fence handle	ReinUsesLisp	1	-0/+17

2020-04-01	renderer_vulkan/wrapper: Add device memory handle	ReinUsesLisp	1	-0/+15

2020-04-01	renderer_vulkan/wrapper: Add pool handles	ReinUsesLisp	1	-0/+15

2020-04-01	renderer_vulkan/wrapper: Add buffer and image handles	ReinUsesLisp	1	-0/+16

2020-04-01	renderer_vulkan/wrapper: Add queue handle	ReinUsesLisp	1	-0/+25

2020-04-01	renderer_vulkan/wrapper: Add instance handle	ReinUsesLisp	1	-0/+17

2020-03-28	renderer_vulkan/wrapper: Address feedback	ReinUsesLisp	1	-3/+24

2020-03-27	renderer_vulkan/wrapper: Add owning handles	ReinUsesLisp	1	-0/+18

2020-03-27	renderer_vulkan/wrapper: Add pool allocations owning templated class	ReinUsesLisp	1	-0/+81

2020-03-27	renderer_vulkan/wrapper: Add owning handle templated class	ReinUsesLisp	1	-0/+144

2020-03-27	renderer_vulkan/wrapper: Add destroy and free overload set	ReinUsesLisp	1	-0/+28

2020-03-27	renderer_vulkan/wrapper: Add dispatch table and loaders	ReinUsesLisp	1	-0/+137

2020-03-27	renderer_vulkan/wrapper: Add exception class	ReinUsesLisp	1	-0/+30

2020-03-27	renderer_vulkan/wrapper: Add ToString function for VkResult	ReinUsesLisp	1	-0/+3

2020-03-27	renderer_vulkan/wrapper: Add Vulakn wrapper and a span helper	ReinUsesLisp	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.