Search Issue Tracker
By Design
Votes
0
Found in
6000.0.40f1
6000.1.0b8
6000.2.0a5
Issue ID
UUM-98281
Regression
No
Recording highlight is not shown when switching between the two GameObjects with Animations
How to reproduce:
1. Open the attached project "Test"
2. Open the "SampleScene" scene
3. Make sure to have the "Animation" tab opened and select the "Test1" GameObject in the Hierarchy
4. Press the "Record" button" and select the "Test2" GameObject
5. Observe the "Animation" tab
Expected results: The recording highlight is shown
Actual results: The recording highlight is not shown unless you move between the frames
Reproducible with: 6000.0.40f1, 6000.1.0b8, 6000.2.0a5
Can't test with: 2022.3.58f1 (Recording is not carried over between the GameObjects)
Reproducible on: macOS Sequoia 15.3
Not reproducible on: No other environment tested
Note: Recording is still active, only the highlight is not shown which might be confusing
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 Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
This is by design since in this specific case, you are using two GO that are not part of the same hierarchy. This means the two GO you are using, each have an independent Animator component. Since it’s normal to not activate the “Rec mode” when simply selecting a GO in the scene, this is expected behaviour.
In order to get the result described in this report, you need the two GO to be under the same hierarchy. This will enable you to only have one Animator on the root GO, and an animated a child or multiple children with the behaviour described in this report.
thank you.