Blender_bevy_components_wor.../testing/bevy_example
Mark Moissette 7ffcd55f5d
fix(gltf_auto_export): fix animation export (#148)
* 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
2024-02-29 15:27:02 +01:00
..
assets fix(gltf_auto_export): fix animation export (#148) 2024-02-29 15:27:02 +01:00
src fix(gltf_auto_export): fix animation export (#148) 2024-02-29 15:27:02 +01:00
Cargo.toml feat(gltf_auto_export): component filtering for exports, bug-fixes and tests(#143) 2024-02-27 00:12:14 +01:00
expected_screenshot.png fix(gltf_auto_export): fix animation export (#148) 2024-02-29 15:27:02 +01:00
README.md feat(gltf_auto_export): component filtering for exports, bug-fixes and tests(#143) 2024-02-27 00:12:14 +01:00

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.