Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autodesk: Vulkan Bugfix - HgiVulkanBlitCmds offset #3382

Open
wants to merge 1 commit into
base: feature-hgi-vulkan
Choose a base branch
from

Conversation

erikaharrison-adsk
Copy link
Contributor

Description of Change(s)

⚠️ Branched off feature-hgi-vulkan.

The staged copy of HgiVulkanBlitCmds has incorrect source and destination offset,

Source offset of a cpu-to-gpu-copy defines the offset of the source cpu memory, and the destination offset of a cpu-to-gpu-copy defines the offset of the destination gpu buffer.

The memcpy from the cpu memory to the staging buffer should use the source offset and the destination offset respectively. But the copy from the staging buffer to the gpu buffer should use the destination offset to define VkBufferCopy.srcOffset.

Link to proposal (if applicable)

N/A

Fixes Issue(s)

N/A

Checklist

[ ] I have created this PR based on the dev branch

[X] I have followed the coding conventions

[ ] I have added unit tests that exercise this functionality (Reference:
testing guidelines)

[X] I have verified that all unit tests pass with the proposed changes

[X] I have submitted a signed Contributor License Agreement (Reference:
Contributor License Agreement instructions)

…tion offset

Source offset of a cpu-to-gpu-copy defines the offset of the source cpu memory,
and the destination offset of a cpu-to-gpu-copy defines the offset of the
destination gpu buffer.

The `memcpy`` from the cpu memory to the staging buffer should use the source offset
and the destination offset respectively. But the copy from the staging buffer
to the gpu buffer should use the destination offset to define `VkBufferCopy.srcOffset`.
@jesschimein
Copy link
Contributor

Filed as internal issue #USD-10365

@jesschimein
Copy link
Contributor

/AzurePipelines run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants