From 34045555a65f40801ca29e6fc04e9e31a7ea3124 Mon Sep 17 00:00:00 2001 From: Adam Sawicki Date: Wed, 26 Jun 2019 14:46:53 +0200 Subject: [PATCH] Minor fix in documentation --- src/vk_mem_alloc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vk_mem_alloc.h b/src/vk_mem_alloc.h index 204f002..f2dc341 100644 --- a/src/vk_mem_alloc.h +++ b/src/vk_mem_alloc.h @@ -1505,7 +1505,7 @@ behavior is implementation-dependant - it depends on GPU vendor and graphics driver. On AMD cards it can be controlled while creating Vulkan device object by using -VK_AMD_memory_allocation_behavior extension, if available. +VK_AMD_memory_overallocation_behavior extension, if available. Alternatively, if you want to test how your program behaves with limited amount of Vulkan device memory available without switching your graphics card to one that really has