Search Issue Tracker
Fixed in 2021.3.21f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
0
Found in
2020.3.42f1
2021.3.16f1
2022.1.23f1
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-21893
Regression
No
TrailRenderer.GetPositions returns invisible points
How to reproduce:
1. Open the user-attached project “TrailRenderer”
2. Open the “Main” scene
3. Enter the Play Mode
4. Observe the lines
Expected result: Both white and red lines are dotted
Actual result: Only the white line is dotted
Reproducible with: 2020.3.42f1, 2021.3.16f1, 2022.1.23f1, 2022.2.2f1, 2023.1.0a24
Reproducible on: Windows 11 Pro, macOS 12.4 (Intel)
Note: Also reproducible in Player
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note (fix version 2023.2):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions
Resolution Note (fix version 2023.1):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions
Resolution Note (fix version 2022.2):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions