Positions not constrained within flyrect

[nesdnuma]

Hello,

I have been using the Windows 64bit version of jit.boids3d provided on the Max forums. I have been trying to adapt it to control specific ranges of data for non-Jitter patches. However, when compared to boids2d, the positions with jit.boids3d go much beyond the values defined for flyrect. Is there any way to keep them inside a defined range?

[diablodale]

Hello. I don't have the current knowledge/remembering to help you with that. As I looked at the commits, I only made the minimal changes needed to get it to compile.

A quick look at the code suggests to me that the flyrect defines the relative boundaries of a flock, not the boundaries of the world.

This is the start of the code which seems to govern the behavior of a boid with the flock's flyrect. It seems to apply a change to velocity and not a hard limit to location.

boids_max/jit.boids3d/jit.boids3d.c

Line 765 in 21304d1

/* if test point is out of the left (right) side of flockPtr->flyrect, */

[nesdnuma]

Oh, I see. Thank you!