Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0f1
Issue ID
926701
Regression
No
[Timeline] Root motion in Timeline looks different on Builds
The Root Transform Rotation (Based Upon (atStart)) and Root Transform Position (XZ) (BasedUp) configuration appear to not affect the animation on Builds, when used in conjunction with the Timeline editor.
Steps to reproduce:
1. Open User's attached project ("UnityProject.zip")
2. Build for Standalone (or iOS, or Android).
3. Play Build
4. Compare with the playing scene in the Editor
Expected behavior: Player and Editor Timeline videos are the same.
Actual behavior: Timeline video in Player is different than in Editor.
Reproduced with: 2017.2.0b1, 2017.1.0f2.
Tested with: macOS, Windows, iOS.
Note:
Animation settings:
Root Transform Rotation (Based Upon (atStart)): Body Orientation
Root Transform Position (XZ) (BasedUp): Center of Mass
What it actually looks like on device:
Root Transform Rotation (Based Upon (atStart)): Original
Root Transform Position (XZ) (BasedUp): Original
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
shubhamswaraj2021
Aug 19, 2020 13:13
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
AquaGhost
Sep 22, 2018 17:39
Still seeing this in 2018.3b
MadeFromPolygons
May 22, 2018 11:41
this is still in 2018.1 and 2018.2
GonzoGan
Mar 31, 2018 23:13
Issue still there on 2018.3. Fix is not consistant.
sanmn19
Aug 02, 2017 11:02
2017.1.0f3 hasn't fixed this issue.