really nice rundown of an interesting crate! i think the reason x*x+y*y >= d*d is used over distance >= required_distance is because getting the length of a vector requires a square root operation, which is (relatively) slow, but it can be avoided by simply comparing the squares of the length (i even think that bevy has a built-in Vec3::distance_squared function). in this example (and most games i'd assume), the performance hit is mostly acceptable, but if this system had to run on a huge amount of entities (i think we're talking on the scale of millions, but don't hold me to that), it could be a reasonably big gain in performance to avoid the square root operation
I'd love to see you tackle implementing behaviour trees in a bevy game at some point. I've looked at Bonsai enough to realize my rust chops and bevy understanding aren't nearly good enough yet to pull it off.
Hey Chris, just want to say I love your stuff! Have you considered making a patreon, a support button for youtube or github? I may buy your course too, but I want to contribute to open information. Also, have you looked at path finding in Bevy yet?
hey! glad you're enjoying it! I've considered it and have said "no, for now" to github and patreon. I haven't seriously considered RU-vid. Mostly because maintaining a set of tiers and rewards on a platform that takes significant cuts from that money doesn't seem worth it at the moment. Rust Adventure is hooked up to Stripe, so I basically pay the processing fees for a Rust Adventure subscription and I don't have to worry about getting locked out of Patreon or what their company does. The Rust Adventure income supports the work I do on RU-vid, as I see the RU-vid videos as extremely early-phase coursework: It's me sharing my research and learning on different topics in a more raw format than the Rust Adventure workshops, which are more on the well researched and tested end of the spectrum. The course, fwiw, is all hosted in open source repos in the Rust Adventure GitHub org (github.com/orgs/rust-adventure/repositories?type=source) and the content is accessible by URL on the site as blog posts. The things that are locked behind paying tend to be more costly things (like serving video, or compiling Rust code) or features that benefit from having an account. I'm very pro "having the information accessible", so I draw the lines there with a good deal of thought beforehand. --- I haven't done any videos on path finding yet, although I did see a new crate pop up recently that could be interesting to look into. I'd need to make an example for the video.
