วีดีโอ

Thanks, I believe that they did something to Foot Placement that completely broke them. I haven't personally been able to get it to work so I am thinking one of the HotPatches they released may be responsible.

Yeah I may be doing more videos like this in the future but honestly I will probably be doing them around State Trees. State Trees are going to be the way to go, they are modern and Behavior Trees will never be as Flexible as State Trees have already become.

@@unrealdevop Thanks for the insight! As a beginner in Unreal Engine 5, I wasn't aware of State Trees. Now that you've mentioned them, I'm very interested in learning more. It would be fantastic to see videos about this modern approach. Looking forward to your future content! Best regards.

@@ganzukc2676 Yeah I have a series where I go over a really complex combination of State Trees and Smart Objects. I did have to use a few hacks to get things working though because in 5.4 there are still several issues that I believe should be mostly worked out now in 5.5

Yeah this is an evolving project, I believe I pretty much got it in a state where I plan on keeping it. I'll eventually go back and redo these videos but it's going to take some time. I have a lot of paid work right now I'll need to get adjusted too before I start considering that.

If it's the error I think then you need to go to the Motion Matching node and Refresh it.

You don't, you have to modify the pose so that it's in the pose or animation the bone is oriented and positioned correctly. Even if you adjusted it's orientation it's positioning will likely differ between guns, you could take all of your guns and re-orient their origins so that you don't have to do that but it wouldn't be appropriate in my opinion. Even if you did do that with all your guns you would be making it more difficult then what it would probably need to be.

Odd, seems that it works for everybody but you.

I'm assuming your using an altered version of the Game Animation Sample Project. I did this in an Unaltered version, I did try this again today in an Altered version and it did what you are describing. I'll try and recreate this again to make sure it's working and that I didn't leave something out and I'll try to figure out what may be causing it to not work.

I looked into it and accidentally fell into the same trap you apparently did. I assume you DUPLICATED the Character Blueprint....this is a Mistake, the Animation Blueprint is Casting to the other Blueprint and so it will always fail. That's why your character is sliding, it happened to me too and it took me like 30 minutes to realize why....this is why I hate it when people Cast to Blueprints.

@@unrealdevop Is there a way to fix it? Or a work around?

@@Uchidan There are a few ways, you could setup a Blueprint interface to pass all the data needed from the reference to the Animation Blueprint, removing the need for a Direct Cast and therefore removing it's dependency on a specific Blueprint....or you can duplicate the Animation Blueprint and replace it's Direct Cast to the CBP_SandBoxCharacter with the one you duplicated....if you do that though then you will also need to duplicate the Choosers that are evaluated because they directly reference the ABP_SandBoxCharacter animation instance and so you'll need duplicates of them that point to the correct Anim Instance so that later when you try to compile it or run it outside the editor your AnimBP's don't stop working for some odd reason.....because the thing they are referencing isn't the thing that is being passed to them for Chooser Evaluation.

Yeah a lot of people seem to want first person. I've mostly been focusing on working out all the problems with the system before expanding it.

Just as a side note: Most people making these projects are focused on quantity over quality. They are more about the Wow factor and drawing people in, but when you open up their logic you realize it wasn't really thought out and they were just slapping stuff together as fast as they could without putting any real thought into it. Also I've been really busy and going through a bit of burn-out so I'm still struggling to find both the time and desire to work on this project further.

Just realized you weren't referring to my DAO Project

The ALS AnimBP did have Multithreading enabled. Not sure about your claim though, Motion Matching Extracts Root Motion from the Animation, it's not the same as playing a Root Motion animation where it drives your capsule. These two things are very much not the same.

As far as what you seen on the Game-Thread, anything executed from the Event Graph in your Animation Blueprint does in-deed get executed on the Game-Thread, it won't be moved over into the Worker-Thread unless you move it over to the Thread-Safe Update. What you seen was the Raw Logic that Drives decisions in the AnimGraph being executed on the Game-Thread, and only that logic was being executed there. You totally misinterpreted what I showed in the video, I guess I assumed too much and should have explained this in the video. Moving ALS logic over to a Thread-Safe Update and not doing the same for the Motion Matching Logic would have been like me giving somebody a 5 second head start in a race. I would be intentionally loading the results in their favor. In Neither case were either of the AnimGraphs for Either of the AnimBP's showed in this Example running on the Game-Thread because Anim Graphs can't be executed outside of the Worker-Thread. Regardless if you have Multi-Threading enabled or not. If you don't believe me then you should really go look through the Documentation. It explicitly says this.

@@unrealdevopMy apology. I didnt watch your prior videos so I'm not sure about your ALS setup. Are you sure multithreading is enabled? The animations contain Root motions and if your ABP didnt set to ignore root motion, the multithreading won't be in effect. When I profile massive number of characters, the timeline doesn't look yours. The mesh and animation updates are segmented and run in batches of parallel tasks

