Hello,
I found a weird behavior with shape casting. It looks like the shape cast won’t hit when:
Here’s a repro: https://playground.babylonjs.com/#1VT1BK#23
If you change mesh1.position.x to -0.5, the shape cast will succeed.
No hit
Hit
I would expect a hit in all cases.
- the cast direction is away from the intersecting shapes
That’s the feature. if the cast direction moves the meshes apart then no collision will happen.
Not taking casting direciton into account will make it behave like the proximity query. Babylon.js docs
Thanks for your answer, but this “feature” is not consistent. A proximity query is different in that the cast is done in all directions up to max distance.
When I look at the definition of shape cast in the docs, I would expect a collision in any case:
When a shape goes from a start position to an end position, if there is a collision, at which fraction of that movement does it happen?
If there’s an exception with shapes already intersecting, this should be true for any cast direction, and this exception should be properly documented. This behavior is found in Unity documentation
Notes: SphereCast will not detect colliders for which the sphere overlaps the collider
I’ll update the documentation for that specific part.
