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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment