Blender_bevy_components_wor.../testing/bevy_example
kaosat.dev fbcd025dc1 feat(Blenvy): continued restructuring & upgrade of blueprint spawning logic
* updated simple test to include deep nested blueprint instance within blueprint instance case
 * restructured materials handling to use the new logic, removed clutter
 * experimenting with solutions to the deeply nested blueprint instances problem
 * moved out all obsolete code to "old" folder, keeeping around until all problems are solved
 * added hack-ish solution to the "aabb system as post process" implementation
 * various minor boilerprate changes
2024-07-05 12:56:51 +02:00
..
art feat(Blenvy): continued restructuring & upgrade of blueprint spawning logic 2024-07-05 12:56:51 +02:00
assets chore(): minor tweaks & experiments 2024-06-26 14:35:47 +02:00
src feat(Blenvy:Bevy): almost complete rework of blueprint spawning workflow (wip) 2024-07-02 14:32:39 +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.