Blender_bevy_components_wor.../examples/relations
2024-08-22 18:09:18 +02:00
..
art faking named entity in type registry 2024-08-22 18:09:18 +02:00
assets faking named entity in type registry 2024-08-22 18:09:18 +02:00
src faking named entity in type registry 2024-08-22 18:09:18 +02:00
Cargo.toml Add relations example 2024-08-22 18:09:17 +02:00
README.md Add relations example 2024-08-22 18:09:17 +02:00

Basic relations example/demo

This example showcases how to refer to another Entity inside Bevy components added to objects/ blueprints/ meshes and materials extracted from the gltf files

Running this example

cargo run --features bevy/dynamic_linking

Wasm instructions

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_blueprints_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.