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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Add comment