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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.