Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
1
Found in
2018.2.18f1
2018.4
2019.2
2019.3
2019.3.0b8
2020.1
Issue ID
1194500
Regression
Yes
Calling TrailRenderer Clear after the trail is created results in incorrect renderer bounds
How to reproduce:
1. Open attached project "TrailRendererBoundingIssue-Unity2019.3.zip" and scene ""
2. In Hierarchy window, select "RuntimeTest" object
3. In Inspector window, enable "Use Clear" boolean
4. Enter Play mode
5. Observe the green border of the trail on the first frame the trail is created
Expected result: the border encapsulates the whole trail
Actual result: the border does not encapsulate the whole trail
Reproducible with: 2018.1.0b13, 2018.4.12f1, 2019.2.10f1, 2019.3.0b9, 2020.1.0a9
Not reproducible with: 2017.4.34f1, 2018.1.0b1
Comments (1)
-
Peter77
Oct 29, 2019 06:16
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2018.4):
Verified in:
2018.4.23f1