Internal fix in VmaBlockVector::AllocatePage

This commit is contained in:
Adam Sawicki 2022-02-08 16:31:11 +01:00
parent 37c2d74b05
commit a1895bc765

View File

@ -12252,7 +12252,8 @@ VkResult VmaBlockVector::AllocatePage(
freeMemory = (heapBudget.usage < heapBudget.budget) ? (heapBudget.budget - heapBudget.usage) : 0; freeMemory = (heapBudget.usage < heapBudget.budget) ? (heapBudget.budget - heapBudget.usage) : 0;
} }
const bool canFallbackToDedicated = !IsCustomPool(); const bool canFallbackToDedicated = !HasExplicitBlockSize() &&
(createInfo.flags & VMA_ALLOCATION_CREATE_NEVER_ALLOCATE_BIT) == 0;
const bool canCreateNewBlock = const bool canCreateNewBlock =
((createInfo.flags & VMA_ALLOCATION_CREATE_NEVER_ALLOCATE_BIT) == 0) && ((createInfo.flags & VMA_ALLOCATION_CREATE_NEVER_ALLOCATE_BIT) == 0) &&
(m_Blocks.size() < m_MaxBlockCount) && (m_Blocks.size() < m_MaxBlockCount) &&