Search Issue Tracker
Fixed in 2.8.9
Fixed in 3.0.0-pre.5
Votes
0
Found in [Package]
2.6.17
2.8.9
2.9.4
3.0.0-pre.3
Issue ID
CMCL-1306
Regression
No
CinemachinePathBase.FindClosestPoint doesn't search the last segment of its path when there are more than 2 segments
How to reproduce:
1. Open the user-attached “PathClosestPoint LatestPatch.zip” project
2. Open the “SampleScene” Scene
3. Select the “Sphere” GameObject in the Hierarchy window
4. Enter Play Mode
5. Note the “Nearest Point” value of the Script component
Expected result: The “Nearest Point” value is 3
Actual result: The “Nearest Point” value is a fraction value
Reproducible with: 2.6.17 (2020.3.43f1), 2.8.9 (2020.3.43f1, 2021.3.16f1), 2.9.4 (2020.3.43f1, 2021.3.16f1, 2022.2.1f1), 3.0.0-pre.3 (2022.2.1f1, 2023.1.0a24)
Reproduced on: macOS Monterey 12.6 (Intel), Windows 10 64bit - User Reported
Edit: The “Nearest Point” fraction value might be ~2.013 and or higher when testing
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment