diff --git a/docs/html/custom_memory_pools.html b/docs/html/custom_memory_pools.html index c40e397..2386363 100644 --- a/docs/html/custom_memory_pools.html +++ b/docs/html/custom_memory_pools.html @@ -84,8 +84,13 @@ $(function() {
You have to free all allocations made from this pool before destroying it.
When creating a pool, you must explicitly specify memory type index. To find the one suitable for your buffers or images, you can use code similar to the following:
-Dummy buffer is needed to query driver for memReq.memoryTypeBits
. Memory is never allocated for this buffer. You should fill structures dummyBufCreateInfo
and allocCreateInfo
with the same parameters as you are going to use for buffers created in your pool.
When creating a pool, you must explicitly specify memory type index. To find the one suitable for your buffers or images, you can use helper functions vmaFindMemoryTypeIndexForBufferInfo(), vmaFindMemoryTypeIndexForImageInfo(). You need to provide structures with example parameters of buffers or images that you are going to create in that pool.
+Dummy buffer is needed to query driver for memReq.memoryTypeBits
. Memory is never allocated for this buffer. You should fill structures dummyBufCreateInfo
and allocCreateInfo
with the same parameters as you are going to use for buffers created in your pool.
When creating buffers/images allocated in that pool, provide following parameters:
+VkBufferCreateInfo
: Prefer to pass same parameters as above. Otherwise you risk creating resources in a memory type that is not suitable for them, which may result in undefined behavior. Using different VK_BUFFER_USAGE_
flags may work, but you shouldn't create images in a pool intended for buffers or the other way around.pool
member. Other members are ignored anyway.