Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f3
Issue ID
903614
Regression
No
ClosestPointOnBounds() returns closest point IN bounds
The function "collider.ClosestPointOnBounds()" is misleading since it gives you a point inside bounds not on bounds (on = contact, in = inside).
If the input position is already inside the bounds the output won't be onto the bounds limits but will instead return the input position values.
This should be renamed to ClosestPointInBounds(), or the code for the function should be edited so the function returns closes point ON bounds.
Reproduced on:5.4.3f1 5.5.2p2 5.6.0f3 2017.1.0b1
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
chriscode
Jul 08, 2018 22:18
Agreed
RoutineAyhan
Mar 16, 2018 09:48
I too think that this is a misleading name. Had the same problem a few minutes ago.
JohnHacker
Oct 24, 2017 21:15
I agree with OP. You can know if the point is inside bounds and use the point if that's your desire, but there's not a built-in function that returns the point ON bounds.