7ffcd55f5d
* fix(gltf_auto_export): added fix for correct "deep-copying" of objects & hierarchy so that animated
meshes & nested hierarchies get exported correctly
* test(gltf_auto_export):
* added visual testing to check for overall regression :
* added screenshoting in bevy app
* added visual compare with reference screenshot on python side
* added testing of correct export of animated models
* added testing of correct export of empties
* added testing of correct export of nested hierarchies
* added testing of correct export of blueprints, with & without components etc
* fixes #147
|
||
|---|---|---|
| .. | ||
| assets | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
| 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.