Closed HansKristian-Work closed 7 months ago
@HansKristian-Work I can reproduce the issue. It happens because submit synchronization validation is enabled by default, starting with the latest sdk. If you want, you can turn it off in vkconfig
(or programmatically) and leave only regular synchronization validation which does not produce errors. Meanwhile, I will investigate the issue.
@HansKristian-Work this was fixed in the latest code but only when binary semaphores are used (I used ext.vk12_features.timelineSemaphore = VK_FALSE;
in context.cpp
for testing).
Timeline semaphores are not supported by syncval at the moment (listed as known limitation here https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/docs/synchronization_usage.md#known-limitations)
so when timelines are enabled gltf-viewer-simple
will not spam but still will report one or few error messages and latency-test
will continue to spam.
I will create a separate issue for timeline semaphore support that will use the above two Granite's samples as a repro case.
Environment:
Describe the Issue
Trivial use of swapchain images triggers false positive sync val errors. The frame in question only renders a single render pass to swapchain with appropriate semaphores in between. To reproduce:
Expected behavior
No errors
Valid Usage ID
is spammed.