Awesome. For me, personally - at least a basic understanding of the architecture of the project made with Bevy is very valuable, and I think you are great at explaining it. Subscribed & hit the bell. Thanks a lot for the tutorial!
6:34 I have used despawn_recursive insted of despawn and I don't see any pigs in child hierarchy. Also I find set_parent(pig_parent); method to be more readable than using .with_children(). You can call set_parent after calling spawn() method. Overall very informative tutorial! Thank you very much! If I could suggest you next topic then more tutorials about community plugins (for example physics engine or any other) would really help!
Finally caught up with the tutorial. Do we really need detach children manually? issue #386 of bevy seems fixed it. Children component returns len() = 0 after pig used despawn_recursive on itself. (And Children component does not exist in PigParent before first pig is spawn)
It might be fixed in bevy 11.2. I haven't followed the patches closely. When I first wrote this code the invalid entities still appeared in the inspector
This video required me to loop { watch(); stop(); digest_everything(); resume() }; but it was a joy! Thank you so much for all the efforts you put in your videos.
Something that puzzles me is how could Bevy understand all the systems I add to the App. There is some kind of magic going on.. at least the Rust Analyzer puts a comma after the last argument of the `fn` definition, which is quite unusual for a `fn`. How could the `add_plugins` method accept functions with so different signatures?
I discovered that the comma after the last function argument is valid and something that Rust Analyzer does quite often. Now I imagine there are several implementations of the same function with variable number of arguments. What I think is that those functions accept some kind of generic argument and later rustc translate the actual call using the function with the right number of parameters, but if anyone could clarify this pattern with an in-depth video it would be much appreciated!
I'm blown away by the quality of your tutorial! Very well done!
Wow, greath explanation! i'm awaiting for next episode. Thanks!
Awesome. For me, personally - at least a basic understanding of the architecture of the project made with Bevy is very valuable,
and I think you are great at explaining it. Subscribed & hit the bell. Thanks a lot for the tutorial!
6:34 I have used despawn_recursive insted of despawn and I don't see any pigs in child hierarchy. Also I find set_parent(pig_parent); method to be more readable than using .with_children(). You can call set_parent after calling spawn() method.
Overall very informative tutorial! Thank you very much!
If I could suggest you next topic then more tutorials about community plugins (for example physics engine or any other) would really help!
Finally caught up with the tutorial. Do we really need detach children manually? issue #386 of bevy seems fixed it. Children component returns len() = 0 after pig used despawn_recursive on itself. (And Children component does not exist in PigParent before first pig is spawn)
It might be fixed in bevy 11.2. I haven't followed the patches closely. When I first wrote this code the invalid entities still appeared in the inspector
@@logicprojects You need to use commands.entity(slime_entity).despawn_recursive();
Seriously these tutorials are incredible please dont stop
This video required me to loop { watch(); stop(); digest_everything(); resume() }; but it was a joy! Thank you so much for all the efforts you put in your videos.
Part 4!
Thanks so much for making these tutorials! Currently learning rust with the goal of using it with bevy and these have been great!
Oh I have been waiting so long for the part 3
Yeah sorry for the delays, life is always busy
Thank you for making such a nice educational video
Excellent series, great work, looking forward to the next part.
Cool🎉
Something that puzzles me is how could Bevy understand all the systems I add to the App. There is some kind of magic going on.. at least the Rust Analyzer puts a comma after the last argument of the `fn` definition, which is quite unusual for a `fn`. How could the `add_plugins` method accept functions with so different signatures?
I discovered that the comma after the last function argument is valid and something that Rust Analyzer does quite often. Now I imagine there are several implementations of the same function with variable number of arguments. What I think is that those functions accept some kind of generic argument and later rustc translate the actual call using the function with the right number of parameters, but if anyone could clarify this pattern with an in-depth video it would be much appreciated!
Fantastic series! Can't wait for the next part 🙏
I'm eager to learn How Bevy ECS works under the hood. Humble request to you to make a video explanation of it.
Watching your second tutorial as I write this comment....happy I can continue on!
hey this is really cool, are you planning on using bevy_rapier for physics? im hoping to make a platformer, and i am following along to learn bevy
Thank you! Very good explanation
Awesome tutorial on plugins! You do a great job explaining and leave just enough out for me to figure out.
Thank you for making the video the content is very good.
very useful. Thank you very much
thank you! very informative... I feel trouble when adding a loading screen when the code is executed especially on the wasm side. ;=(