David
David
Replacing the viewer->compile() with a compileManager in our frame loop appears to have solved the issue. Thanks! I suppose it will make a difference, performance wise, between passing the scene...
vsgExamples, VulkanSceneGraph and vsgXChange are all on master. Machine is using Windows 11, our team doesn't see this on certain machines so it may be GPU specific.
I do get varying results with different Vulkan SDK versions using vsgdraw -d, I'm changing the path to VkLayer_khronos_validation.json using regedit in location Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ExplicitLayers: 1.3.268.0: No validation errors 1.3.283.0: Constantly...
@AnyOldName3 I have a proposed fix for this error (01779), by creating a semaphore for each image, do you have any input about potential drawbacks? See commit: https://github.com/vsg-dev/VulkanSceneGraph/commit/b4d04d569ae60edb218e74a55a67adc380d4e687
Thanks for merging Robert, the error is fixed on master.