-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix vulkan error per VUID-VkMemoryAllocateInfo-pNext-00639
Per https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkMemoryAllocateInfo.html#VUID-VkMemoryAllocateInfo-pNext-00639, dedicated allocation is required by certain externalMemoryFeatures. This change is to keep dedicated allocation in those scenarios for capture mode, while being assured no dedicated allocation for reading and replaying mode.
- Loading branch information
1 parent
0d8190e
commit 7b86a47
Showing
2 changed files
with
56 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7b86a47
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even we have to allow the dedicated memory in Capture mode per VUID-VkMemoryAllocateInfo-pNext-00639, we are still safe in ReplayingAndReading mode by
renderdoc/renderdoc/driver/vulkan/wrappers/vk_resource_funcs.cpp
Lines 310 to 325 in 322a069
Test plan:
Tested by a simple Android app with following codes in rendering loop.
vulkan error was raised from App, once it was launched from RenderDoc.
capturing/loading/replaying are all good.
no vulkan error happens..