Search Issue Tracker
Fixed
Fixed in 2021.3.21f1, 2022.2.8f1, 2023.1.0b3, 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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2023.2.0a1):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions
Resolution Note (fix version 2023.1.0b3):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions
Resolution Note (fix version 2022.2.8f1):
TrailRenderer.GetPositions should be replaced with TrailRenderer.GetVisiblePositions