Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.7.0-pre.2
Issue ID
1415354
Regression
Yes
Control track nested in sub-timeline doesn't deactivate GameObject
1. Open project "Sequences_lastRelease_22.1.zip"
2. In the Hierarchy window select "GameObject' GameObject and expand it then expand "A" GameObject
3. Select "GameObject" GameObject
4. In the Timeline window double click on "A" clip
5. Move the playhead further than the clip's length
6. Observe the Hierarchy window
Expected result: "A1" GameObject is deactivated
Actual result: A1 GameObject is not deactivated
Reproducible with: 1.7.0-pre.2, 1.7.1 (2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11)
Not reproducible with: 1.7.0-pre.1 (2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a11)
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
Resolution Note:
This issue is by design and it probably does not impact users. For now, this issue is on hold if we get users' feedback about it we will act based on the feedback. For now, it's not an issue.