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

Expose Previous Frame Sync #348

Closed
freesig opened this issue Jun 14, 2019 · 0 comments · Fixed by #452
Closed

Expose Previous Frame Sync #348

freesig opened this issue Jun 14, 2019 · 0 comments · Fixed by #452
Assignees

Comments

@freesig
Copy link
Collaborator

freesig commented Jun 14, 2019

Problem

Currently there is no way to get hold of the fence that is signaled by the gpu when the previous frame (and it's command buffer) is submitted.

Motivation

We need to be able to know when the previous command buffer is done so that we can tell that any copys that we added to the previous frame are done. Then we know it's safe to access the buffers associated with these copys.

Solution

We basically need a good way to expose pub(crate) previous_frame_end: Mutex<Option<vk::FenceSignalFuture<Boxvk::GpuFuture>>>,

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 a pull request may close this issue.

1 participant