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
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
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.