Video

in bevy 0.14.1 Color::rgb(red: u8, green: u8, blue: u8) -> Color is deprecated, use Color::srgb(red: f32, green: f32, blue: f32) -> Color instead

brilliant! very clever explanations, congrats

Thank you @Zymartu! Very very clean explanations. I've learned a LOT about ECS desig pattern!!

Hey keep em coming! Your videos are great

Awesome video. keep this series going!

Great vid!, fyi you have a small spelling error in the thumbnail: Pratice

Awesome stuff.

If you are using Bevy >= 0.13 then add_state is renamed to init_state.

Your vids are 🦆-ing awesome. Very easy to understand and helpful af.

Awesome tutorial, thanks a lot dude :D

app.add_state() has been renamed to app.init_state() since Bevy 0.13

Awesome series! I appreciate the effort you put in to create this gem. Hopefully you'll find time and energy to continue it. Good luck with your game-development!

Haha - love the graphic explaining the flush points @7:00 :D Great video - love this series! I learn so much since you have an excellent teaching style!

What a joy to code along. Feels very structured and I often already (kinda) know what to do next. Very well paced. Edit: Just finished this episode. I think the game will crash if the spaceship goes beyond DESPAWN_DISTANCE.

Holy smokes - you are a really talented tutor! Your series is _very_ easy to follow along and you already squashed some brain-bugs I had due to a lack of understanding (looking_at you, camera) ;-)

That's a _very_ nice introduction! Well done 🎉

This one showed how to use events like events and not like some resource. So you can make system to be run only if event was sent!

It is so nice and to the point, please create additional videos ?

Great tutorials! Hope to see new episodes soon😅

I hope you eventually find the time to continue this series. It's been a great help and really sets the standard for bevy tutorials.

This series has been a HUGE help. Thank you so much!

I love it!!

This is great - is there per chance a written version of this tutorial series ?

when will have a further tutorials especially the 0.13 have released,you are the only recent video so far,another are too old

Great tutorial so far. But I have one little problem: I can't find the Asteroid.glb file in the linked asset bundle. Does anyone know a fitting alternative?

I don't see how these loosey-goosey labels are in the Spirit of Rust. These appear like a very vague (if flexible!) and unreliable way to maintain your system order. But spotting conflicts or reasons why a system runs too late appears difficult.

Not a fan of Bevy, nor Rust, but this is still a good series. (I'm here to spy, I maintain an ECS for C# :-))

In Bevy 0.13, add_state is renamed to init_state

Super useful series of tutorials ! About 38:06 since the spaceship is currently also targeted by the despawn query, making the app panic when it gets too far away off the center of the screen, and that could be fixed by just targeting the asteroids using "With<Asteroid>" in that system or even better make a component to tag every despawnable entity and target that like "With<Despawnable>" right ?

This tutorial was awesome. Really appreciate it, thank you!

Thought we were checking different documents of bevy-render as they are different. And yes, you were checking bevy_render 0.11.3, not as the title suggested 0.12.

The Space keypress has a Velocity::new(-transform.forward() * ... if you get Direction3d and not a Vec3 you can deref the Direction3d to a vec3

How is your game development going?

Amazing. Hope you will find capacity to record more videos any time soon

The only improvement for this tutorial series that I can think of is to change the default fps to 30 max. That way I can watch the videos on any older hardware and even on my big TV in high resolution (while following the tutorial on my laptop). Anything over 30fps does not make sense on youtube if there are no fast movements. On CZcams, high resolution is almost always more important than framerate (and sound is often more important than video quality but you are already doing well there).

I am really hyped to find a useful tutorial series about bevy engine. Thanks for the good work.

I’ve been writing notes and following along. Thank you for this series, though I’ve been learning rust, the abstractions in bevy is tough to wrap your head around. The documentation is something I haven’t quite figured out so thank you. For myself and others, bevy is a great way to learn rust. This is keeping me engaged in my rust journey

wonderful tutorial series, and i hope your game is coming along nicely too!

please finish the tutorial, you have covered almost all basics of the engine and you have done a great job

7:47 bug fuel right there

Thanks for your effort, a great way to start mit Rust and Bevy. I'm just wondering why you use "... in query.iter_mut()" here, because only the position is mutating in my eyes not the query itself.

bevy 0.13 is out, redo the whole series

This explains ECS very well. Thank you! Got me subscribed.

Is it a Bevy 0.13. issue? I don't see the model, just the background.

Please back to your videos, such a great start!

I had to add a build.rs script (in root, not src) to make the assets copy into the target directory. Here's my code: use std::{ env, fs, path::{Path, PathBuf}, }; /// A helper function for recursively copying a directory. fn copy_dir<P, Q>(from: P, to: Q) where P: AsRef<Path>, Q: AsRef<Path>, { let to = to.as_ref().to_path_buf(); for path in fs::read_dir(from).unwrap() { let path = path.unwrap().path(); let to = to.clone().join(path.file_name().unwrap()); if path.is_file() { fs::copy(&path, to).unwrap(); } else if path.is_dir() { if !to.exists() { fs::create_dir(&to).unwrap(); } copy_dir(&path, to); } else { /* Skip other content */ } } } fn copy_dir_to_output(source_dir: &str) { // Command sent to cargo println!("cargo::rerun-if-changed={}", source_dir); // Request the output directory let out = env::var("PROFILE").unwrap(); let out = PathBuf::from(format!("target/{}/{}", out, source_dir)); // If it is already in the output directory, delete it and start over if out.exists() { fs::remove_dir_all(&out).unwrap(); } // Create the out directory fs::create_dir(&out).unwrap(); // Copy the directory copy_dir(source_dir, &out); } fn main() { copy_dir_to_output("assets"); }

Worth noting that the Asteroid and Missile assets no longer exist in the linked asset pack, I'm just shooting astronauts at planets for now 😆

Moves so fast (and text so small) that I can't read WTF you're doing.

I am very new to rust and data oriented programing. I would like to know why use these simple structs like // struct Acceleration { value: Vec3 } //, that has a single propriety? Why not a tuple? Something like this // struct Acceleration(Vec3) //, any one knows if there is an advantage on any of these aproachs? My JS mind thinks the tuple version would de more memory compact and have one less dereference for reading/writing its content.

Very good intruduction