@@koctf3846 Yeah so I believe a lot of people misinterpret that Multi-Threading option in the Class Settings. That tooltip can be misleading because it mentions Native Update and executing it on a Worker-Thread. What I believe they are actually referring to is the actual update of the stuff you see on the AnimGraph, that's the update they must be referring too. Anything on the Event Graph will still be executed on the Game-Thread. As far as your question goes, by default when you bring a project into Unreal Engine 5 it will automatically be set to use Multi-Threading. So in the case of my example, yes it was Multi-Threading on both. For it to not do that in Unreal 5 you would have to explicitly go into the settings and turn it off. I'm not sure what you seen but I'm under the assumption you misinterpreted that data. It's not difficult to misinterpret things in Unreal Engine.

@@koctf3846 As a final note I will say that neither of those animation blueprints were taking advantage of the Blueprint Thread-Safe Update, that would move those calculations over to a Worker-Thread which would reduce the impact it has on Game-Performance. With the Game Animation Sample Project I've done this in my own variant (Note NOT the one I used in this Profiling Video) of it but there were somethings such as the Console Commands they were executing and the Manual Calculation of their Trajectory which I was unable to move over to the Worker-Thread. I haven't looked into doing that for ALS but I assume much of that could be moved over. Just remember that ALS pre-dates the Thread-Safe Update introduced in 5.0

Yeah so I believe right now in 5.4 the Foot Placement node may actually be broken, I haven't been able to get it to work either. I think they may have tried to make changes to it in order to adapt it to the new method they release with the Game Animation Sample Project (Offset Root Bone) and in doing so actually broke it. If your using 5.3 and it's doing that though then it could likely be do to something else. Have you tried it in the 5.5 Preview? I haven't tried it in 5.5 Preview to see if it's fixed. I have a Discord in the description you can join if you want to talk about this further.

@@unrealdevop Thanks! I would like to join, but recently I don't have time to test it in 5.5 preview

@@gavinxu1622 I'll test it later today and get back to you.

lol

Yeah I've already got my side of the code mostly replicated, I'm waiting on the guys at Unreal Engine to release their Replicated version of the Motion Matching Sample Project because for me to do it properly like them would require me to release a modified version of the entire Unreal Engine Source Code. The replication I have provided only currently works with hacky workaround plugins that create massive server crippling traffic by replication arrays of 40-80 large structs being sent for every character in the game across the network. You can imagine how heavy sending an array with 40-80 large structs packed full of data across a network would be....it's a rather dumb way of handling the issue. Unreal's version won't comprise of such a simple-minded approach to replicating the Motion Matching Movement......I've been having people ask me to replicate it since I first revealed the project though....just give it another 1-2 months and you guys won't have to worry about that anymore.

Might check to make sure the character you are performing this on has a Motion Warping Component and that you have set the Motion Warping on the Animation Montage. If it's a Sequence playing on the Anim Graph or it's being selected for Motion Matching like a regular Locomotion Animation then it won't work. The Motion Warping Targets normally have to be set manually unless your doing it from a State Tree and your using that node....however some things have changed in later versions and some things have been broken in later versions. Make sure that the names match between the Anim Montage and wherever the Motion Warping is being handled. That's about the only advise I can give you, if it's not one of them things then it's almost impossible for me to help you without looking at it myself and I don't do that for free because too many people would be bothering me for help and I stay pretty busy.

@@unrealdevop Thanks you for the answer. FInally it's a bit deeper issue. As I am working with Mass Entity, my AI character doesn't have AI Controller and doesn't belong to this. It is fully driven by Mass. It seems root motion is not correctly applied on characters without AI Controller.

@@Alex-qh8er Have you seen my latest video? I'm not familiar with Mass Entity, it's actually something i haven't even taken the time to look at yet. However, if it's Motion Matching Related then it's probably a commonly overlooked checkbox that I cover in that latest video.

I have a deep voice, it's biology and I have no control over that. If you don't like my voice, you don't have to watch my video's

Watch some tutorials about behavior trees and ai controllers, they will help.

@@0UTSIDER thanks.

Yeah so some people will tell you to use Behavior Trees, I've had experience with both....and I'll tell you now that Behavior Trees are very RIGID and difficult to perform Parallel Processes together, there are a myriad of approaches to doing that with Behavior Trees but a lot of them are rather hacky and the Simple Parallel that is provided with them does not work for every situation and will bug out if you try to use it in certain ways.....the point is that it's ability to run things in Parallel is very limited. State Trees are modern and designed around Modern Needs, they don't have any of the Weaknesses that Behavior Trees have and are far more flexible because of that. You can run Multiple things in Parallel from my Understanding (I Have not fully tested the extent of this quite yet). In a State Tree you would have the Parent of the Attack run the MoveTo function and a child of it would execute the Attack Logic.....you could also have an Entirely Separate State Tree Performing Movement Functionality and run it as a Parallel Tree that executes while doing other things under it. This is something that would cause all kinds of conflicting problems were you to try doing it in an Archaic Behavior Tree.

