-
Notifications
You must be signed in to change notification settings - Fork 437
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
Replace PipelineMemoryAccess
with PipelineStageAccess
#2212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a thing to consider, there already exists a crate that does this sort of thing that most if not all other projects use. Maybe we can use that in the future as well.
Teleporting here from #2223, where a sync hazard was found originating here. Looks like this: 2023-06-05.13-19-42.mp4Here's what the layer gave me:
|
So weird that I don't get any of these errors. |
Here's a dump of me running the indirect example, with the API dump and validation layers enabled. |
My bad, those validation errors are caused by something older still. I'll make sure to track that down sometime soon, just ignore that. |
Here's my dump: dump.txt |
This dump only contains the API calls, not the validation errors that occur as they are called. I really need both as a single stream to be able to correlate them together. |
…#2212) * Replace `PipelineMemoryAccess` with `PipelineStageAccess` * Rename `is_2` to something better * Missed rename
When making the late new command buffer, I introduced the crate-private
PipelineStageAccess
type to provide the ability to more finely specify the access types of individual commands. It seemed to be still useful for the existing command buffer, and possibly for task graphs later too, so I improved on it and replaced the olderPipelineMemoryAccess
struct with it.