"the trait bound (bevy::DefaultPlugins, ShaderUtilsPlugin, PlayerPlugin, camera::CameraPlugin, WorldPlugin, bevy_third_person_camera::ThirdPersonCameraPlugin, bevy_inspector_egui::quick::WorldInspectorPlugin, bevy::prelude::MaterialPlugin<ExtendedMaterial<bevy::prelude::StandardMaterial, ExtensionTest>>): bevy_app::plugin::sealed::Plugins<_> is not satisfied
perhaps two different versions of crate bevy_app are being used?"
is being reported whenever I add the ShaderUtilsPlugin, this maybe be my fault as I am new to bevy and rust. I'm using bevy 0.13.1.

Much thanks Maebh!

Rust 1.74 allows specifying lints in a workspace-level Cargo.toml.

Common lints that Bevy applications trigger in clippy but are typically false flags are:

• clippy::type_complexity
• clippy::too_many_arguments

Lints can be defined at the workspace Cargo.toml.

[workspace]
members = ["examples/*"]
resolver = "2"

[workspace.lints.clippy]
type_complexity = "allow"
too_many_arguments = "allow"

Each package needs this in Cargo.toml.

[lints]
workspace = true

• 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.

Migrating from 0.12 to 0.13

There are a lot of examples and it might be simpler to get them to work with Bevy 0.11 one by one. This issue is regarding one of the coolest, the shield-with-depth example.

It depends on

• bevy_basic_camera
• bevy_prepass_debug
• bevy_shader_utils

So in total four crates need to be touched. We could migrate them to get to work with Bevy 0.11 and any other improvements such as enabling prepass motion vector would be left as future enhancements.

error[E0609]: no field time on type &mut CustomMaterial
--> libs\bevy_shader_utils\examples\voronoise-pan.rs:62:20
|
62 | material.1.time =
| ^^^^ unknown field
|
= note: available fields are: color

error[E0599]: no method named seconds_since_startup found for struct bevy::prelude::Res<'_, bevy::prelude::Time> in the current scope
--> libs\bevy_shader_utils\examples\voronoise-pan.rs:63:18
|
63 | time.seconds_since_startup() as f32;
| ^^^^^^^^^^^^^^^^^^^^^ method not found in Res<'_, Time>

error[E0308]: mismatched types
--> libs\bevy_shader_utils\examples\voronoise-pan.rs:85:19
|
85 | .push("VERTEX_UVS".to_string());
| ---- ^^^^^^^^^^^^^^^^^^^^^^^^ expected ShaderDefVal, found String
| |
| arguments to this method are incorrect
|
note: method defined here
--> C:\Users\Administrator.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\alloc\src\vec\mod.rs:1836:12
|
1836 | pub fn push(&mut self, value: T) {
| ^^^^
help: call Into::into on this expression to convert std::string::String into ShaderDefVal
|
85 | .push("VERTEX_UVS".to_string().into());
| +++++++

error[E0308]: mismatched types
--> libs\bevy_shader_utils\examples\voronoise-pan.rs:88:35
|
88 | fragment.shader_defs.push("VERTEX_UVS".to_string());
| ---- ^^^^^^^^^^^^^^^^^^^^^^^^ expected ShaderDefVal, found String
| |
| arguments to this method are incorrect
|
note: method defined here
--> C:\Users\Administrator.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\alloc\src\vec\mod.rs:1836:12
|
1836 | pub fn push(&mut self, value: T) {
| ^^^^
help: call Into::into on this expression to convert std::string::String into ShaderDefVal
|
88 | fragment.shader_defs.push("VERTEX_UVS".to_string().into());
| +++++++

This seems like a great little resource for Bevy shaders. Unfortunately, there's no license specified, so it's not clear whether the code can actually be used or redistributed.

There seems to be an issue with the Perlin 3D implementation.
Passing the following data world_position.xyz * 5.0

• Simplex 3D:
  
• Perlin 3D:
  

It seems to have something to do with the algorithm only using the decimal part on one of the parameters, the cube has length of 1, notice how I multiplied the input by 5 and we see 5 stripes in one of the directions...

https://extremelearning.com.au/how-to-evenly-distribute-points-on-a-sphere-more-effectively-than-the-canonical-fibonacci-lattice/

Assets v2 introduced some new embedded asset features. Should bevy_shader_utils switch?

https://bevyengine.org/news/bevy-0-12/#embedded-assets

it was an accident and is already fixed on main, but we'll have to wait for 0.13.1 to upgrade the examples here that use time in a vertex shader, or we'll have to use a main commit rev.

fix is 12032 on the bevy repo