Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2017.3.1f1
Issue ID
1005222
Regression
No
Trail starts rendering a frame late after the object was not moving and the previous trail has ended
To reproduce:
1. Open QA's attached project
2. Play the "test" scene, the path and the ball will be instantiated
3. Pause the Play Mode
4. Select "Parent" gameobject
5. Tick "Start Follow" on "Game Manager" component
6. Step a few frames
Expected result: The trail starts rendering as the object starts moving
Actual result: The trail falls behind one frame
Reproduced with: 2017.1.3f1, 2017.2.2f1, 2017.3.1p3, 2018.1.0b10, 2018.2.0a2
Notes:
- The trail works as expected if the object starts moving before trail disappears (Time setting in the Trail Renderer component).
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