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 }}
This repository has been archived by the owner on Jul 29, 2021. It is now read-only.
The Vulkan spec here states that calling vkGetInstanceProcAddr with a NULL instance must return NULL for all but a few functions listed out in the spec. As such, a conforming implementation is required to return null here (though no implementation actually does).
The fix is to look up the correct VkInstance handle associate with the VkPhysicalDevice handle that is passed by this function and to pass that instance handle to vkGetInstanceProcAddr.
The text was updated successfully, but these errors were encountered:
The overlay layer doesn't seem to actually build anymore, so the best solution to this issue is probably to just remove the overlay from this repo since it isn't being maintained.
@Tony-LunarG If there are samples that aren't being built anymore, we should deprecate/remove them from the repository They are also being included in the SDK and developers could be referencing the sample code for a layer. Issue #1373 has revealed the negative impacts of layers not following the specification and we are working on finding ways to discourage new layers exhibiting this behavior. Hence why we should remove the layer sample that isn't following the convention from the samples repository to ensure it isn't being referenced during layer development.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Inside
vkCreateDevice
the overlay layer gets a pointer to the next layer like:The Vulkan spec here states that calling
vkGetInstanceProcAddr
with a NULL instance must return NULL for all but a few functions listed out in the spec. As such, a conforming implementation is required to return null here (though no implementation actually does).The fix is to look up the correct
VkInstance
handle associate with theVkPhysicalDevice
handle that is passed by this function and to pass that instance handle tovkGetInstanceProcAddr
.The text was updated successfully, but these errors were encountered: