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
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
Add comment