johanhelsing / bevy_smud

Sdf 2d shape renderer for Bevy
Other
141 stars 10 forks source link

Gray borders around shapes #18

Closed Vixeliz closed 1 year ago

Vixeliz commented 1 year ago

Basically the title i'm not sure if it's due to my intel gpu or what. My console spits out some things but I'm pretty sure it's unrelated in case though here:

2022-11-05T00:18:39.528209Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1.5
2022-11-05T00:18:39.548085Z  INFO bevy_render::renderer: AdapterInfo { name: "Intel(R) UHD Graphics (CML GT2)", vendor: 32902, device: 39745, device_type: IntegratedGpu, backend: Vulkan }
2022-11-05T00:18:39.548672Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-VkDeviceCreateInfo-pNext-02830 (0x211e533b)]
        Validation Error: [ VUID-VkDeviceCreateInfo-pNext-02830 ] Object 0: handle = 0x55d6e0ac6500, 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://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkDeviceCreateInfo-pNext-02830)
2022-11-05T00:18:39.548723Z ERROR wgpu_hal::vulkan::instance:   objects: (type: INSTANCE, hndl: 0x55d6e0ac6500, name: ?)
2022-11-05T00:18:39.598406Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-VkDescriptorSetLayoutCreateInfo-descriptorType-03001 (0x8ac432cd)]
        Validation Error: [ VUID-VkDescriptorSetLayoutCreateInfo-descriptorType-03001 ] Object 0: handle = 0x55d6e13a95a0, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x8ac432cd | vkCreateDescriptorSetLayout(): binding (8) has VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT flag, but binding (1) has descriptor type VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC. The Vulkan spec states: If any binding has the VK_DESCRIPTOR_BINDING_UPDATE_AFTER_BIND_BIT bit set, then all bindings must not have descriptorType of VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC or VK_DESCRIPTOR_TYPE_STORAGE_BUFFER_DYNAMIC (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkDescriptorSetLayoutCreateInfo-descriptorType-03001)
2022-11-05T00:18:39.598511Z ERROR wgpu_hal::vulkan::instance

and heres a screenshot: 20221104_19h17m54s_grim

Vixeliz commented 1 year ago

After some more research appears linux + intel + msaa have some issues so setting msaa samples to 1 makes this issue disappear my bad sorry.