mediapipe VS bevy

Medipaipe library link: https://mediapipe.dev/

If you're looking for the differences in terms of how inference is done, I recommend you take a look at MediaPipe's source code. MediaPipe doesn't use raw code, but uses a "graph" instead (eg. pose_landmark_cpu.pbtxt), which can be visualised using MediaPipe Viz. I also used axinc-ai/ailia-models as the base (preprocessing, inference, postprocessing, etc...) which I further built upon (keypoint refinement, roi from keypoints, filtering / smoothing, etc...)

I thought of doing that but unfortunately medipipe requires a RGB input and performs better with it more on that here

You might want to check out https://github.com/open-mmlab/mmhuman3d and https://github.com/google/mediapipe

This architecture was also used in the link referenced when bringing up alternative implementations:

https://github.com/google/mediapipe/issues/877#issuecomment-...

Game engines (Bevy, Fyrox)

After the quick start there isn't as much documentation yet as one might hope, but I find you can learn to do just about anything you need by reading the extensive examples. There are tons of them in GitHub of which a subset have been turned into interactive WebGL apps on the main site.

well, wasm threads are weird for some reason. Issues like https://github.com/bevyengine/bevy/issues/4078 remind me that wasm is still a moving target.

There are some examples here: https://github.com/bevyengine/bevy/tree/main/examples/animation

Rust is much newer a language than Java. Give it time. There is clearly industry interest: check out the sponsors list on bevyengine.org.

Binaries file-sizes in debug are just insanely big, a Hello World will be around ~4MB, an empty Bevy project will be around ~600MB.

$ git clone https://github.com/bevyengine/bevy.git ; cd bevy $ cargo install --locked cargo-public-api $ cargo public-api -ss -p bevy_utils diff v0.9.1..v0.10.0 Removed items from the public API ================================= (none) Changed items in the public API =============================== (none) Added items to the public API ============================= +pub use bevy_utils::<> +pub use bevy_utils::petgraph +pub use bevy_utils::thiserror +pub fn bevy_utils::synccell::SyncCell::read(&self) -> &T where T: core::marker::Sync +pub mod bevy_utils::syncunsafecell +pub use bevy_utils::syncunsafecell::UnsafeCell +#[repr(transparent)] pub struct bevy_utils::syncunsafecell::SyncUnsafeCell +impl bevy_utils::syncunsafecell::SyncUnsafeCell +pub fn bevy_utils::syncunsafecell::SyncUnsafeCell::from_mut(t: &mut T) -> &bevy_utils::syncunsafecell::SyncUnsafeCell +pub const fn bevy_utils::syncunsafecell::SyncUnsafeCell::get(&self) -> *mut T +pub fn bevy_utils::syncunsafecell::SyncUnsafeCell::get_mut(&mut self) -> &mut T +pub const fn bevy_utils::syncunsafecell::SyncUnsafeCell::raw_get(this: *const Self) -> *mut T ...

Firstly, Bevy has an internal crate called bevy_reflect, and it can handle most of the things you would usually use reflection for. For example, https://github.com/jakobhellermann/bevy-inspector-egui exists which uses Bevy's internal reflect derive to make the values available via an egui-based UI. Changing simple values (like an f32, or a boolean) can be done at runtime, and if I remember correctly all you actually need to do is to add the plugin. Taking a look at the README https://github.com/bevyengine/bevy/tree/main/crates/bevy_reflect you can "patch" types with new values, iterate over struct fields, serialize + deserialize, and generally do stuff like that.

It doesn't work currently. The only problem is that plugin initialization must be asynchronous, so you have to pass control back to the browser to allow it to initialize the WebGPU api properly[1]. I hacked async plugin initialization into a fork for Bevy 0.8[2], but I never got it to 100% work because Chrome had already moved onto a newer WGSL syntax. In theory if you do the same changes for 0.10 as I did for 0.8 it should allow WebGPU to work (and I plan on doing this in the next couple days).

[1]https://github.com/bevyengine/bevy/discussions/3239