✨ Implement Multiple Data Transfers from Host-to-Device Staging#91
Merged
Conversation
…nor fixes in skybox.cppm
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Task Description
This PR resolves issue #90 .
Current
vk::buffer::transferAPI in vulkan-cpp has limitations, which would require to callvkMapMemoryandvkUnmapMemoryfor each sub-range resource just to transfer those data from the host to the device.The issues comes effectively when having a group of composite resources such as cubemaps (6-faces), textures arrays, or multiple segments that are packed tightly together.
Changelogs
std::ranges::forward_range.vkMapMemory/vkUnmapMemorysequence call.