archetype testing #141
Labels
Comments
|
1 circles |
|
ooo it seems i can iterate the archetypes and maybe print some info about what components each of them contains? that would be amazing! |
|
bohahaha! i'm become amy, mistress of exclusive systems :3 fn print_archetypes(
world: &World,
mut count: Local<usize>,
) {
let c = world.archetypes().len();
if c > *count {
*count = c;
info!("len = {}", c);
for (i, a) in world.archetypes().iter().enumerate() {
info!("{}", i);
for c in a.components() {
info!("{:?}", world.components().get_name(c).unwrap());
}
}
}
} |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
60 archetypes seems like a lot! like, i can think of maybe 12 off the top of my head, but 60? what's going on in there? (was 97 actually)
next steps, tinker with the same idea in smol, figure out how to minimize the fragmentation. especially for those incrementing archetypes [a], [a,b], [a,b,c],...
wait, does that only happen when pulling them out of the scene? try creating an entity with children then remove parent on them (in smol) [edit: nope]
the fucking aabb's!
ditching the fucking highlights and info texts cuts it down to exactly 60 (from 97)...
only 75 after c4616da
The text was updated successfully, but these errors were encountered: