Видео

Another approach is to create macros, they will remove the boilerplate and keep all the benefits like parallel processing

so... when can we make Elden Ring with bevy...

Uh, oh. Rust asynch. Truly cursed.

i immediately recognized the control scheme and was ready to ask lol

What did you use for SpriteSheet creation? It's about the software from the start of the video

Great channel 🎉

Cool🎉

Great 🎉

Very cool review 🎉

Great bevy content, keep it up

very nice, thanks :D

I'm blown away by the quality of your tutorial! Very well done!

Rogue is rogue. Rouge is makeup.

Can the client be in typescript?

- Structs don't require being in it's own file of the same name, it's perfectly acceptable being in a shared file like you have here as long as it makes sense organizationally. Personally, having a single file to dump components into that don't relate sounds like a nightmare to extend and refactor.

It was just a couple lines of code, but making my pixel pigs run on the screen made me happy! Thanks for the tutorial!

This is a fantastic overview of the render pipeline, and how all the key components work together to form a whole. Would really love to see a deeper dive into the optimisations - like how batching works - to get an even more complete understanding of whats happening under the hood!

Some friendly corrections: RefCell is not a reference counted pointer, it's actually a type that owns and lets you borrow the contents at runtime (Rc is the Reference Counted pointer). And Arc is not an asynchronous pointer, it's an *atomic* reference counted pointer.

im really considering moving to Bevy, im just a bit unsure since the 3D front seems a bit underdeveloped? i come from the source engine where the world was done in their hammer editor and the logic in C++ / visual studio, im slightly confused on how to do it with Bevy since it doesn't have a world editor / mapping tool. i also found godot but i dont like the non-compiled code since people can just decompile your entire game and steal or change stuff, ive used unreal in the past but i dont want all the bloat they put in nor deal with epics licenses, unity is similar to godot, its C# so its not that hard to decompile. i love that Bevy just uses rust and dont mix things like unreal does with its blueprints/C++ or unity with their visual scripting / js / cs etc. But I do miss visual studio (not code, the other one) and am a bit confused with rust coming from cpp / cs😅 (especially when it comes to setting up the IDE) but it dont seem to bad tbh.

2:16 Don't you just love when you don't even start coding and you're already stuck X'D. Hello world won't build after adding bevy (identical toml file) due to some unresolved import with ItemFn and ItemTrait in bevy_derive-0.6.0/src/bevy_main.rs.

Amazing video! More of this please.

Hi there, I'm trying to rebuild this in bevy 0.13, but couldn't get the PickSelection is_selected (which i believe is the equivalent of Selection selected()) to change to 'true' when click on one of the TowerType.

11:25 quick update: bevy 0.13+ uses ButtonInput instead of Input also KeyCode::W -> KeyCode::KeyW

Very helpful tutorial! Can't wait to see bevy community grow larger and have such good tutorials!

So many ads

Thank you so much for your videos!

I'm following this tutorial with Bevy 0.13, and I have to say, a lot has changed since then. It's a bit troublesome to find the correct way to do things, but I managed to find the right solutions with a lot of trial and error!

Amazing!

with Bevy 0.13 WindowPlugin needs to be used instead of WindowDescriptor docs.rs/bevy/latest/src/scale_factor_override/scale_factor_override.rs.html#10

on windows you can still get fast build. add opt mentioned in the video and in the terminal type: cargo run --features bevy/dynamic_linking subscribed :)

Any confused about why you're getting an error for the 'Input' resource. In Bevy 0.13, the Input resource was renamed to `ButtonInput`. Additionally, instead of the KeyCode being `KeyCode::W` it is now `KeyCode::KeyW`

One objection I have the bsn! macro is that it looks like declarative code (e.g., maybe functional code that would be returning scene info), but it's actually imperative code that's modifying things in the background. That feels very unrustlike. I've also had nothing but negative experiences with embedding one language into another. That tends to lead to abominations like PHP.

Remember when "roguelike" wasn't more or less a synonym for "game?"

Good video, but that dark-grey-on-black syntax highlighting is a bit of a problem.

TOMATOE OF DESTRUCITON!!!!!

quick question as a noob: why 9:16 asser_server in the fn setup() does not require mut? Is it because Res<AssetServer> uses internal mutability?

I have to install bevy via command line. But there is no video about it. Do you know how to do it?

5:23 no need for nested for loop there. only one loop is enough let direction = { let mut min_distance = MAX; let mut transform = None; for target in &targets{ let distance = Vec3::distance(bullet_spawn, target.translation()); if distance < min_distance{ min_distance = distance; transform = Some(target.translation() - bullet_spawn); } }; transform };

thank you 😊

people who are less intelligent would not understand even a sentence in this tutorial

Does anyone know, or can point me in the direction of how to do ui in bevy 0.12? Thanks :)

Could you not have merged the voxels even further into bigger blocks long as they had the same consistent texture that could have been calculated and repeated? Especially when beyond any possible interactions, it seems like this might be a good strategy. I have only played with voxels limited number of times because I don't really do gamedev, but I find the voxel to be interesting problem; and I helped a friend make a tactics game once and ran into many of the voxel problems then; and ever since have found the entire subject pretty interesting. There are a lot of overlapping principles with graph databases which is why I think another modern way to store this type of data is the oct-trie previously quad-trie. Also are you only rendering just the frustum (the presumably visible trapezoid if I remember my terms correctly). By combining the server and client you came across the essential design to any p2p protocol; there is a lot more obviously like peer discovery, and message passing, but combining server and client functionality together is the first step. I did it recently with XMPP to create a decentralized XMPP client (node).

I'm hoping to play with bsn soon. An ergonomic was of representing changes over time in both UI and 3D scene component values will be very valuable.

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!

Thank you for this overview and tutorial!

"bevy e-gooey" (say it properly brickass)

is this not like the ascii from DF? lol

These are pretty cool can you do these for newer versions of bevy? They're probably less work since you don't need to go editing and such.

why do they call them von neumann neighbors when they could be called rook neighbors

"Im probably making an aggressively inaccessible, unplayable, and unfun game" Good!! This is genuinely very good, and you should follow that path. Lots of great ideas are locked behind doors that are "unfun" or "completely incomprehensible to most players".