Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
preview.2 - 1.4.0
Issue ID
1232412
Regression
No
Performance drop while using Control Track with Particle system when a clip enters the looping section
To reproduce:
1. Open attached project ("case_1232412.zip")
2. From Hierarchy select "TimelineControl" Game Object
3. Press Play and in Timeline window select the Control Track
4. Observe the FPS before and after the Control Track enters a looping section
Expected result: The FPS remains relatively close
Actual result: There is a significant FPS drop
Reproducible in: 2017.4.39f1, 2018.4.20f1, 2019.3.8f1, 2020.1.0b4, 2020.2.0a5
Reproducible in package versions: 1.1.0, preview.2 - 1.4.0
Note: In the Profiler window it can be observed how Update.DirectorUpdate spikes significantly in the looped section
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Disable the 'control children' flag on the first control track. There were multiple control tracks trying to advance the same particle systems, which causes them to de-synchronize and re-simulate. In 2019.4, the control children flag was changed to be defaulted to off.