Currently, finding parts in Region3 with the existing api limits you to up to 100 parts (default limit is 20). This is incredibly restrictive. Please implement FindPartsInRegion3WithWhitelist, which only checks for the whitelisted parts or their descendants within the region, similar to what we have with rays in the form of FindPartOnRayWithWhitelist
12 Likes
Yeah, regions are lacking some love. The part limit and the inability to rotate them both diminish their usefulness.
2 Likes
The limit of 100 parts was lifted a few months ago:
> print(#workspace:FindPartsInRegion3(Region3.new(Vector3.new(-1000, -1000, -1000), Vector3.new(1000, 1000, 1000)), nil, math.huge))
131
5 Likes
Probably still faster to ignore on the C side than to, on a frequent basis, iterate through 1000s of parts in small spaces on high-detail levels. Would definitely be faster if you already know what you’re looking for and can whitelist.
5 Likes
That’s awesome! The wiki should probably be changed to reflect this.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.