RigidBody3D support

[meridew]

I'm really excited to try and implement this in my hobby project.

Is there any chance you might be able to provide RigidBody3D support for this?

[90-008]

i'm not sure what exactly you meant by RigidBody3D support? do you want each boid to be a rigidbody and respect physics? should be possible i think but i didn't really think about it. in theory it should be just adding new implementations that base off of RigidBody2D/3D and then use the rigidbodies apply force method to apply forces, though not sure if i can do this right now but i'll keep it in mind

[meridew]

Yes perhaps a RigidBoid3D or something?

I just managed to implement as you suggested - using the distance between the hidden boid entity and the RigidBody3D entity to calculate follow strength. It gives me an additional control layer but it works really well, nearly 2000 RigidBody3D entities with the new Jolt physics engine.

I was only able to get about 300 boid entities in a pure GDScript implementation.

It would be really handy to adjust boid/flock properties at runtime.

Is there anyway to disable the boid registration output?

[Flock3D:84875938424] boid 1009535468182 registered

Really great work! Thanks again!

[90-008]

good to know you could get something working. i'll actually implement it in rust proper when i find time for this

It would be really handy to adjust boid/flock properties at runtime.

this should be simple yeah, i didn't really have a usecase for this so i hadn't added it but it should be fine to just update the properties before we calculate anything.

Is there anyway to disable the boid registration output?

i can add a way to disable these yeah just haven't thought of how? probably something like an option on the singleton i guess

[meridew]

Personally my use case is that my game is data driven, and all my "non-singleton" entities are pooled, instanced, and driven by stats and systems (zero code on the entities). Being able to tween a boid "component" property over time for a flock would result in some spectacular real-time physics movement.

I realise this is supposed to simulate bird-oid movement, but with gravity they are more like "glob-oids" (if globs even flock?) - kinda looks like sticky nano-bot swarms, which tbh is exactly what I wanted.

You've really built something great here - and with Jolt now, you can do a bewildering amount per physics frame, thanks to your add-on.

With regard to logging, really not critical, it just makes the loading a little slower as I'm instancing 10k+ entities and it clogs up the output. I imagine a bool on the singleton would work well.

[meridew]

It would also be super useful to disable BoidsProcess per flock/boid ID.

Do you have the raw rust code in github? I'd happily create a PR

[90-008]

disabling flocks / specific boids should be pretty easy, implementing a bool on flocks / boids and then skipping flocks if they are disabled (here https://github.com/yusdacra/godot_boids/blob/main/rust/src/lib.rs#L242) and skipping boids if it's disabled (this one would need to be disabled both in flock get_boids so it doesnt return that boid when queried but also in get_boids_posvel)

the rust code is in the root of the repo under the rust directory if you wanna play around