mirror of
https://github.com/bevyengine/bevy
synced 2024-09-20 06:22:01 +00:00
4bf20e7d27
# Objective - Materials should be a more frequent rebind then meshes (due to being able to use a single vertex buffer, such as in #10164) and therefore should be in a higher bind group. --- ## Changelog - For 2d and 3d mesh/material setups (but not UI materials, or other rendering setups such as gizmos, sprites, or text), mesh data is now in bind group 1, and material data is now in bind group 2, which is swapped from how they were before. ## Migration Guide - Custom 2d and 3d mesh/material shaders should now use bind group 2 `@group(2) @binding(x)` for their bound resources, instead of bind group 1. - Many internal pieces of rendering code have changed so that mesh data is now in bind group 1, and material data is now in bind group 2. Semi-custom rendering setups (that don't use the Material or Material2d APIs) should adapt to these changes.
18 lines
331 B
WebGPU Shading Language
18 lines
331 B
WebGPU Shading Language
#import bevy_pbr::forward_io::VertexOutput
|
|
|
|
struct CustomMaterial {
|
|
color: vec4<f32>,
|
|
};
|
|
|
|
@group(2) @binding(0) var<uniform> material: CustomMaterial;
|
|
|
|
@fragment
|
|
fn fragment(
|
|
mesh: VertexOutput,
|
|
) -> @location(0) vec4<f32> {
|
|
#ifdef IS_RED
|
|
return vec4<f32>(1.0, 0.0, 0.0, 1.0);
|
|
#else
|
|
return material.color;
|
|
#endif
|
|
}
|