CBuffer/arrays.test: Match output buffer stride and size to the Arrays struct definition.#1260
Merged
manon-traverse merged 1 commit intoJun 10, 2026
Conversation
bogner
approved these changes
Jun 9, 2026
EmilioLaiso
approved these changes
Jun 10, 2026
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
3 participants
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.
The output buffer in
Cbuffer/arrays.testhas 4 extra integers at the end that didn't match with theArraysstruct that is defined in the shader. The stride also did not match the one of the struct. By removing the padding and setting the stride to128we can fix this issue.