Validation Layers reporting changes between 1.2.131.2 and 1.2.141.2 Lunarg Runtimes

Vulkan
1

Hello.

I have noticed a difference in the reporting of validation warnings / error between 1.2.131 and 1.2.141 Runtimes.

1.2.131 Runtime
Submitting a signaled fence via vkQueueSubmit generates “Dispatch Handle submitted in signaled state”

1.2.141 Runtime
Submitting a signaled fence via vkQueueSubmit does not generate any error message.

This is also true of some of the other reportings where the program running on 1.2.141 version throws an access violation error, when the program running on 1.2.131 show validation layer warnings.

This is happening on NVidia and AMD hardware.

I am guessing its the runtime because i installed the 1.2.141 SDK which installed the runtime as well and building the program with 1.2.131 SDK and 1.2.141 SDK yielded similar results (no validation layer errors).

Are there changes in the reporting? or are there different flag bits to be enabled in the debug messenger setup to get similar warning reported.

Best regards.
Nihal Kenkre.

2

The check seems to still be there. I tried to create presignaled Fence and then submit using it, and I get (with 1.2.141.2):

VALIDATION+ERROR: [Fence(0x67C11F000000001A)]: UNASSIGNED-CoreValidation-MemTrack-FenceState(1497273503), “Validation Error: [ UNASSIGNED-CoreValidation-MemTrack-FenceState ] Object 0: handle = 0x67c11f000000001a, type = VK_OBJECT_TYPE_FENCE; | MessageID = 0x593e949f | VkFence 0x67c11f000000001a submitted in SIGNALED state. Fences must be reset before being submitted”

As for warnings, those are being largely moved to the Best Practices layer, which is off by default and needs to be enabled.

3

Hello…

Thank you for the response. It helped.

Best regards.
Nihal Kenkre.

4

This topic was automatically closed 183 days after the last reply. New replies are no longer allowed.