Search Issue Tracker
Fixed in 1.3.0
Fixed in 1.2.13
Votes
0
Found in [Package]
1.1.0, 1.3.0-preview.6
Issue ID
1216702
Regression
No
Performance drop when using Control Track with Particle system if a clip is extended beyond the original duration
To reproduce:
1. Open attached project ("case_1216702.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 "HOLD" phase
Expected result: The FPS remains relatively close
Actual result: There is a significant FPS drop
Reproducible in: 2017.4.36f1, 2018.4.17f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a22
Reproducible in package versions: 1.1.0, 1.3.0-preview.6
Note: On a testing machine, the FPS drop resulted in a ~40% FPS loss (from ~2450 FPS while playing the initial clip, down to a ~1500 FPS while in the "HOLD" phase).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Summary tab is selected but its content is not displayed when pressing Ctrl/Cmd+A in the Project Auditor window
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
Add comment