Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash on pbr_opaque_mesh_pipeline with opengl backend #8086

Open
Kaesebrot84 opened this issue Mar 14, 2023 · 2 comments
Open

Crash on pbr_opaque_mesh_pipeline with opengl backend #8086

Kaesebrot84 opened this issue Mar 14, 2023 · 2 comments
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior P-Crash A sudden unexpected crash

Comments

@Kaesebrot84
Copy link

Bevy version

bevy = "0.10.0" also tried the (3d_scene) example with 0918b30e2925b2ce628d3e89f6e120e68c61a06c.

Relevant system information

  • cargo 1.67.0 (8ecd4f20a 2023-01-10)
  • os: "Linux 22.0.4 Manjaro Linux", kernel: "5.15.94-1-MANJARO"
`AdapterInfo { name: "AMD BARTS (DRM 2.50.0 / 5.15.94-1-MANJARO, LLVM 15.0.7)", vendor: 0, device: 0, device_type: Other, driver: "", driver_info: "", backend: Gl }`

What I did

So far I was able to use bevy for some 2d-setups. But when I try to run a 3d example I am constantly running into the same errors.

I tried to run the 3d_scene example locally with bevy = "0.10.0" in my Cargo.toml and I also tried running the same example in the repo's example folder. The results are always the same.

This might be related to gfx-rs/naga#841 see this comment.

What went wrong

This is the output I get before the app crashes:

2023-03-13T16:37:07.490477Z INFO bevy_render::renderer: AdapterInfo { name: "AMD BARTS (DRM 2.50.0 / 5.15.94-1-MANJARO, LLVM 15.0.7)", vendor: 0, device: 0, device_type: Other, driver: "", driver_info: "", backend: Gl }
2023-03-13T16:37:08.396321Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 22.0.4 Manjaro Linux", kernel: "5.15.94-1-MANJARO", cpu: "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz", core_count: "2", memory: "7.7 GiB" }
2023-03-13T16:37:08.634536Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 2 : GL_INVALID_ENUM in glTexStorage2DMultisample(target=GL_TEXTURE_2D)
2023-03-13T16:37:08.634845Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 2 : GL_INVALID_ENUM in glTexStorage2DMultisample(target=GL_TEXTURE_2D)
2023-03-13T16:37:09.024041Z ERROR wgpu::backend::direct: Shader translation error for stage FRAGMENT: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias
2023-03-13T16:37:09.024083Z ERROR wgpu::backend::direct: Please report it to https://github.com/gfx-rs/naga
2023-03-13T16:37:09.024150Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (0)' panicked at 'wgpu error: Validation Error

Caused by:
In Device::create_render_pipeline
note: label = pbr_opaque_mesh_pipeline
Internal error in FRAGMENT shader: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias

@Kaesebrot84 Kaesebrot84 added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels Mar 14, 2023
@StyMaar
Copy link

StyMaar commented Apr 1, 2023

I faced the same issue, this is likely related to gfx-rs/wgpu#4455 but the comments on that naga bug are a bit confusing.

@nicopap nicopap added A-Rendering Drawing game state to the screen P-Crash A sudden unexpected crash and removed S-Needs-Triage This issue needs to be labelled labels Apr 24, 2023
@nicopap
Copy link
Contributor

nicopap commented Apr 24, 2023

I can reproduce this running

WGPU_BACKEND=gl cargo run --example 3d_scene

On the linked commit and current main (a4323d5)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior P-Crash A sudden unexpected crash
Projects
None yet
Development

No branches or pull requests

3 participants