Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.1.3f1
Issue ID
1065826
Regression
No
"Vector2.Distance" is slower than "Vector3.Distance"
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Open the "Test" scene
3. Open the Profiler Window
4. Enter Play Mode
5. Select the First Frame
6. Search for "Start"
7. Compare the "Time ms" of "Vector2Test.Start()" and "Vector3Test.Start()"
Expected Result: "Vector2" and "Vector3" "Distance" function should execute at a similar time
Actual Result: "Vector2" "Distance" function is slower than "Vector3"
Fixed in: 2019.2.0a4, 2019.1.0a6
Reproduced with: 2019.1.0a5, 2019.1.0a1, 2018.3.0b7, 2018.2.14f1
Did not reproduce on: 2019.1.0a6, 2018.1.9f1 (Couldn't find the scripts in the Profiler)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
- “ArgumentException” error thrown when disabling all columns in Project Auditor's Multi-column panel context menu
- Errors are thrown and contextual menu does not open when right-clicking multiple mixed keyframes in Dopesheet
- Crash on MergeObjectCollection when repeatedly selecting a Prefab Asset in the Project Browser
Add comment