eden-emu/VulkanMemoryAllocator
18
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

change documentation to allow defragmentation of only buffers not images

Browse source 
#59
This commit is contained in:
Adam Sawicki 2019-04-17 13:33:27 +02:00
parent bb18b299dc
commit c9f948243c
3 changed files with 149 additions and 167 deletions
Download patch file Download diff file Expand all files Collapse all files

14
src/vk_mem_alloc.h
View file

@ -907,19 +907,7 @@ in function vmaDefragmentationBegin().
\section defragmentation_additional_notes Additional notes
It is only legal to defragment allocations bound to:
- buffers
- images created with `VK_IMAGE_CREATE_ALIAS_BIT`, `VK_IMAGE_TILING_LINEAR`, and
being currently in `VK_IMAGE_LAYOUT_GENERAL` or `VK_IMAGE_LAYOUT_PREINITIALIZED`.
Defragmentation of images created with `VK_IMAGE_TILING_OPTIMAL` or in any other
layout may give undefined results.
If you defragment allocations bound to images, new images to be bound to new
memory region after defragmentation should be created with `VK_IMAGE_LAYOUT_PREINITIALIZED`
and then transitioned to their original layout from before defragmentation if
needed using an image memory barrier.
<b>It is only legal to defragment allocations bound to buffers, not images!</b>
While using defragmentation, you may experience validation layer warnings, which you just need to ignore.
See [Validation layer warnings](@ref general_considerations_validation_layer_warnings).