Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
1
Found in
5.6.1p1
Issue ID
921297
Regression
Yes
TrailRenderer doesn't function when object position is changed instantly
Steps to reproduce:
1. Open "TestStartOrder.zip" attached project
2. Enter play mode
3. Observe trail sometimes working, sometimes not
Expected result: Trail is always created from the sphere start position to the end regardless of interpolation
Actual result: With Interpolation trail sometimes gets created, without - it never gets created
Doesn't reproduce on: 5.5.4f1, 5.6.0a1, 5.6.0a3, 5.6.0a4
Regression introduced in 5.6.0a5
Reproduced on: 5.6.0a6, 5.6.0b1, 5.6.0b8, 5.6.1p1, 5.6.1p4, 2017.1.0b10, 2017.2.0a4
Notes: Setting even the tiniest amount of in-between motion delay makes the trail function properly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment