TBF a website/stock issue is what it is and happens everywhere. They contacted you and gave you your options, that's basically all you can expect from any company.

I really love your content. I'm going to out myself for being a scrub... but can you please leave the code up just a little longer. There are a few transitions in this video where if you're coding along you have a split second to pause the video and see the code. Keep up the good work! I appreciate the thorough hands on break downs.

These are great, I'm really enjoying this project. You probably have realized this already, but the ball is spinning because the platform is moving at the instant of the collision. Because the engine gives both rigid bodies friction, the motion of the platform imparts a torque on the ball, causing it to spin. (By accident) I managed to hit the spinning ball so that on the next wall collision it stopped spinning and the motion became purely vertical, so the game would have to be manually reset. Adding Friction { coefficient: 0.0, combine_rule: CoefficientCombineRule::Min } to the ball fixed that.

This is great! I started following the channel after your reddit post about the first Pong episode. Very educational! But I find the collision detection part here a little confusing 😅 I understand how the Player enum is used to decide which one of the borders the ball is colliding with, but if you wanted to detect collision between the ball and ANY border, how would you do that? How would you type you `goles` Query param? Or would you in that case not need to have `goles` as a param at all? I tested this with having no other if-checks inside `for hit in ball.iter()`, but then it seems to also detect the ball colliding with itself? 🤔

16:55 that's a little weird. So a coëfficient of restitution is not actually something that an object in the real world has, it's actually the relationship between 2 objects but obviously some objects are bouncier than others but the coëfficient is just the relationship between it and another object - the coëfficient might be 0.9 against a hard surface and 0.3 against something soft (or even it could be *functionally* 1.5 if mechanically pushed like in a pinball machine, it's not actually 1.5 nothing is 1.5 but if you were to have it in a game you'd use 1.5). However the way I've previously combined coëfficients is the geometric mean [sqrt(coefficient_1 * coefficient_2)], which is close to average when the numbers are closer 0.9 and 0.8 would be 0.849 compared to the average 0.85, but biased towards the low end when more different 0.9 and 0.1 would be 0.3 rather than 0.5 (additionally if a 0.9 ball bounces of a perfectly inelastic wall of 0 then the result is 0 because the wall is perfectly inelastic); so it's strange that they don't provide that as an option as it's not unusual (I'm not the first to do it this way). I tried to clone the project to add GeometricMean as an option but I can't get the dependencies to work as they're doing some kind of fuckery with them, I want GeometricMean as I know how that reacts and this is why I always end up just making my own stuff rather than relying on others. I can't find what `crate::math::Real` actually refers to for sure to know if I can just `.sqrt()` (I'm pretty sure it's just an f32 and so can) it and I can't just guess and give it to others. I don't know how people can contribute to OSS, I want to, but it always feels so punishing; once again resorting to just filing an issue - I have filed an issue so hopefully they'll add it, it's a very simple addition. However the game I have in mind I'm probably going to roll my own physics as it can be reduced down to just what I need.

People have mentioned it being fast paced, in the future maybe include an unlisted video with nothing sped up. It shouldn’t require as much work although if you’re speeding up segments progressively while editing then it would require changing how you do it. Also people should generally watch a tutorial through once and then follow along, you want to know what the end result is, and so if you make the default longer then it's harder to watch it through first. This video has come at a perfect time for me as I last touched Bevy in 0.11 and I’m aware that a lot of things have changed. Thank you for this, the video is fine for me but I think only because I have a lot of Rust knowledge and prior Bevy knowledge

Great tutorial!

That was my PR, yayy! Nice. Love the content.

Thanks for making this simple tutorial. It was a bit fast paced, so I used pause and rewind a fair bit as I typed the code. Fortunately I now have Rust and a little Bevy experience so it all made sense to me. This is a great starting point. I am interested in simplifying the hit test code, perhaps with the Bevy collision function.

Love this!

I like this format) would like to see more in this style

Nothing like an event. Just a resource. Even a singleton to be clear. And you have to relay on the screen update rate + organize the systems execution so that it would read the event data in time. This is an anti-event at best ) I thought that I could connect systems to the event so it will run them once it will be broadcasted.

Very helpful overview, thanks for making this video!

I'm rather confused- why use bevy to track state? It's trivial to have an entity that tracks state.

Please keep this tutorial going. Would love to see some card system with a nice hand visualization

Bro please slower... I've never touched Bevy or Rust in my life, and you're rushing as hell ;-; to much speeding up

Thanks for making this game for beginners, there's not many videos like this for beginners on youtube. Very helpful, thanks again

Which Operating System is Best for Rust ? linux or Windows ?

LOL, I always thought you had to install Visual Studio to have libraries and a linker for Rust on Windows (I already had it installed when I first installed Rust)

Can you do a separate video for 2d and features that are agnostic?

Great video! Plus, a gentle reminder to do chapters :-)

now you have to do this again for version 0.14 :D

old

Did you compare the release versions? I think comparing debug versions can lead to incorrect results. Just because one debug version is faster than the other does not necessarily mean the same is true for the release version.

Bevy has been amazing. It works great with robotics too

bevy 0.13 in debug: ~22k entities at 27fps with 86 rings. bevy 0.13 release: ~263k entities at ~25 fps with 296 rings.. Specs: CPU: Intel(R) Core(TM) i5-8400 @ 2.8GHz, 6 cores GPU: Intel(R) UHD Graphics 630 (integrated) 12 GB ram (idk if this matters that much) this is crazy.

This made me want to give bevy another shot :) nice work 👍

Cool showcase, however, I felt a bit lost as I asked myself all the video what a Ring supposed to be, as you showed a hexagonal procedurally generated map :D

Cool right

What's the red inline stuff you have going? 7:50 I know it's not copilot (grey) and my rust-analyzer is only in the console..

Thanks for mentioning sparse sets, I maintain a C# ECS called fennecs, and i am always on the lookout for better data structures for certain archetypes. I do think that I already use a sparse set-like structure as the "Meta"-Table for my entities, but I had not yet considered using it as the backing datatype for the storages that comprise each archetype. I'm not sure it's suitable. :)

Hi

ILOVEyou

How to do that you can interact with an asset.

Nice work my man!

oh my fucking god thats a bigggggg octopus

As a rule you don't need a heated box to print PETG. ABS, yes. But not PETG.

I'm watching this video 9 months after upload and belly still does not have a crate. I'm perplexed why such a feature rich library isn't available as a crate from cargo? Is it complicated to create a crate? Surely it's much easier than what jkb0o as accomplished with belly! I hope that one day belly will be adopted as the official method to create ui in bevy and become a part of the engine.

Insanely helpful, especially the linked videos. It's one thing to do all the math for vectors and matricies in school, it's another thing entirely to apply it to something real.

I've been getting into game dev with Bevy recently, and I think this would be great for making a Minecraft-like registry system for items and whatever else. I think its be neat for registered content to provide their own callback systems, which run under different circumstances (like items getting used).