Bevy version 0.14.0-rc.4 The following is a simp

2d custom vertex attribute not working about bevy HOT 2 OPEN

jonathandw743 commented on August 24, 2024 1

2d custom vertex attribute not working

from bevy.

Comments (2)

jonathandw743 commented on August 24, 2024 1

Do you know if this worked in 0.13?

it did not.
In 0.13.2, the same code with very minor changes gives the same output:

2024-07-01T21:18:02.604417Z ERROR log: Device::create_render_pipeline error: Error matching ShaderStages(VERTEX) shader requirements against the pipeline    
2024-07-01T21:18:02.604511Z ERROR log: Handling wgpu errors as fatal by default    
thread 'Async Compute Task Pool (0)' panicked at /home/.../.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.19.4/src/backend/wgpu_core.rs:3006:5:
wgpu error: Validation Error

Caused by:
    In Device::create_render_pipeline
      note: label = `transparent_mesh2d_pipeline`
    Error matching ShaderStages(VERTEX) shader requirements against the pipeline
    Shader global ResourceBinding { group: 1, binding: 0 } is not available in the pipeline layout
    Buffer structure size 160, added to one element of an unbound array, if it's the last field, ended up greater than the given `min_binding_size`


note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::render_resource::pipeline_cache::PipelineCache::process_pipeline_queue_system`!
thread 'Compute Task Pool (0)' panicked at /home/.../.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_render-0.13.2/src/pipelined_rendering.rs:49:67:
called `Result::unwrap()` on an `Err` value: RecvError

This is the same as the 0.14 error, just with a bit less spam.

from bevy.