Minor addition to documentation.

This commit is contained in:
Adam Sawicki 2018-03-12 16:06:10 +01:00
parent 2283f4287a
commit 93ef5c2340
3 changed files with 120 additions and 110 deletions

View file

@ -673,6 +673,14 @@ about overlapping regions of memory bound to different kinds of buffers and
images. This is still valid as long as you implement proper handling of lost
allocations (like in the example above) and don't use them.
You can create an allocation that is already in lost state from the beginning using function
vmaCreateLostAllocation(). It may be useful if you need a "dummy" allocation that is not null.
You can call function vmaMakePoolAllocationsLost() to set all eligible allocations
in a specified custom pool to lost state.
Allocations that have been "touched" in current frame or VmaPoolCreateInfo::frameInUseCount frames back
cannot become lost.
\page statistics Statistics