Of course, and it's coming soon.

@@tareqgamedev Great to hear, Thanks man

Unfortunately, I do not have much experience with multiplayer coding, but maybe in the future, I will consider creating a series focused on replicating a locomotion system for multiplayer games. However, this won’t necessarily be the same system, as I plan on developing a new one using Motion Matching.

I look forward to it.

Part 1 of the aiming system and part 2 are a continuation of the advanced locomotion series. In the video, I mentioned that you should watch the entire series to understand the code and the animation system in detail. I highly recommend viewing the whole series, and I guarantee that you'll have a clear understanding of everything afterward.

Coming soon!

I’ll definitely cover motion matching in future videos. For now, this series focuses on ALS because it’s a great starting point for understanding advanced character animation systems in UE5. Stay tuned for the motion-matching videos!

@tareqgamedev ohh ok, I shall look forward to it. Thanks for your hardwork. GGs

Thank you so much! I’m happy to hear that you enjoy the videos and find them useful. Stay tuned for upcoming tutorials!

Thank you for your feedback. The firing mechanics shown in this video are part of my free 2D gameplay mechanics pack, which includes editor scripting for quick and intuitive configuration. This system allows users to configure mechanics directly in the inspector without worrying about any complexities. For this video, I copied some variables from the pack and changed their access specifiers to private but forgot to remove the HideInInspector attributes. You’re absolutely right; those attributes are unnecessary in this case, and they can be removed. Regarding the input system, I completely agree that there are more efficient approaches. However, as I mentioned in the video, the focus of this tutorial is not on the new input system but on teaching the core firing mechanics. This video is aimed at beginners, and my aim is always to introduce fundamental concepts in an accessible way while implementing them whenever possible. For topics like object pooling, although Unity has a built-in system, I believe demonstrating a simple custom implementation can help learners grasp the basics. With this foundation, they can later explore and develop more advanced solutions if needed. I appreciate you pointing out these areas for improvement, and I’ll definitely consider integrating some of these practices into future tutorials. Thanks again for your feedback!

Sure! There will be more videos about different gameplay mechanics soon.

I'm not quite following the issue you're experiencing. Could you please send a video that demonstrates the problem? I’ve checked and tried rotating while looking at the floor, and the character seems to turn in place as expected.

😂 Haha, yes, "actual human skeleton" might sound a bit dramatic! Unity just needs a digital human rigged skeleton (the virtual bones and joints) to work with the Animation Rigging package.

Unfortunately, I don't have much experience in multiplayer programming. However, it really depends on your game. If you are creating a game with hundreds of players in the same room or level, managing this locomotion system for each character could impact performance. Such systems are usually better suited for single-player games. If you have experience in multiplayer programming, feel free to give it a try, and please keep me updated. I would love to see the results.

If you followed every step I did in the video, the strafing to both left and right should work as expected. If not, that means you missed something. Make sure to watch the video again and check that the values are correct by debugging them. Additionally, I mentioned in this video that this is not the final result. When you complete the whole playlist, you will see the final result. Although there are multiple features we can add to make the whole system look much more refined, such as pivoting, which I may do a video about soon.

@@tareqgamedev Thank you for your reply. My issue is that my result looks exactly as yours. Even in your video, I cannot see your character jogging leftwards. Is that a misunderstanding from my side? When your Wraith character moves to the left, he jogs backwards, even in your video. Is it supposed to be like that?

No, he doesn't jog backward. This is the left strafe animation clip. Please review the animation yourself before running the game. I am sure you will understand. The issue with jogging backward while strafing or jogging forward while strafing is because, as I mentioned in the video, we have not yet handled diagonal movement at this point. Watch the entire playlist for when we implement leaning and diagonal movement. This issue won't happen again because the blending between jogging and strafing will be handled differently.

Yep! It's just a verbal mistake.

Make sure to set the scale values for both "MoveForward" and "MoveRight" correctly as we did in the video at 20:50.

@@tareqgamedev I did, that's why I couldn't comprehend what's going on. In the end I found it, I did `AddMovementInput(ForwardDirection)` instead of `AddMovementInput(ForwardDirection, Value)`. I guess my eyes need a break.

Hey. It's not too difficult to achieve. You need to shoot a third ray starting from the hit point of the height ray and moving forward along the depth of the obstacle direction. Then you can simply check if the distance is larger than 1 meter, for example. You can then play a jump animation similar to how we played the vaulting animation. Otherwise, you play the vaulting animations.

Thanks man, the code could be similar to the height check raycast but in the horizontal direction

Sure, more videos on Unreal Engine and C++ are coming!

Glad you enjoyed it.

@KZbinrUser002 Unity is a great engine. Many AAA games are made using Unity. However, I also use Unreal Engine and C++ to create games and cinematics (you can check out my channel videos). A great developer should be able to learn any engine quickly. The most important thing is to know how to code efficiently and have excellent problem-solving and math skills.

Yes, that's correct! Someone asked the same question in the comments section before, and I answered it as follows. You can use the code snippet below as a starting point. When the ray hits the collider of the weapon, we acquire the current weapon. You can identify the current weapon by its name in the Equip function (make sure to rename all your weapons appropriately in the hierarchy so you can easily identify them in the code). Then, you should store the positions for both the right and left hands and use them as needed. You can use the provided code as a starting point. The list weaponsIKHandsPos will contain references to both hands' positions for each weapon you have. In the Equip function, after identifying the picked weapon, you can store the positions of both hands in the transforms IKRightHandPos and IKLeftHandPos, which hold the current weapon's hand positions. [System.Serializable] public struct WeaponsIKHandsPos { public string name; public Transform IKRightHandPos; public Transform IKLeftHandPos; } [SerializeField] private List<WeaponsIKHandsPos> weaponsIKHandsPos; private Transform IKRightHandPos; private Transform IKLeftHandPos;

Thank you! I'm really glad the video was helpful to you. Best of luck with your Ph.D. journey!

Hey, @harharrr9810! It's pretty straightforward. When the ray hits the collider of the weapon, we acquire the current weapon. Right? You can identify the current weapon by its name in the Equip function (make sure to rename all your weapons appropriately in the hierarchy so you can easily identify them in the code). Then, you should store the positions for both the right and left hands and use them as needed. You can use the provided code as a starting point. The list weaponsIKHandsPos will contain references to both hands' positions for each weapon you have. In the Equip function, after identifying the picked weapon, you can store the positions of both hands in the transforms IKRightHandPos and IKLeftHandPos, which hold the current weapon's hand positions. [System.Serializable] public struct WeaponsIKHandsPos { public string name; public Transform IKRightHandPos; public Transform IKLeftHandPos; } [SerializeField] private List<WeaponsIKHandsPos> weaponsIKHandsPos; private Transform IKRightHandPos; private Transform IKLeftHandPos;

How did it go?

@@SaschaRobitzki My 1650ti can't bear UE5.At least 5 min to compile

@@LostAngel175 Yeah, UE5 is definitely more demanding than Unity 6.

@@SaschaRobitzki

Yep! That's a great system. Right now, I have a couple of tutorials planned that I have been studying and working on. I will consider creating a tutorial about parry mechanics as soon as possible.