Closed heinzelotto closed 1 year ago
I am also experiencing this issue. I can tell that it was working fine with bevy 0.9.1 but breaks in 0.10.0.
I just noticed the error tells me to report it to upstream, so I also did that now.
I am getting this now on 0.13.0. In Firefox it works but on Chromium I get:
wgpu error: Validation Error
Caused by:
In Device::create_render_pipeline
note: label = `tonemapping pipeline`
Internal error in ShaderStages(VERTEX) shader:
I get the error when looking at the examples. When I try to compile my own wasm project it works in 0.12.0 in Chromium but not on 0.13.0.
My CPU: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
My graphics: NVIDIA NVS 5400M
Bevy version
0.10.0 (or whichever version is currently used in the bevy WASM examples).
Relevant system information
Android 12 Chrome (v110.0) on pixel 3a, and android 13 Firefox (v110.1) on pixel 4a.
What you did
Opened the https://bevyengine.org/examples/3d/3d-scene/
What went wrong
The 3d scene does not load.
Additional information
I am not sure whether the error is in gfx-rs/naga or bevy's usage of it (through gfx-rs/wgpu). The string
Assertion failed: false && "Unknown named pointer type or missing metadata"
also appears in https://github.com/google/filament/issues/6355 .My own bevy application that uses PbrBundles also had this problem in the WASM build. Then while looking for a cause I noticed that the example also does not run. Removing all PbrBundles or rolling back to bevy 0.9.1 both cause the error to disappear.
chrome on android console log: