search

Avindr / MxM-IssueTracking

7 stars 0 forks source link

Character gets stuck. #133

Closed tadilj closed 2 years ago

tadilj commented 3 years ago

It seems that sometimes the character gets stuck.

MxMAnimator RootMotion On

Phenomenon:

The green arrow is fully extended, but the red one is not. I've tried various update rates.

Maybe it's because of this:

Perform a direction change to a direction close to directly behind. Less animation to turn right back?

I don't think this is a bug, it's probably a misconfiguration on my part.

Thank you very much.

LudiKha commented 2 years ago

I too have this, and it seems to be the same bug as I posted here: https://github.com/Avindr/MxM-IssueTracking/issues/130

@Avindr any update on tracking this down?

Avindr commented 2 years ago

I have some ideas that I'm looking into but no concrete solution just yet. Sorry

Particularly difficult because it only seems to do it in some animations sets which I don't currently have. If anyone has a basic setup that reproduces this, I'd greatly appreciate it. Would help to identify what exactly is going on.

LudiKha commented 2 years ago

My project is rather big and complex at this point, but will set up a reproduce project if @tadilj 's doesn't have one at hand.

LudiKha commented 2 years ago

I found a potential solution and hint to the origin of the problem here https://github.com/Avindr/MxM-IssueTracking/issues/130#issuecomment-952790686

Avindr commented 2 years ago

After getting an example project to test this I found it was indeed caused by coverage issues with cut clips. The trajectory got so far extended beyond the current animation that the gap to jump was very large. I managed to fix this by improving the setup by adding 'RuntimeSplicing' to the plant and start animations. The 'TrajectoryBlending' option on the MxMAnimator can help also but too much of it will cause poor responsiveness.

I found a potential solution and hint to the origin of the problem here #130 (comment)

I believe that issue 130 that you submitted is likely a very different issue altogether even though the outcome may appear similar. If you could provide a smaller version of your project that is cut down somewhat that would be very helpful.

I will close this one and continue tracking the issue with #130

vabichequer commented 2 years ago

Hi! So I've just encountered this problem in my code, also. I'm coding a custom trajectory generator and this is what I get: image

I've tried messing with the 'TrajectoryBlending' attribute in the MxMAnimator, but no dice. I've recorded 5 minutes of walking motion in a full suit also and no luck. The dataset I'm currently using is the one from Mixamo, provided in the demo scene. Any idea what is happening?

Cheers!

Avindr commented 2 years ago

Hi! So I've just encountered this problem in my code, also. I'm coding a custom trajectory generator and this is what I get: image

I've tried messing with the 'TrajectoryBlending' attribute in the MxMAnimator, but no dice. I've recorded 5 minutes of walking motion in a full suit also and no luck. The dataset I'm currently using is the one from Mixamo, provided in the demo scene. Any idea what is happening?

Cheers!

Hard to tell just seeing screenshot but It doesn't appear to be the same issue. This particular issue doesn't stop the character moving altogether but rather causes the character to get stuck (usually when changing direction) until input is changed again.

Not sure why your mocap wouldn't work, I'd have to see it to figure out what's up. As far as Mixamo goes, does it have transition animations? I find Mixamo is pretty terrible at best. If there is no walk forward start then the behavior makes sense and I would expect it to do just that.

Also if you haven't already, I recommend checking out the tutorial videos and documentation for setting up cut clips as there are some nuances to it.

Let me know what animations you actually have in detail. No need to continue on this thread though, you can either make a new one or PM me on Discord.

Cheers.

LudiKha commented 1 year ago

@vabichequer @tadilj in case you might still need a solution:

I've also had this happen to me, and I have reason to believe it's to do with "Next pose tolerance test", which can lead to a host of failures to find matches when configured in a certain way. See this post for more info:

https://github.com/Avindr/MxM-IssueTracking/issues/130#issuecomment-1304330600