Original Post — Direct link
over 4 years ago - /u/RebelAndroid - Direct link

There was a bug specific to using a controller (on any platform) causing traversal emotes to be interrupted. It will be fixed in 10.40 (sorry, too late for 10.30).

Please note that you also must not sprint; if you have the option for
"Sprint by Default" on, you will need to use your input to disable sprinting or it will still cancel.

over 4 years ago - /u/RebelAndroid - Direct link

Originally posted by alphwn

Yes, i loaded in a different mission with sprint by default toggled off, and it still cancels the animation as shown in this video clip http://imgur.com/a/yyrSfJl

Maybe the slightest movement to the sides cancels it as well? Not too sure

But thanks for the reply, i really appreciate it :)

Yes, the issue was that any non-zero side movement was erroneously canceling the emote, which is unavoidable on controllers. That will be fixed in 10.40; all of the thresholds for cancellation are now shared with BR, so the behavior should be identical to BR behavior.

over 4 years ago - /u/RebelAndroid - Direct link

Originally posted by RisKQuay

When you say use your input to disable sprinting do you mean you need to push the stick in to toggle back to walking?

I believe so. I haven't looked through all the control schemes recently to make sure about how you toggle sprint/walking, but yes, as long as you are walking before you move forward you should be fine, so if that's press the stick to toggle walking and then move forward that should work (once 10.40 is released; currently controller input is breaking traversal emotes anyway). If you sprint, it will interrupt the traversal emote.