Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation Errors With pNext Chain on Vulkan #2925

Closed
Rigidity opened this issue Jul 30, 2022 · 1 comment · Fixed by #2936
Closed

Validation Errors With pNext Chain on Vulkan #2925

Rigidity opened this issue Jul 30, 2022 · 1 comment · Fixed by #2936
Labels
area: correctness We're behaving incorrectly help required We need community help to make this happen. type: bug Something isn't working

Comments

@Rigidity
Copy link

Description
I get a long error about the pNext chain including structures that can't co-exist.

Here is the complete log.
2022-07-30T19:14:40.951440Z INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce RTX 3070 Ti", vendor: 4318, device: 9346, device_type: DiscreteGpu, backend: Vulkan } 2022-07-30T19:14:40.954007Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-VkDeviceCreateInfo-pNext-02830 (0x211e533b)] Validation Error: [ VUID-VkDeviceCreateInfo-pNext-02830 ] Object 0: handle = 0x1533402c970, type = VK_OBJECT_TYPE_INSTANCE; | MessageID = 0x211e533b | If the pNext chain includes a VkPhysicalDeviceVulkan12Features structure, then it must not include a VkPhysicalDevice8BitStorageFeatures, VkPhysicalDeviceShaderAtomicInt64Features, VkPhysicalDeviceShaderFloat16Int8Features, VkPhysicalDeviceDescriptorIndexingFeatures, VkPhysicalDeviceScalarBlockLayoutFeatures, VkPhysicalDeviceImagelessFramebufferFeatures, VkPhysicalDeviceUniformBufferStandardLayoutFeatures, VkPhysicalDeviceShaderSubgroupExtendedTypesFeatures, VkPhysicalDeviceSeparateDepthStencilLayoutsFeatures, VkPhysicalDeviceHostQueryResetFeatures, VkPhysicalDeviceTimelineSemaphoreFeatures, VkPhysicalDeviceBufferDeviceAddressFeatures, or VkPhysicalDeviceVulkanMemoryModelFeatures structure The Vulkan spec states: If the pNext chain includes a VkPhysicalDeviceVulkan12Features structure, then it must not include a VkPhysicalDevice8BitStorageFeatures, VkPhysicalDeviceShaderAtomicInt64Features, VkPhysicalDeviceShaderFloat16Int8Features, VkPhysicalDeviceDescriptorIndexingFeatures, VkPhysicalDeviceScalarBlockLayoutFeatures, VkPhysicalDeviceImagelessFramebufferFeatures, VkPhysicalDeviceUniformBufferStandardLayoutFeatures, VkPhysicalDeviceShaderSubgroupExtendedTypesFeatures, VkPhysicalDeviceSeparateDepthStencilLayoutsFeatures, VkPhysicalDeviceHostQueryResetFeatures, VkPhysicalDeviceTimelineSemaphoreFeatures, VkPhysicalDeviceBufferDeviceAddressFeatures, or VkPhysicalDeviceVulkanMemoryModelFeatures structure (https://vulkan.lunarg.com/doc/view/1.3.211.0/windows/1.3-extensions/vkspec.html#VUID-VkDeviceCreateInfo-pNext-02830) 2022-07-30T19:14:40.955357Z ERROR wgpu_hal::vulkan::instance: objects: (type: INSTANCE, hndl: 0x1533402c970, name: ?) 2022-07-30T19:14:44.227385Z INFO bevy_winit: Skipped event for closed window: WindowId(00000000-0000-0000-0000-000000000000) 2022-07-30T19:14:44.227639Z INFO bevy_winit: Skipped event for closed window: WindowId(00000000-0000-0000-0000-000000000000) 2022-07-30T19:14:44.229784Z INFO bevy_winit: Skipped event for closed window: WindowId(00000000-0000-0000-0000-000000000000)

Repro steps
Bevy Example (using version 0.8.0)
This is not a Bevy-specific error, though.

Expected vs observed behavior
It has validation errors, but it shouldn't and didn't in previous versions.

Extra materials
Nothing else to say.

Platform
On Windows 11 using Vulkan with an RTX 3070 Ti and AMD Ryzen 5600X.
Using wgpu 0.13

@cwfitzgerald cwfitzgerald added type: bug Something isn't working help required We need community help to make this happen. area: correctness We're behaving incorrectly labels Jul 31, 2022
@cwfitzgerald
Copy link
Member

For reference: this is functionally harmless, but something we should still fix as it's technically incorrect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: correctness We're behaving incorrectly help required We need community help to make this happen. type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants