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

extensions/khr/ray_tracing_pipeline: Set length of capture-replay shader handle buffer after filling #658

Merged
merged 2 commits into from
Sep 21, 2022

Conversation

djkoloski
Copy link
Contributor

Because the capacity is allocated but the length of the vector is not set, the vec returned from get_ray_tracing_capture_replay_shader_group_handles will always appear to be empty. I checked for other mistakes of this nature and did not locate any.

Copy link
Collaborator

@MarijnS95 MarijnS95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch! That was a bad yet-easy-to-make oopsie in the original Ray Tracing PR :)

Can you add a changelog item for this under a new ### Fixed designator?

ash/src/extensions/khr/ray_tracing_pipeline.rs Outdated Show resolved Hide resolved
@MarijnS95 MarijnS95 changed the title Set length of buffer after filling VK_KHR_ray_tracing_pipeline: Set length of capture-replay shader handle buffer after filling Sep 21, 2022
@MarijnS95 MarijnS95 changed the title VK_KHR_ray_tracing_pipeline: Set length of capture-replay shader handle buffer after filling extensions/khr/ray_tracing_pipeline: Set length of capture-replay shader handle buffer after filling Sep 21, 2022
@MarijnS95 MarijnS95 merged commit 5f4b1bb into ash-rs:master Sep 21, 2022
MarijnS95 pushed a commit that referenced this pull request Sep 22, 2022
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.

2 participants