Search Issue Tracker
Fixed in 2018.2.X
Votes
13
Found in
2017.1.0f3
Issue ID
938726
Regression
No
[Backport] [Backport] Start Delay of Particle System is not applied when object is in Timeline
Reproduction steps:
1. Open the attached project "987068.zip";
2. Open the Test scene;
3. Click the Pause Button;
4. Click the Play Button;
5. Click the Next Button again and again.
6. In the Game view, you can see the two effect with the same start delay, 0.04s.
Expected results: both of them should act the same and start with the same delay;
Actual results: the one which is attached to the timeline, has different start delay.
Note: in the console, you can see 3 times, current, timeline object and object without no timeline. The output shows when does the effect start.
Reproducible on: 2017.1.2p4, 2017.2.1p1, 2017.3.0p2, 2018.1.0b2, 2018.2.0a1.
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
pavel_litvin
Oct 25, 2017 16:03
I confirm this one, also hear the same issue with animation speed.
Also look at particle system behavior, when "loop" parameter is off and it reach "Hold" part of Control Playable Asset Clip. ( Particles will fly away with increasing speed).