Explain why renderFinishedSemaphores is sized per swapchain image - #473
Open
gpx1000 wants to merge 1 commit into
Open
Explain why renderFinishedSemaphores is sized per swapchain image#473gpx1000 wants to merge 1 commit into
gpx1000 wants to merge 1 commit into
Conversation
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
1 participant
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.
Unlike
presentCompleteSemaphores/inFlightFences,renderFinishedSemaphoresis sized by swapchain image count and indexed byimageIndex, notframeIndex— because the other side of its synchronization is the presentation engine, which only knows aboutimageIndex. This wasn't explained anywhere, so it looks inconsistent with the "duplicate per frame in flight" pattern taught elsewhere in the chapter. Adds that explanation.Fixes #310.