From 00069968e7b025cf1fbecda77241e75ec9a6285e Mon Sep 17 00:00:00 2001 From: Johannes Schneider Date: Fri, 28 May 2021 01:21:39 +0200 Subject: [PATCH] Remove reference to MoltenVK issue 175 which is fixed now --- include/vk_mem_alloc.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/include/vk_mem_alloc.h b/include/vk_mem_alloc.h index 3c8882e..5e5d2b1 100644 --- a/include/vk_mem_alloc.h +++ b/include/vk_mem_alloc.h @@ -440,8 +440,6 @@ There are some exceptions though, when you should consider mapping memory only f block is migrated by WDDM to system RAM, which degrades performance. It doesn't matter if that particular memory block is actually used by the command buffer being submitted. -- On Mac/MoltenVK there is a known bug - [Issue #175](https://github.com/KhronosGroup/MoltenVK/issues/175) - which requires unmapping before GPU can see updated texture. - Keeping many large memory blocks mapped may impact performance or stability of some debugging tools. \section memory_mapping_cache_control Cache flush and invalidate