mirror of
https://github.com/kaosat-dev/Blender_bevy_components_workflow.git
synced 2024-12-22 23:54:10 +00:00
bce6d43c50
* fixed bad default path for library * added missing ComponentsFromGltfPlugin which causes the blueprint plugin not to work as expected if ComponentsFromGltfPlugin is not added elsewhere * all info! calls are now debug! for a less spammy debugging experience * refactor(examples:advanced): * removed ComponentsFromGltfPlugin as that is now included directly in the blueprints plugin * moved all physics (rapier) related code to the core/physics module |
||
|---|---|---|
| .. | ||
| assets | ||
| core | ||
| game | ||
| main.rs | ||
| README.md | ||
| state.rs | ||
| test_components.rs | ||
| TODO.md | ||
Workflow with blender / demo information
This example, is actually closer to a boilerplate + tooling showcases how to use a minimalistic Blender (gltf) centric workflow for Bevy, ie defining entites & their components inside Blender using Blender's objects custom properties. Aka "Blender as editor for Bevy"
It also allows you to setup 'blueprints' in Blender by using collections (the recomended way to go most of the time), or directly on single use objects .
Running this example
cargo run --example advanced --features bevy/dynamic_linking
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. - this example contains code for future features, not finished yet ! please disregard anything related to saving & loading