Hi any updates on these fixes?

Unity Engine
1

Hello, I was wondering if unity devs could give us some feedback on the following issues?

Thanks.

https://forum.unity.com/threads/obj…w-mode-vs-scene-playback.483435/#post-3209919

https://forum.unity.com/threads/playing-animtion-in-timeline-in-absolute-reference.493446/

1 Like
2

Unfortunately, they are still in progress. It’s taking a bit of time because they are not being worked on in isolation, and several fixes and improvements related to root motion are being worked.

3

Alright thanks Seant.

4

2017.3 is out and it’s still not fixed. @seant_unity Could we expect to see a fix in a patch release or 2018.x?

5

The fixes will be in a version of 2018. I don’t believe they will be back-portable to 2017.3.

Root motion has been undergoing transformations under the hood to better support timeline. 2018.1 has some of the changes that will fix issues with root motion with scale in timeline. You should notice the changes in the inline curve window - root motion values show up explicitly. Those needed to be addressed first, and now the animation team can properly address the absolute vs relative position issue.

1 Like
6

Hi, any news on this fix?

1 Like
7

The timeline is such a great idea but it’s so broken with runtime animators, most of my controllers use them but then when I bind the character to the timeline I have to remove the runtime animator which causes all manner of errors… pulls out hair

8

Timeline is kind of useless with all these limitations. This issue is still there in 2018.3 (beta), making the whole thing useless.

9

To give an update, it looks like a much better solution will land in 2018.3. That includes scaling root motion, making the starting position an option on the track (as opposed to the existance of a controller) as well as some other root motion/transform improvements.

We were hoping for 2018.2, or even 2018.1, but the change involves risk to both timeline and to animation, and we do everything we can to avoid regressions.

2 Likes
10

Thanks for the update! This sounds like it would fix the problem I’m having:

11

Same problem here.

12

Did anyone test this with the 2018.3.0b1 Beta? I have and it doesn’t seem to be fixed. I hope I’m wrong…