I’m attempting to do a simple walkcycle and have it follow a path. I’m doing this just like it says in the 2.33 guide: put the walkcycle as an NLA strip on the armature, then normal parent the armature to the path and set ‘use path’ and the stride parameter to match.
This has only worked one time.
I can duplicate the armature and path that it worked on, but that’s cumbersome and cannot be imported (to my knowledge) to another file completely intact. With that one successful exception, every time it has stretched/compressed the walkcycle to take up the path in one stride. This looks horrible, as it slides all over the ground. For the moment I can workaround, but soon I’ll have to make more complex paths and I just can’t do that in the present situation. Can anyone tell me what I’m doing wrong? I followed all the steps in the book, and it just isn’t working.
I accidentally discovered it when I mis-set the stride parameter to something insanely large just a minute ago while fooling with it.
The stride parameter seems to be auto-doubled. Apparently that’s a change from the previous version, because there’s no mention of it in the book. My guess is that it’s designed so that you only have to count one step of a bipedal stride instead of multiplying it by two. It was partly my doing, because I miscalculated the stride length, but the program was also doubling THAT, which messed it up royally. The cycle covers a distance of 4.0 units (when correctly calculated), so that’s the figure I put in the stride parameter. But in fact, after experimentation I found that only 2.0 units will make it sync correctly.
(And before you think that I’ve got it set to display double increments or something, I did this cycle by the numbers, not visually.)