Warning `Too many textures in mesh pipeline view layout` when using SSAO and TAA together

[lomirus]

Bevy version

0.15.0

Relevant system information

• cargo 1.83.0 (5ffbef321 2024-10-29)
• Windows 11

AdapterInfo { name: "NVIDIA GeForce RTX 4070 SUPER", vendor: 4318, device: 10115, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "565.90", backend: Vulkan }

What you did

Trying to use the SSAO and the TAA together:

use bevy::{
    core_pipeline::experimental::taa::{TemporalAntiAliasPlugin, TemporalAntiAliasing},
    pbr::ScreenSpaceAmbientOcclusion,
    prelude::*,
};

fn setup(mut commands: Commands) {
    commands.spawn((
        Camera3d::default(),
        ScreenSpaceAmbientOcclusion::default(),
        TemporalAntiAliasing::default(),
        Msaa::Off,
    ));
}

fn main() {
    App::new()
        .add_plugins((DefaultPlugins, TemporalAntiAliasPlugin))
        .add_systems(Startup, setup)
        .run();
}

What went wrong

It prints the warning bevy_pbr::render::mesh_view_bindings: Too many textures in mesh pipeline view layout, this might cause us to hit `wgpu::Limits::max_sampled_textures_per_shader_stage` in some environments:

2024-12-01T09:58:00.186054Z  INFO bevy_render::renderer: AdapterInfo { name: "NVIDIA GeForce RTX 4070 SUPER", vendor: 4318, device: 10115, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "565.90", backend: Vulkan }
2024-12-01T09:58:00.326936Z  INFO bevy_winit::system: Creating new window "App" (0v1#4294967296)
2024-12-01T09:58:00.489292Z  WARN bevy_pbr::render::mesh_view_bindings: Too many textures in mesh pipeline view layout, this might cause us to hit `wgpu::Limits::max_sampled_textures_per_shader_stage` in some environments.

[DGriffin91]

This is a known issue. There are some system (WebGL2, WebGPU, and some native) that won't work when this warning occurs. Unfortunately the renderer is currently designed around binding lots of textures that aren't in use (which does possibly reduce pipeline switches in some cases, which can improve performance, but it could be designed to avoid the switches and not bind so many unused textures, it would just be a bit tricky). If you're concerned about the platform support, one option is to not use the StandardMaterial. I think this warning is expecting the StandardMaterial to be in use, which is a bit odd given it complains with out a material instance in the scene.

[komadori]

As of 0.16, TAA on its own is sufficient to trigger this warning for me.