mirror of
https://github.com/kaosat-dev/Blender_bevy_components_workflow.git
synced 2024-12-22 15:44:11 +00:00
09915f521d
* chore(crates): updated crates to Bevy 0.13 * updated deps * updated / changed code where relevant * updated README files * bumped version numbers for upcoming release * updated rust-toolchain * updated assets where relevant * closes #132 * feat(bevy_gltf_components): * added GltfProcessed flag component to improve performance of iteration over added<gltfExtras> * closes #144 * light & shadow processing is now integrated, to match lights coming from Blender: you can now control whether lights cast shadows, the cascade resolution , background color etc from Blender * closes #155 * feat(bevy_registry_export): added boilerplate to make registry path relative to assets folder * closes #137 * feat(tools): added boilerplate for internal tools * clean zip file generator for blender add-on releases * example gltf file generator * feat(lighting): added components, exporter support & testing for blender-configurable shadows * added BlenderLightShadows component to bevy_gltf_components * added writing shadow information to gltf_auto_export * updated tests * closes #157 Co-authored-by: Jan Hohenheim <jan@hohenheim.ch> |
||
|---|---|---|
| .. | ||
| assets | ||
| src | ||
| Cargo.toml | ||
| expected_screenshot.png | ||
| 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.