Device memory allocate flags #1486
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
added pNext allocInfo for createBufferAndMemory()
so that we can customize the memory allocation, specifically for raytracing.
This resolves vulkan validation errors when creating memory with the
device address usage bit but without the bit set in the pNext structure.
Note that this PR includes changes found in #1439 and essentially takes it one step further.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
This was tested on our own raytracing example code. Was shown to work on linux windows and mac (arm).
Checklist: