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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment