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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment