mirror of
https://github.com/kaosat-dev/Blender_bevy_components_workflow.git
synced 2024-12-22 23:54:10 +00:00
6dde9823ed
* added logic to track spawning of sub blueprints * added ability to determine when a blueprint instance is truly ready (aka all its assets have been loaded, blueprint scene & sub scenes spawned & processed etc) * reworked spawning steps for more determinism & reliability * no more "seperate" spawning post process * lots of related changes * still messy but functional |
||
|---|---|---|
| .. | ||
| art | ||
| assets | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
Bevy registry export example/demo
This example showcases
- the use of the bevy_registry_export crate to extract all components & types information into a json file.
- That file is then used by the Blender addon to create Uis for each component, to be able to add & edit Bevy components easilly in Blender !
Running this example
cargo run --features bevy/dynamic_linking
Running the example also regenerates the registry.json file.