Search Issue Tracker
Fixed
Fixed in 1.6.4
Votes
0
Found in [Package]
1.6.3
Issue ID
TB-104
Regression
No
Duplicated Track Groups lose their nested track's game object assignments
Repro steps:
1. Create a new timeline or select an existing one
2. Create a Track Group
3. Within the Track Group, add a track which has a game object reference (i.e. an activation track, audio track, or animation track)
4. Select the Track Group and duplicate it
5. Observe that the duplicated tracks no longer retain their game object references
Expected outcome:
- Tracks within duplicated Track Groups to retain their game object references
Note:
- Duplicating tracks outside of Track Groups seems to work fine.
- Doesn't seem like a regression, repros in 2021.2 up to 2022.1
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
Add comment