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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
Add comment