-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Potential Bug] Render Complete Semaphore is specified using currentFrame
rather than imageIndex
which can cause sync validation errors.
#90
Comments
Additionally, the index for the |
Ok, I saw this issue some weeks ago, becuase it caused validation warnings. Perviously, everything as reported as correct. I was not using the proper image index returned while acquiring the image. But I already uploaded a fix for that, and the valiaton error messages are goone. Therfore, it seems to be working now. In any case, just for you to know. I'm currently working on a new version of the book with the following deisgn goals:
I'm also planning in including a sample for PhysX. It is taking some time, but I'm working on it. |
Sounds awesome! I will take a look at it when it's done, although not looking forward to more sync error nightmares. Hopefully it will run faster though :) |
I can give access to the working source code if you want to have a look. I'm regulary testing with sync validation layers on. |
Sure if you want. Just DM me on discord I guess. |
As title suggests. I noticed this after comparing my work with yours (having previously followed the tutorial before), and having conferred with someone in the Vulkan discord.
The solution would be to create an array of Semaphores and access them using the
imageIndex
passed back fromacquireNextImage
, in place of the currentrenderCompleteSemaphore
within theSyncSemaphores
record.You could also do the same by specially accessing the SyncSemaphores array for the render complete semaphore:
syncSemaphores[imageIndex].renderCompleteSemaphore().vkSemaphore
The text was updated successfully, but these errors were encountered: