mirror of
https://github.com/kaosat-dev/Blender_bevy_components_workflow.git
synced 2024-11-22 20:00:53 +00:00
9f21df035b
* closes #80 * preliminary work for further asset management from the Blender side without needing additional dependencies & boilerplate on the Bevy side * feat(auto_export): * now injecting list/tree of sub blueprints to main scenes/levels & blueprints * made blueprints/asset list conditional on NOT legacy mode * feat(gltf_blueprints): * basics of dynamic loading of sub_blueprints * added same kind of logic to the loading of material files * also made a more generic variant of the BlueprintAssetLoadTracker * added gltf file path for more informative error in case a gltf is missing * refactor(): * made the various gltf assets loaded by bevy_asset_loader optional (to handle the case where they are not present) * updated all examples accordingly * chore(crates): fixed links, slight tweaks, bumped versions |
||
|---|---|---|
| .. | ||
| 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.