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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment