Search Issue Tracker
Not Reproducible
Not Reproducible in 1.6.X
Votes
0
Found in [Package]
1.6.3
Issue ID
TB-92
Regression
No
Assertion failed on expression is thrown when opening or playing a scene with Timeline
How to reproduce:
1. Open the attached "1380180.zip" project
2. Open the "Bug_Repo" Scene in the Assets folder
3. Press Play
4. Open the Console
Expected result: No errors
Actual result: An error is thrown - "Assertion failed on expression: `pred(previous, i)` "
Reproducible with: 1.2.18 (2019.4.33f1), 1.4.8 (2020.3.24f1), 1.6.2 (2021.2.6f1), 1.7.0-pre.1 (2022.1.0b2)
Note:
- Just doing step 2. is enough to reproduce the issue
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
The file is in an invalid state.
Without information on how it got into that state, and without a better idea of the prevalence of this issue (so far we only have one report), it would be premature to add costly consistency checking to the PlayableDirector loading routine.
If you get into this situation, it is probably due to multiple entries with the same key under the m_References section of the scene file where the PlayableDirector is saved.
The workaround in this specific case was to delete any references that looked like this (- : {fileID: 0}).
Description
Resolution Note (1.6.X):
The file is in an invalid state.
Without information on how it got into that state, and without a better idea of the prevalence of this issue (so far we only have one report), it would be premature to add costly consistency checking to the PlayableDirector loading routine.
If you get into this situation, it is probably due to multiple entries with the same key under the m_References section of the scene file where the PlayableDirector is saved.
The workaround in this specific case was to delete any references that looked like this (- : {fileID: 0}).
Description