:FindPartsInRegion3 incorrectly identifying WedgeParts

[PhoenixSigns]

When using :FindPartsInRegion3(), WedgeParts will be included in the list as long as its bounding box is within the region rather than its actual shape. As you can see in the following image, I have set the lower and upper bound of the region, indicated by the two red parts.

After running the following code, the triangle part will printed out even though its actual shape isn’t within the boundaries. This is extremely problematic for games using triangle terrain where certain triangles will be at a diagonal or even vertical angle.

wait(0.2)

local Pos1 = game.Workspace.P1.Position
local Pos2 = game.Workspace.P2.Position
local Box = Region3.new(Pos1,Pos2)
local Parts = game.Workspace:FindPartsInRegion3(Box,nil,500)

for i,v in pairs(Parts) do
	print(v.Name)
end

The repo file is below.

TriangleRepo.rbxl (14.7 KB)

[sircfenner]

This is not a bug - it’s intended behavior.

See also:

Region3 not accounting for rotation

That’s how it’s always worked, and how it’s supposed to work. FindPartsInRegion3 isn’t a collision detector, it’s a part finder that finds nearby parts quickly by using bounding-boxes. If you’re going to do collision detection, then use it for the broad phase, and implement the narrow phase yourself. Or, if you want it to be efficient, get AxisAngle to do it.

[PhoenixSigns]

Oh rip. So is there an alternative method aside from :GetTouchingParts() or am I stuck with this behavior?

[Chrythm]

There’s always raycasting if you run out of ideas.

[PhoenixSigns]

Raycasting doesn’t fulfill the purpose as well though.