Search Issue Tracker
Fixed
Fixed in 2.3.X
Votes
0
Found in [Package]
2.3.X
Issue ID
SPLB-169
Regression
No
Returned parameter t does not correspond to the nearest point found when using “CurveUtility.GetNearestPoint”
How to reproduce:
1. Open the user’s attached “BezierBug.zip” project
2. Enter Play Mode
3. Observe both logs in the Console window
Expected result: Both logs have similar coordinates
Actual result: Logs has different coordinates ((5.56f, 19.4113f, 0f) and (4.654922f, 19.1567f, 0f))
Reproducible with: 2.2.1 (2021.3.27f1), 2.3.0 (2022.3.2f1, 2023.1.0f1, 2023.2.0a20)
Reproduced on: macOS 13.2.1 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Add comment