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
{{ message }}
Repository navigation
The validation layer warns on vkGetDeviceFaultInfoEXT when only pipeline creation reported the device lost #100
In the TDR runs of #85 (RX 580, amdvlk 31.0.21924.61, Windows 10), only vkCreateComputePipelines (Glass_Light, Reflect) returned VK_ERROR_DEVICE_LOST. vk_lost (rhi/vulkan_device.odin) then asks vkGetDeviceFaultInfoEXT for the description, and the validation layer prints:
vkGetDeviceFaultInfoEXT(): device has not been found to be in a lost state
The layer only takes a loss reported by the queue and wait calls, not one from pipeline creation, so it flags a call the driver answered.
The description was "No fault detected", so nothing is learned from the call in that case either.
No validation message when Mirai reacts to a loss the driver reported. Either vk_lost asks for fault info only when the loss came from a queue or wait call, or, if the call is valid there, the message goes upstream to Vulkan-ValidationLayers and is noted here.
Activity