bevy_mod_debugdump
bevy_mod_debugdump copied to clipboard
Is debugdump lacking some information ?
in today's discovery, I realized that bevy's initialization is quite complex, as it requires an "update" before having registered all components:
playground with bevy 0.15: https://learnbevy.com/playground?share=3f41d0ce49af0f5569aaf321d6d56e52899a0c66c8b065ad10aa227bc72bfa7d
// bevy 0.16
let mut app = App::new();
app.add_plugins((
DefaultPlugins,
));
// 301 registered components
app.finish();
// 306 registered components
app.cleanup();
// 307 registered components
app.update();
// 441 registered components
I suspect systems may be in a similar state 🤔
I'm wondering if bevy_mod_debugdump is considering this.
- The ambiguity from https://github.com/dimforge/bevy_rapier/issues/650 brought me to this, where my ambiguities did not seem displayed by
bevy_mod_debugdump, but they are present when going throughfinish, cleanup, update.
I can probably make an easier repro if there's interest.