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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note (fix version 2018.4):
Verified in:
2018.4.23f1