Just to clarify it a bit more from my last statement. In regards to Behavior Trees - you can run things from a service....and some people opt for Behavior Tree / Blueprint Separated Logic for handling Parallel. I personally don't like that Separation that is required for handling things that the structure and design of Behavior Trees simply fail to achieve on their own. That is why I have chosen to Abandon Behavior Trees and Go all in on State Trees. If you have ever tried to develop a sophisticated Cooldown based system with Behavior Trees you'll begin to understand the real limitations of the Behavior Tree.

Yeah for sure, appreciate your feedback.

Nah it's just normal fog, but if you want it to look thicker like that lower to the ground you can just adjust it's height offset, depending on where your map is located in space you may need to lower or raise the actual fogs location in the world to get a similar effect, of course you would also need to adjust the actual settings of it too....but a lot of people are unaware that the actual Z location of the fog has a direct impact on how it appears as well.

Yeah of course.

Yeah they use the Attach Bone and they position it during animation creation at the point where the object they are traversing is. They then have the Motion Matching System match against that. If your playing it as an Anim Montage with Root Motion enabled then there is no reason why your character should be snapping back unless the last from of the animation ends at the starting position. I'm assuming you root bone is following the character through the air rather then the Pelvis simply leaving it behind. In Pelvis based animations, the pelvis transforms are normally transferred to the Root so that it follows along.

@@unrealdevop I only mentioned disabling the root motion because when it’s off the animations align with ledge. But when root motion is enabled it’s above the debug capsule spheres. I am going to retarget fresh animations and triple check the attach bone.

@@michaelderosier3505 Yeah, I'm just not sure exactly what it is your trying to do over there. May be best to join the Discord and just show me in a Live Stream.

Appreciate the feedback, I'll eventually get some transitions setup in there for the weapons.

Yeah, so the Offset Root Bone can only help so much. It seems like the animations need to be done a specific way for it to even completely work. There is another possible approach too but it could potentially be expensive. It involves a Distance Matching Approach. There is a guy who's working on a plugin which adds distance matching to the Steering Node and from what I've seen it works rather well, but he's still stuck on some problems with it that have yet to be resolved.

Yeah for sure. It's been rough working out all the issues I've ran across.

@@unrealdevop what would you say was the biggest hurdle in this project?

The Aim Offset actually....I kept trying to figure out how to get rid of the jittering and hitching....I've reduced it about as much as I can....without speeding up the turn rate of the turn animations, which I have little control over without manually modifying each animation responsible for turning....I can't actually reduce it any further then I have without allowing the spine to rotate more then 90 degrees which is obviously impossible for a human to do and even if I did it would be like twisting a balloon, the weights simply can't hold up the mesh under that much pressure

Oh lol yeah...I've been a bit off the past 3 weeks.

Thanks for the input

Yeah I get a bit too excited and spam them sometimes lol.

I'll continue developing it for some time. This project is really meant as a learning project for me and others.

On which version 1.27 or the one I just pushed 1.28?

and for the 5.5, it have 3 new Selection Behavior, one is the "Try Select Children At Random" I cant get it to wrok.

I haven't explored State Trees in a minute so I'm not really sure, I'll get back into them soon though.

@@unrealdevop thanks~

@@weijunchen1290 Yeah I'll look into it soon because I'm about to start setting up Ai in my Project under the 5.5 Preview. If I had to guess though it probably activates something based on a Gameplay Tag or jump too it, assuming your not referring to an actual State Condition for Entry.

@@unrealdevop that's what I though too, but don't know how to use it.

I've kind of got my hands full with a lot of stuff right now, but perhaps I'll do a video on something like that in the future. I have done a video on Physical Animation in the past if you want to go check that out.

@@unrealdevop ok thanks, looking forward to it

Yeah I left it up for those who just want a quick fix. Perhaps I'll eventually do another video on that, the problem with the feet is really related to retargeting animations and the fact that IK bones are displaced. I've stopped using IK bones and I just use virtual bones in their place now, especially for feet. However doing this in ALS may require a value to be adjusted since they use a dynamic foot adjustment method for correcting feet during foot locking.

It's hard to say without seeing it, if he's falling through the floor then it could be that collision is being disabled. If the capsule is staying above the ground but the character is going through the floor then it could be that an animation needs Force Root Lock Enabled. If that's checked then it could be a problem with the animation if it's the case that it was retargeted.

@@unrealdevop thank you for the tips!

@@unrealdevop It was the retarget. The root bone information did not transfer correctly. Thank you again

@@michaelderosier3505 Oh, glad you found the problem.