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
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment