Search Issue Tracker
Fixed
Fixed in 2021.3.32f1, 2022.3.11f1, 2023.1.17f1, 2023.2.0b14, 2023.3.0a10
Votes
0
Found in
2021.3.30f1
2022.3.10f1
2023.1.15f1
2023.2.0b11
2023.3.0a7
Issue ID
UUM-49717
Regression
No
Animation Event marker is not placed on the current time of the timeline when using the “Add Event” button
How to reproduce:
1. Open the user’s attached “AnimationEventBug.zip” project
2. In the Project window, select “Ch39_nonPBR.fbx”
3. In the Inspector window, open the “Animation” tab
4. Expand “Events” tab
5. Press the “Add Event” button
6. Observe the result
Expected result: Added event’s marker is placed on 0:00
Actual result: Added event’s marker is placed not on 0:00
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a7
Reproduced on: macOS 13.5.2 (Intel), Windows 10
Not reproducible on: No other environment tested
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0a10):
Fixed in: 2023.3.0a10
Resolution Note (fix version 2023.2.0b14):
Fixed in: 2023.2.0b14
Resolution Note (fix version 2023.1.17f1):
Fixed in: 2023.1.17f1
Resolution Note (fix version 2022.3.11f1):
Fixed in: 2022.3.11f1
Resolution Note (fix version 2021.3.32f1):
Fixed the sizing of the event marker in the FBX importer Animation tab. Depending on the screen's resolution, the image area was too big, but the actual texture was still sized down to fit the visible area, giving the impression that the event marker was shifted to the left.