mirror of
https://github.com/kaosat-dev/Blender_bevy_components_workflow.git
synced 2024-12-22 23:54:10 +00:00
09d1218942
* fixed & improved the Blenvy crate README * make a few things conditional on whether hot reload is enabled or not * cleaned up very verbose debug messages * a few renames & coherency pass * cleanups cleanups, cleanups ! |
||
|---|---|---|
| .. | ||
| art | ||
| assets | ||
| src | ||
| Cargo.toml | ||
| index.html | ||
| README.md | ||
Basic physics example/demo
This example showcases various 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 componentsthat 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.