Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b8
Issue ID
917361
Regression
No
Timeline animation behaving unexpectedly when model has Animator controller and its Animation Type is set to Generic
Steps to reproduce:
1. Open attached Unity Project "case_917361-VR_sink-reduced".
2. Open Scene "Scenes\test".
3. Enter Play mode.
4. Observe the dinosaur model move sideways (with-AnimController.gif).
5. Select "raptor" in the Inspector.
6. Remove Animation Controller.
7. Enter Play mode again.
8. Observe the dinosaur model move along the X axis as it was animated in the Timeline (without-AnimController.gif).
Expected result: The animated model follows a trajectory set by the Timeline editor.
Actual result: Axes get mixed up, different animations may cause random "jumping" of the model, diagonal movement and other unexpected behavior.
Reproducible with: 2017.1.0b1, 2017.1.0b2, 2017.1.0b3, 2017.1.0b4, 2017.0.0b5, 2017.1.0b6, 2017.1.0b7, 2017.1.0b8, 2017.1.0b9
Not tested on previous versions because feature was introduced in 2017.1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment