Search Issue Tracker
In Progress
Fix In Review for 1.8.8
Votes
1
Found in [Package]
1.8.6
Issue ID
TB-259
Regression
No
Update.DirectorUpdate is affected by the whole content of the Timeline when only a few tracks are playing
How to reproduce:
1. Open the user-attached project “2023_2_Test”
2. Click File → Build Settings and check “Development Build” and “Autoconnect Profiler”
3. Build And Run the project
4. In Player Profiler, select the Hierarchy tab, expand the “PlayerLoop” and observe Update.DirectorUpdate
Expected result: Update.DirectorUpdate takes an insignificant amount of times
Actual result: Update.DirectorUpdate always takes 2 to 8 ms
Reproducible with: 1.8.4, 1.8.5 (2021.3.34f1, 2022.3.17f1), 1.8.6 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Note: Also reproducible in Editor
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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
Peter77
Jan 09, 2024 16:33
Related forum thread:
https://forum.unity.com/threads/in-64548-timeline-playabledirector-performance-issues.1531024/