Search Issue Tracker
Won't Fix
Votes
1
Found in
2023.1.0a25
2023.2.0a1
Issue ID
UUM-968
Regression
No
The Line Renderer is inconsistent when the Width is above 0.5 or it's positions are too close to each other
How to reproduce:
1. Open the user's attached "LineRenderer.zip" project
2. Open the "SampleScene" Scene
3. Select the "Line" GameObject in the Hierarchy window
4. Observe the "Line" GameObject in Scene view while changing the Width value (See attached "1286740_widthRepro.mp4")
5. Select the "Line (3)" GameObject in the Hierarchy window
6. Observe the positions of the Line Renderer in the Inspector window
7. Observe the "Line (3)" GameObject in the Scene view
Expected result: Line Renderer is consistent when Width is above 0.5 (step 4) or Line Renderer's positions are too close to each other (step 7)
Actual result: Line Renderer is inconsistent when Width is above 0.5 (step 4) or Line Renderer's positions are too close to each other (step 7)
Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.2.1f1, 2023.1.0a22
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
LineRenderer is being deprioritised.