wgpu_hal console spam

[frank prism]

Whenever I run my project, I recieve a lot of console spam from wgpu_hal about a vulkan validation.

[dawn mauve]

try to remove dynamic_linking, on Windows is mostly broken afaik

[frank prism]

Thank you for the reply, however that didn't seem to do it. Here's my updated Cargo.toml

[package]
name = "sandwars"
version = "0.1.0"
edition = "2021"

[dependencies]
bevy = "0.11.3"

Here's also the full error

2023-10-21T13:29:14.362680Z  INFO bevy_window::system: No windows are open, exiting
2023-10-21T13:29:14.362959Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-VkRenderPassBeginInfo-framebuffer-04627 (0x45125641)]
        Validation Error: [ VUID-VkRenderPassBeginInfo-framebuffer-04627 ] Object 0: handle = 0xfb320f000000009d, type = VK_OBJECT_TYPE_RENDER_PASS; | MessageID = 0x45125641 | vkCmdBeginRenderPass: Image view #0 created from an image with usage set as (VK_IMAGE_USAGE_TRANSFER_SRC_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT) but using VkImageViewUsageCreateInfo the inherited usage is the subset (VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT) and the image info #0 used to create the framebuffer had usage set as (VK_IMAGE_USAGE_TRANSFER_SRC_BIT|VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT). The Vulkan spec states: If framebuffer was created with a VkFramebufferCreateInfo::flags value that included VK_FRAMEBUFFER_CREATE_IMAGELESS_BIT, each element of the pAttachments member of a VkRenderPassAttachmentBeginInfo structure included in the pNext chain must be a VkImageView with an inherited usage equal to the usage member of the corresponding element of VkFramebufferAttachmentsCreateInfo::pAttachmentImageInfos used to create framebuffer (https://vulkan.lunarg.com/doc/view/1.3.261.1/windows/1.3-extensions/vkspec.html#VUID-VkRenderPassBeginInfo-framebuffer-04627)

[dawn mauve]

can you show me your main.rs?

[dawn mauve]

here it says:
INFO bevy_window::system: No windows are open, exiting

are you adding DefaultPlugins or something that handle the Window?

[frank prism]

This is my fault. I copied the error message from the bottom of the console therefore it got infomation when I closed the window.

[frank prism]

use bevy::prelude::*;

mod rendering;
use rendering::camera;

fn main() {
    App::new()
    .add_plugins((
        DefaultPlugins,
        camera::CameraPlugin,
    ))
    .run();
}

[dawn mauve]

ah ok then I've no clue, I'm sorry 😄 I'll leave it to more experienced ones

[frank prism]

Ah that's ok, thank you anyways 🙂

[wary dirge]

This is logged any time a window is closed and no other windows were available. This is expected behaviour

@frank prism this should be fixed in bevy 0.12 which will release in a couple of days

for now you can safely just disable the vulkan validation layers

I believe this was caused by OBS doing something funky with the validation layers