Bevy version and features
- commit 7b65256
- the example is using
bevy_core_pipeline::mip_generation::experimental::depth::early_downsample_depth
and
bevy_core_pipeline::mip_generation::experimental::depth::late_downsample_depth
Relevant system information
`AdapterInfo { name: "AMD Radeon RX 9070 (RADV GFX1201)", vendor: 4098, device: 30032, device_type: DiscreteGpu, device_pci_bus_id: "0000:03:00.0", driver: "radv", driver_info: "Mesa 25.3.5", backend: Vulkan, subgroup_min_size: 32, subgroup_max_size: 64, transient_saves_memory: false }`What you did
Run the example, it runs fine. Then hit Space to disable occlusion culling and it freaks out. It still renders, but it is jumping from one frame to another and then back effectively freezing.
What went wrong
Example is freezing and a bunch of error logs are flooding the output.
Additional information
I copied the repeating part of the logs, they are the same after this.
Logs with debug
WARNING: radv is not a conformant Vulkan implementation, testing use only.
2026-02-22T10:59:59.803376Z INFO bevy_render::renderer: AdapterInfo { name: "AMD Radeon RX 9070 (RADV GFX1201)", vendor: 4098, device: 30032, device_type: DiscreteGpu, device_pci_bus_id: "0000:03:00.0", driver: "radv", driver_info: "Mesa 25.3.5", backend: Vulkan, subgroup_min_size: 32, subgroup_max_size: 64, transient_saves_memory: false }
2026-02-22T11:00:00.068087Z INFO gilrs_core::platform::platform::gamepad: Gamepad /dev/input/event6 (Keychron Keychron V3 System Control) connected.
2026-02-22T11:00:00.134685Z INFO bevy_render::batching::gpu_preprocessing: GPU preprocessing is fully supported on this device.
2026-02-22T11:00:00.139706Z INFO bevy_winit::system: Creating new window Bevy Occlusion Culling Example (63v0)
2026-02-22T11:00:00.176055Z INFO bevy_input::gamepad: Gamepad 292v0 connected.
2026-02-22T11:00:12.468476Z ERROR bevy_render::error_handler: Caught rendering error: Validation Error
Caused by:
In Device::create_bind_group, label = 'downsample multisample depth bind group'
Usage flags TextureUsages(RENDER_ATTACHMENT) of TextureView with '' label do not contain required usage flags TextureUsages(TEXTURE_BINDING)
2026-02-22T11:00:12.470808Z ERROR RenderContextState::apply{system=bevy_pbr::render::gpu_preprocess::early_gpu_preprocess}: bevy_render::error_handler: Caught rendering error: Validation Error
Caused by:
In a CommandEncoder
In a set_immediates command
Provided immediate data written to offset 0..4 overruns the immediate data range with a size of 0
2026-02-22T11:00:12.470853Z ERROR RenderContextState::apply{system=bevy_core_pipeline::mip_generation::experimental::depth::early_downsample_depth}: bevy_render::error_handler: Caught rendering error: Validation Error
Caused by:
In a CommandEncoder
In a set_bind_group command
BindGroup with 'downsample multisample depth bind group' label is invalid
2026-02-22T11:00:12.471092Z ERROR RenderContextState::apply{system=bevy_core_pipeline::mip_generation::experimental::depth::late_downsample_depth}: bevy_render::error_handler: Caught rendering error: Validation Error
Caused by:
In a CommandEncoder
In a set_bind_group command
BindGroup with 'downsample multisample depth bind group' label is invalid
2026-02-22T11:00:12.471393Z ERROR queue_submit{count=9}: bevy_render::error_handler: Caught rendering error: Validation Error
Caused by:
In Queue::submit
In a set_immediates command
Provided immediate data written to offset 0..4 overruns the immediate data range with a size of 0
2026-02-22T11:00:12.476545Z ERROR bevy_render::error_handler: Caught rendering error: Validation Error
Bevy version and features
bevy_core_pipeline::mip_generation::experimental::depth::early_downsample_depthand
bevy_core_pipeline::mip_generation::experimental::depth::late_downsample_depthRelevant system information
What you did
Run the example, it runs fine. Then hit Space to disable occlusion culling and it freaks out. It still renders, but it is jumping from one frame to another and then back effectively freezing.
What went wrong
Example is freezing and a bunch of error logs are flooding the output.
Additional information
I copied the repeating part of the logs, they are the same after this.
Logs with debug