Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X, 2018.1.X, 2018.2.X
Votes
0
Found in
2017.2.0b2
2017.3.0f3
Issue ID
984547
Regression
Yes
Upgrading project from 2017.1 to 2017.2, slows down Root Motion
Reproduction steps:
1. Open "AnimationTest3.zip" project
2. Enter Play mode
3. Walk around using WASD
Expected Result: The Player moves at the same speed in 2017.2 (and up) as in 2017.1 (and below)
Actual Result: The Player moves up to two times as slow in 2017.2 (and up) compared to 2017.1 (and below)
Fixed in: 2018.3.0a1, 2018.2.0b4, 2018.1.6f1
Reproduced with: 2018.1.0b3, 2017.3.0p2, 2017.2.1p2, 2017.2.0f1, 2017.2.0b11, 2017.2.0b5, 2017.2.0b2
Did not reproduce on: 2017.2.0b1 to 2017.2.0a1(Project doesn't start, crashes immediately), 2017.1.3f1
Note:
The movement is not always slower, in that case, Exit and Enter Play mode until you notice a significant slowdown
Workaround:
Adjust the "Base Walk Speed Multiplier" value in the "Player Controller" component on the "Player" object
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script
- New items are created and old ones remain in memory when using 'treeView.SetRootItems(items)' and 'treeView.Rebuild()' which can cause a memory leak
- Code continues to run after enabling the Frame Debugger when in paused Play Mode and using 'WaitForSecondsRealtime' coroutine
- Dragging and dropping files from the Unity Editor to a different app doesn't work when Cmd-Tab is used to switch apps
- SDF Baking causes memory to be allocated that isn't deallocated when in Play Mode and in Builds
Add comment