Skip to content

Commit b8e5747

Browse files
Fixed language mistake in the documentation
1 parent e1bdbca commit b8e5747

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

include/vk_mem_alloc.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17048,7 +17048,7 @@ implementation whether the allocation succeeds or fails. You can change this beh
1704817048
by using #VMA_ALLOCATION_CREATE_WITHIN_BUDGET_BIT flag. With it, the allocation is
1704917049
not made if it would exceed the budget or if the budget is already exceeded.
1705017050
VMA then tries to make the allocation from the next eligible Vulkan memory type.
17051-
The all of them fail, the call then fails with `VK_ERROR_OUT_OF_DEVICE_MEMORY`.
17051+
If all of them fail, the call then fails with `VK_ERROR_OUT_OF_DEVICE_MEMORY`.
1705217052
Example usage pattern may be to pass the #VMA_ALLOCATION_CREATE_WITHIN_BUDGET_BIT flag
1705317053
when creating resources that are not essential for the application (e.g. the texture
1705417054
of a specific object) and not to pass it when creating critically important resources

0 commit comments

Comments
 (0)