3D boids don't work #4

New Issue

TheYellowArchitect · 2024-12-06T02:04:54+03:00

2024-12-06 02:04:54 +03:00

Hello! There are many godot plugins but this one is said to be the only one supporting 3D.
However, I have failed to make them work. It's like their velocity gets stuck to go on Z. I even tried placing a static marker for Flock3D and instead of the boids flying around it, flying on a radius from a point, they just fly to the distance (as they go away, they become smaller)

If this is fixed, I am willing to make a 3D example. I do need it for my project after all (full 3D game, specifically for floating/hovering cards)

Also, there is a warning spam, it stops if I press "New Flock Properties" on the Flock3D Node. Even if I reset it rightafter to the default, it stops the warning spam lol

Hello! There are many godot plugins but this one is said to be the only one supporting 3D. However, I have failed to make them work. It's like their velocity gets stuck to go on Z. I even tried placing a static marker for `Flock3D` and instead of the boids flying around it, flying on a radius from a point, they just fly to the distance (as they go away, they become smaller) If this is fixed, I am willing to make a 3D example. I do need it for my project after all (full 3D game, specifically for floating/hovering cards) Also, there is a warning spam, it stops if I press "New Flock Properties" on the `Flock3D` Node. Even if I reset it rightafter to the default, it stops the warning spam lol

boids-3d.png

476 KiB

dusk commented

2024-12-06 19:31:58 +03:00

yeah sorry, i did not really test the 3D too much so it might have been broken while i was changing stuff. i'll take a look at it

dusk added the

bug

label 2024-12-06 19:32:26 +03:00

dusk commented

2024-12-06 21:10:41 +03:00

i think this problem is mostly because of units in 3D being different than 2D so the default values understandably make the math freak out because they are tuned for 2D. still even after adjusting the values a bit it seems like they are simply "too fast" (see video). gonna look into that more, ill push the 3d example i made though

Godot_v4.3-stable_win64_sBx35hlp4W.mp4

398 KiB

dusk commented

2024-12-06 22:05:57 +03:00

ok actually, it seems like for whatever reason the boid properties werent being used, it looks correct now

godot_RpX1UfZUvS.mp4

660 KiB

dusk commented

2024-12-06 22:15:25 +03:00

oh btw i fixed the warnings as well. gonna be publishing a new version now

dusk commented

2024-12-06 23:25:42 +03:00

@TheYellowArchitect https://git.gaze.systems/dusk/godot_boids/releases/tag/v0.1.2

dusk commented

2024-12-13 12:31:10 +03:00

i’m gonna close this now, though you can reopen it if you think it’s still a problem

dusk closed this issue

2024-12-13 12:31:10 +03:00

TheYellowArchitect commented

2025-01-07 18:40:38 +03:00

I apologize for not having replied to the above, I got no email notification for any of these messages, and I had forgotten I posted here 😓

TheYellowArchitect commented

2025-01-07 19:10:50 +03:00

I did a quick testing. The 2D follow example seems broken:
The same goes for the 3D example

At the end of the 3D example video there is also a bug I encountered when I first used this boids add-on, where you press F6 or F5 and the game doesn't start. If you stop and start again, it doesn't start either and requires a Godot reboot. It's a serious bug imo.
^The above video seems to be broken for some reason, reuploading the "run current scene" bug, its the 3rd uploaded file: https://git.gaze.systems/attachments/fa06b686-b05e-4898-9484-315ec5978b14
Anyway, the 3D example is as broken as the 2D one in movement/boids.

Lastly, DebugCam doesn't exist in the released package above so it had to be removed for any boids to work.

I did a quick testing. The 2D follow example seems broken: <video src="/attachments/7274b98b-39aa-4831-942f-8f457fe32ae1" title="video-250107-2006-14.mp4" controls></video> The same goes for the 3D example <video src="/attachments/a11d4ef6-d2c6-4a9a-b53a-fb7d8b22ccf4" title="video-250107-2008-16.mp4" controls></video> At the end of the 3D example video there is also a bug I encountered when I first used this boids add-on, where you press F6 or F5 and the game doesn't start. If you stop and start again, it doesn't start either and requires a Godot reboot. It's a serious bug imo. ^The above video seems to be broken for some reason, reuploading the "run current scene" bug, its the 3rd uploaded file: https://git.gaze.systems/attachments/fa06b686-b05e-4898-9484-315ec5978b14 Anyway, the 3D example is as broken as the 2D one in movement/boids. Lastly, DebugCam doesn't exist in the released package above so it had to be removed for any boids to work.

video-250107-2006-14.mp4

906 KiB

video-250107-2008-16.mp4

2.5 MiB

video-250107-2012-06.mp4

698 KiB

TheYellowArchitect reopened this issue

2025-01-07 19:10:50 +03:00

dusk commented

2025-01-14 23:16:48 +03:00

i'm not really sure why those happen; i can't really reproduce any of that on my computers (windows or linux)... did you try building the libraries yourself and see if they do the same thing? i don't really have anything else you could try i'd have to add some more debugging info code, no idea how i could reproduce this either since it works for me...

(the debugcam i forgot about, i'll have to remove those lines from the examples)
(also feel free to open an issue on the github mirror, i forgot to link there)

i'm not really sure why those happen; i can't really reproduce any of that on my computers (windows or linux)... did you try building the libraries yourself and see if they do the same thing? i don't really have anything else you could try i'd have to add some more debugging info code, no idea how i could reproduce this either since it works for me... (the debugcam i forgot about, i'll have to remove those lines from the examples) (also feel free to open an issue on the github mirror, i forgot to link there)

Sign in to join this conversation.