koobas.hobune.stream
Why is it that the Bounds.Intersects DOES NOT WORK if the gameobjects are rotated?
While testing the intersection of two cube gameobjects I noticed that when they were neither of them was rotated, the Bounds.Intersects was working just fine. But when either of them or both was rotated to my surprise I noticed the Bounds.Intersects ceased to work.
I believe it has to do with Bounds' representation of a AABB.
An axis-aligned bounding box, or AABB for short, is a box aligned with coordinate axes and fully enclosing some object. Because the box is never rotated with respect to the axes, it can be defined by just its center and extents, or alternatively by min and max points.
Thanks, Dragate.
I see what you mean. The Bounds.Intersects works just fine if the two rotated objects are not very close; when they are close, almost touching but not quite, then the Bounds.Intersects doesn't. If I want extreme precision, even hairline precision, how could I solve the problem?
Do I have to make calculations to redefine each object's boundaries using their center and extends or by $$anonymous$$ and max. But how could Ido that?
Could I use ClosestPointOnBounds ins$$anonymous$$d?
I don't know how you could achieve this. Hopefully, someone else can help you.
