Lots of shader errors

[pluiedev]

Not sure where to begin debugging this one... Normally I woulda just given up but it looks like this project is actively maintained so I'm giving it a shot:

MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_render_pipeline
      note: label = `smaa.pipeline.edge_detect`
    Internal error in VERTEX shader: 0:96(2): error: value of type vec4 cannot be assigned to variable of type float
0:104(2): error: value of type vec4 cannot be assigned to variable of type float
0:112(2): error: value of type vec4 cannot be assigned to variable of type float
0:129(2): error: value of type vec4 cannot be assigned to variable of type float
0:137(2): error: value of type vec4 cannot be assigned to variable of type float
0:141(2): error: initializer of type float cannot be assigned to variable of type vec4
0:143(2): error: initializer of type float cannot be assigned to variable of type vec4
0:147(2): error: initializer of type float cannot be assigned to variable of type vec4
0:149(2): error: initializer of type float cannot be assigned to variable of type vec4
0:151(2): error: value of type vec4 cannot be assigned to variable of type float
0:188(2): error: no matching function for call to `SMAAEdgeDetectionVS(vec2, vec4[3])'; candidates are:
0:188(2): error:    void SMAAEdgeDetectionVS(vec2, vec4)


', /home/<redacted>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wgpu-0.15.0/src/backend/direct.rs:3024:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[fintelia]

I was able to reproduce this issue by running with WGPU_BACKEND=gl cargo test.

[fintelia]

Thanks for reporting this! I just opened gfx-rs/naga#2248 which I believe is the root cause, though if I have time I'll try implementing a workaround.

[pluiedev]

Huh, didn't expect a naga bug would be the root cause of this — thanks for looking into that!