From 18aada29ef7cf90c3d85cbd83f670e0772bded22 Mon Sep 17 00:00:00 2001 From: Philip Rebohle Date: Tue, 16 Jul 2019 09:24:55 +0200 Subject: [PATCH] [dxvk] Don't put large resources into their own memory allocations This approach currently has two issues: - We might fail to allocate the resource on the desired memory type even if there is a chunk available that it would tif in - With 128MB chunks, this no longer seems to be beneficial anyway --- src/dxvk/dxvk_memory.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/dxvk/dxvk_memory.cpp b/src/dxvk/dxvk_memory.cpp index 9a8cec3d..1a692e5d 100644 --- a/src/dxvk/dxvk_memory.cpp +++ b/src/dxvk/dxvk_memory.cpp @@ -284,7 +284,7 @@ namespace dxvk { DxvkMemory memory; - if ((size >= type->heap->chunkSize / 4) || dedAllocInfo) { + if (size >= type->heap->chunkSize || dedAllocInfo) { DxvkDeviceMemory devMem = this->tryAllocDeviceMemory( type, flags, size, priority, dedAllocInfo);