This crate allows you to define Bevy components direclty inside gltf files and instanciate the components on the Bevy side.
important : the plugin for processing gltf files runs in update , so you cannot use the components directly if you spawn your scene from gltf in setup (the additional components will not show up)
Please see the
* example
* or use bevy_asset_loader for a reliable workflow.
* alternatively, use the bevy_gltf_blueprints crate, build on this crate's features,
that allows you to directly spawn entities from gltf based blueprints.
Here's a minimal usage example:
```toml
[dependencies] bevy="0.11.2" bevygltfcomponents = { version = "0.1.1"}
```
```rust norun //too barebones of an example to be meaningfull, please see https://github.com/kaosat-dev/Blenderbevycomponentsworkflow/examples/basic for a real example fn main() { App::new() .addplugins(DefaultPlugins) .addplugin(ComponentsFromGltfPlugin) .addsystem(spawnlevel) .run(); }
fn spawnlevel(
assetserver: Res
){ if keycode.justpressed(KeyCode::Return) { commands.spawn(SceneBundle { scene: assetserver.load("basic/models/level1.glb#Scene0"), transform: Transform::from_xyz(2.0, 0.0, -5.0), ..Default::default() }); } }
```
Add the following to your [dependencies] section in Cargo.toml:
toml
bevy_gltf_components = "0.1.1"
Or use cargo add:
toml
cargo add bevy_gltf_components
the ordering of systems is very important !
For example to replace your proxy components (stand-in components when you cannot/ do not want to use real components in the gltf file) with actual ones,
which should happen AFTER the components from the gltf files have been injected,
so bevy_gltf_components provides a SystemSet for that purpose:GltfComponentsSet
Typically , the order of systems should be
bevy_gltf_components (GltfComponentsSet::Injection) => replace_proxies
https://github.com/kaosat-dev/Blenderbevycomponents_workflow/tree/main/examples/basic
This crate, all its code, contents & assets is Dual-licensed under either of