Updated documentation of memory mapping with known bug in MoltenVK, based on #47. Thanks @DiegoAce !
This commit is contained in:
parent
b0c363693f
commit
7f97202add
3 changed files with 134 additions and 131 deletions
|
@ -391,7 +391,9 @@ There are some exceptions though, when you should consider mapping memory only f
|
|||
for the time of any call to `vkQueueSubmit()` or `vkQueuePresentKHR()`, this
|
||||
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.
|
||||
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 control
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue