basic

Basic bevy_gltf_components + wasm demo

Running this example (non-wasm)

cargo run --features bevy/dynamic_linking

Wasm

Setup

as per the bevy documentation:

rustup target add wasm32-unknown-unknown
cargo install wasm-bindgen-cli

Building this example

navigate to the current folder , and then

cargo build --release --target wasm32-unknown-unknown --target-dir ./target
wasm-bindgen --out-name wasm_example \
  --out-dir ./target/wasm \
  --target web target/wasm32-unknown-unknown/release/bevy_gltf_components_basic_wasm_example.wasm

Running this example

run a web server in the current folder, and navigate to the page, you should see the example in your browser

Additional notes

• You usually define either the Components directly or use Proxy components that get replaced in Bevy systems with the actual Components that you want (usually when for some reason, ie external crates with unregistered components etc) you cannot use the components directly.

Included are the following modules / tools

• process_gltf the most important module: this is the one extracting component information from the gltf files
• insert_dependant_component a small utility to automatically inject components that are dependant on an other component for example an Entity with a Player component should also always have a ShouldBeWithPlayer component you get a warning if you use this though, as I consider this to be stop-gap solution (usually you should have either a bundle, or directly define all needed components)
• camera an example post process/replace proxies plugin, for Camera that also adds CameraTracking functions (to enable a camera to follow an object, ie the player)
• lighting an other example post process/replace proxies plugin for lighting, that toggles shadows, lighting config, etc so that things look closer to the original Blender data
• physics an other example post process/replace proxies plugin for physics, that add Rapier Colliders, Rigidbodies etc . Most of these do not need proxies these days, as the most Rapier components are in the Registry & can be used directly

Feel free to use as you want, rip it appart, use any/all parts that you need !

This tooling and workflow has enabled me to go from a blank Bevy + Blender setup to a working barebones level in very little time (30 minutes or so ?) ! You can then add your own components & systems for your own gameplay very easilly

Information

• the Bevy/ Rust code is here
• the Blender file is here
• I added bevy_editor_pls as a dependency for convenience so you can inspect your level/components