Search Issue Tracker
Fixed
Votes
0
Found in
5.3.6f1
Issue ID
818304
Regression
No
The Plane struct constructor calculates "this.m_Distance" inaccurately if the passed normal vector isn't normalized by user
Steps to reproduce:
1. Observe Plane third constructor (or watch attached photo).
Expected results: "this.m_Distance = -Vector3.Dot(this.m_Normal, inPoint);"
Actual results: "this.m_Distance = -Vector3.Dot(inNormal, inPoint);"
--- "This.m_Normal" normalizes passed vector but doesn't use it to calculate "this.m_Distance". The reason behind
this is that user can accidentally pass not normalized vector so the second line of Plane third overload constructor
will use not normalized vector and will calculate distance wrong. The code used in actual results will save user from
normalization errors. (More about this in editor window).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Package Manager window disappears when adding a package from git URL
- Duplicating an array element in Inspector when there's a scrollbar makes an invisible item at the bottom
- Text in the Profiler events disappears before the event reaches the bottom of the window when changing the height of the Module details pane
- The Text Field of the parameters of the “Layout Element” Component disappears when inserting the “NaN” text
- Mesh Collider stops working and throws an error "doesn’t have Read/Write enabled" in the Development Console when in the Player
Add comment