You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you run Wicked Engine Editor or the Template Projects you will get spammed with validation errors if running VERBOSE and VULKAN. This is due to the imageAcquiredSemaphore associated with the Swapchain not finishing its wait operation before trying to present. After digging deep, it seems like we only wait on the fence associated with the imageAcquiredSemaphore AFTER presentation. Adding vkWaitForFences right before presentation does fix the problem but may not be the smartest solution...
To reproduce this error do these steps:
Clone repo. Build Solution. Set TemplateWindows as startup project. Build and Run.
Nothing happens yet.
Now in the commandline arguments: -vulkan and -gpu_verbose
Now you will see the validation errors.
The text was updated successfully, but these errors were encountered:
I added buffering to acquire semaphores. I thought semaphore is supposed to be GPU only, but it looks like vkAcquireNextImageKHR uses it from the CPU too since otherwise we wouldn't get validation warning immediately at this call.
Currently if you run Wicked Engine Editor or the Template Projects you will get spammed with validation errors if running VERBOSE and VULKAN. This is due to the imageAcquiredSemaphore associated with the Swapchain not finishing its wait operation before trying to present. After digging deep, it seems like we only wait on the fence associated with the imageAcquiredSemaphore AFTER presentation. Adding vkWaitForFences right before presentation does fix the problem but may not be the smartest solution...
To reproduce this error do these steps:
Clone repo. Build Solution. Set TemplateWindows as startup project. Build and Run.
Nothing happens yet.
Now in the commandline arguments: -vulkan and -gpu_verbose
Now you will see the validation errors.
The text was updated successfully, but these errors were encountered: