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
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment