Blender_bevy_components_wor.../testing/bevy_example
kaosat.dev 56763879b1 feat(Blenvy): added an "all-in-one" (almost) Blenvy crate
* includes components, registry export & blueprints
 * overhauled settings / config to match the new structure
 * keeping the different sub plugins for now
 * cleaned up some of the internals of the blueprints code
 * related tweaks & cleanups
 * added events to blueprints : for when assets have been loaded & when a blueprint has been spawned (wip)
 * various experiments with blueprints
 * updated testing to make use of new crate & logic
2024-06-20 00:05:02 +02:00
..
art chore(testing): moved blend files into "art" folder 2024-04-26 23:01:58 +02:00
assets feat(Blenvy): added an "all-in-one" (almost) Blenvy crate 2024-06-20 00:05:02 +02:00
src feat(Blenvy): added an "all-in-one" (almost) Blenvy crate 2024-06-20 00:05:02 +02:00
Cargo.toml feat(Blenvy): added an "all-in-one" (almost) Blenvy crate 2024-06-20 00:05:02 +02:00
README.md feat(gltf_auto_export): component filtering for exports, bug-fixes and tests(#143) 2024-02-27 00:12:14 +01:00

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.