-
Notifications
You must be signed in to change notification settings - Fork 435
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
Resources management suggestion #1
Comments
Vulkan doesn't guarantee that command buffers will be executed in the order you submit them, so this idea is discarded. |
Limeth
pushed a commit
to Limeth/vulkano
that referenced
this issue
Jun 16, 2019
Feature hashable types
blacksailer
pushed a commit
to blacksailer/vulkano
that referenced
this issue
Nov 27, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is mostly a post-it so that I don't forget this idea.
It should be possible to transition resources between states encoded in the type system, like this:
You could only modify a
Buffer
. When executing a command, the user could choose between creating a fence or not. If creating a fence, theBuffer
would turn into aFenceLockedBuffer
. If not creating a fence, theBuffer
would turn into aLockedBuffer
.A
FenceLockedBuffer
could be turned back into aBuffer
by blocking. BothFenceLockedBuffer
andLockedBuffer
could be used when executing commands.However this system doesn't say how to handle the relationship between buffers/textures and command buffers.
The text was updated successfully, but these errors were encountered: