Unhelpful error for invalid textures
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
## Bevy version and features
Version `0.17.3` with default and `exr` features.
## \[Optional\] Relevant system information
```
AdapterInfo { name: "NVIDIA GeForce RTX 3060", vendor: 4318, device: 9351, device_type: DiscreteGpu, driver: "32.0.15.7657", driver_info: "", backend: Dx12 }
```
## What you did
I started my program and waited a bit
## What went wrong
Wgpu paniced
## Additional information
```
2025-12-16T18:00:28.328968Z ERROR wgpu::backend::wgpu_core: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (1)' (18672) panicked at C:\Users\buchT\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\wgpu-26.0.1\src\backend\wgpu_core.rs:1195:26:
wgpu error: Validation Error
Caused by:
In Device::create_bind_group, label = 'mesh_view_bind_group_binding_array'
Texture binding 0 expects dimension = Cube, but given a view with dimension = D2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_pbr::render::mesh_view_bindings::prepare_mesh_view_bind_groups`!
```
EDIT: This is an issue with the Environment Light Map
Contributor guide
Research direction
Start at bevy_pbr::render::mesh_view_bindings::prepare_mesh_view_bind_groups and reproduce with the reported Bevy 0.17.3 default and exr features using the Environment Light Map. Trace how its invalid texture view reaches wgpu's create_bind_group validation, then verify that the resulting diagnostic is helpful instead of the current panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100