Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.10f1
2019.2.0a1
2019.3.0a1
Issue ID
1169997
Regression
No
LineRenderer Line is not rendered when it is in between Orthographic Camera position and the actual camera rendering position
How to reproduce:
1. Open attached project "Case_1169997_repro.zip"
2. Open "Repro" scene
3. Observe Game View
Expected result: Two lines appear in the Game View
Actual result: One line appears in the Game View
Reproducible with - 2017.4.30f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Notes:
This happens because the LineRenderer Line is billboarding to the position of the camera which means that if the Near Clipping Plane of the Orthographic Camera is set to a negative value, the Line will face away from the actual rendering point of the Camera.
(Also apply same fix to TrailRenderer, if possible)
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
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a4
Fixed in 2019.3.0b4
Fixed in 2019.2.6f1
Fixed in 2018.4.10f1