Meshes not rendering with default GpuPreprocessing on Intel integrated GPU

[xenon615]

Bevy version

0.15.3 and 0.16 ( commit #12f71a8)

Relevant system information

OS Windows 11

AdapterInfo { name: "Intel(R) UHD Graphics 630", vendor: 32902, device: 16018, device_type: IntegratedGpu, driver: "?", driver_info: "?", backend: Vulkan }

What I did

Trying to draw 2 simple 3d shapes.
Sphere using standard material (red) and cube using shader (blue)

Link to repo

What was expected

What went wrong

With version 0.15.3 everything happens as expected. But with 0.16 we have 3 options:

1. both shapes are displayed (correct option)
2. only the cube (blue)
3. only the sphere at first blue quickly becomes red

[Henauxg]

I could not reproduce with AdapterInfo { name: "NVIDIA GeForce RTX 4070", vendor: 4318, device: 10118, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "572.83", backend: Vulkan }. I will try later with an intel integrated GPU.

Just to gather more info for this issue: you 3 mentioned options, is one happening at random when you start the program, and does it change after a compilation or just when you re-run the compiled program ?

Is it possible that your intel drivers are outdated ?

[xenon615]

Just to get gather more info for this issue: in you 3 mentioned options, is one happening at random when you start the program, and does it change after a compilation or just when you re run the compiled program ?

When rerun compiled program.

[Henauxg]

Could not reproduce on:
AdapterInfo { name: "NVIDIA GeForce GTX 1660 Ti", vendor: 4318, device: 8593, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "566.03", backend: Vulkan }

However I tested on the same integrated GPU (UHD Graphics 630) and could reproduce the issue:
AdapterInfo { name: "Intel(R) UHD Graphics 630", vendor: 32902, device: 16027, device_type: IntegratedGpu, driver: "Intel Corporation", driver_info: "Intel driver", backend: Vulkan }

I linked a small video, running the sample 3 times, each time with a different result. The last time showcasing the ball starting blue then turning red and the cube not rendering.

2025-04-23.23-12-22_issue.mp4

[Henauxg]

Upgrading intel drivers to the latest release (31.0.101.2135) did not resolve the issue

[Henauxg]

The custom material & shader is not the issue. I could also reproduce it partially with just 2 simple rgb StandardMaterial.

Partially because, I now simply get some runs with both shapes rendering properly, and some runs with just the sphere rendering and not the cube. The color swap does not seem to appear with this setup.

Minimal repro:

use bevy::prelude::*;

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

fn startup(
    mut cmd: Commands,
    mut meshes: ResMut<Assets<Mesh>>,
    mut materials: ResMut<Assets<StandardMaterial>>,
) {
    cmd.spawn((
        Mesh3d(meshes.add(Sphere::new(0.5))),
        MeshMaterial3d(materials.add(Color::srgb(1., 0., 0.))),
        Transform::from_xyz(-2., 0., 0.)
    ));

    cmd.spawn((
        Mesh3d(meshes.add(Cuboid::from_length(1.))),
        MeshMaterial3d(materials.add(Color::srgb(0., 0., 1.))),
        Transform::from_xyz(2., 0., 0.)
    ));

    cmd.spawn((
        Camera3d::default(),
        Transform::from_xyz(0., 0., 10.).looking_at(Vec3::ZERO, Vec3::Y)
    ));
}

Note: In addition, in my case, I do force the GPU selection by WGPU to be the integrated GPU with:

        .add_plugins(DefaultPlugins.set(RenderPlugin {
            render_creation: RenderCreation::Automatic(WgpuSettings {
                power_preference: PowerPreference::LowPower,
                ..Default::default()
            }),
            ..Default::default()
        }))

[Henauxg]

Even if the issue is not present when starting the app, here is a way to trigger it:

  // in main
  app .add_systems(Update, update_materials)

// ...

fn update_materials(
    mut meshes: Query<&mut MeshMaterial3d<StandardMaterial>>,
    keys: Res<ButtonInput<KeyCode>>,
    mut materials: ResMut<Assets<StandardMaterial>>,
) {
    if keys.just_pressed(KeyCode::Space) {
        for mut mesh_mat in meshes.iter_mut() {
            mesh_mat.0 = materials.add(Color::srgb(0., 0., 1.));
        }
    }
}

Just repeatedly pressing Space causes on or the other mesh to not render at some point.

[Henauxg]

Disabling the new GPU pre-processing seems to fix the issue:

fn main() {
    let mut app = App::new();

    app.add_plugins(DefaultPlugins)
    .add_systems(Startup, startup)
    .add_systems(Update, update_materials);

    app.sub_app_mut(RenderApp)
        .insert_resource(GpuPreprocessingSupport {
            max_supported_mode: GpuPreprocessingMode::None,
        });

    app.run();
}

But I'm not confident that it's a proper fix. This probably needs to be handled elsewhere.