Video

What is the error?

@@KITATUS I fixed it, it wasn't in the header file, but somehow another error referenced the delegate variable as an error.

Did you include the #include for GameMode?

@@KITATUS That was the issue, thanks a ton !!

Performance-wise, there's no real difference, it's just one class broadcasting out a messing on a bound variable. For your use case there, if it is literally just this one use-case then a direct function might serve you better but if you plan to do something like "Puzzle complete" - then it may make sense to use the delegate system.

Yup! Anything you bind to a delegate should be called. All of them should be called, not just one of them. Are you sure the others are bound in time?

@@KITATUS hey! Thanks for yoir reply. Yes, they're all working now. Turns out, I had bound a delegate to a function in a begin play of a class. But it's begin play was not being called by it's child class! *smh 🤦‍♂️🤦‍♂️ It was a silly error that kept me up for 2 hours past my bed-time lol. Calling parent:begin_play (super) in the child class fixed it!

Did you figure this out? I'm having the same problem.

In C++? Can you show me your code?

I think I have the same issue as you. A brief flickering when the NPC's ragdoll activates. Have you found any way to fix it?

@mrtoyre No sadly

yes

maybe drop updated video?

By the sounds of it, you may need to update the virtual bones / bone names in use to use your skeletons bones / virtual bones and not the original. Using this approach, that original skeleton still exists, your new skeleton is just copying it. So you need to find in the code where those bone names are being called and direct them to your new skeleton :)

Have you checked the w ritten part to assist in the area you are stuck in?

@@KITATUS i dont understand the ( target mesh) where did i need to get this what is the name i need to type?

@@officialjmweh120m3 yeah, same ploblem

The written version available in the description should help.

Take it out. See if it breaks. It likely will, as it is the parent of the Metahuman but it might be worth playing with. With the mesh not visible, there wouldn't be any graphic overhead anyway.

The "Project" being ALS Community? I could spin up a tutorial on how to do that if that is what you are requesting.

@@KITATUS Yes please, that would be amazing. I am on the github page and have no clue how to install the plugin. If you could make a full beginner friendly tutorial from start to finish?

Which version of UE5 are you referencing? All of the code from this video and the written version in the description are from UE5. I have not seen the need to include "Delegate/Delegate.h" or the DelegateSignatureImpl in any UE5 version (5.0, 5.1, 5.2 or UE5-Main). MULTICAST delegates are touched on here instead of just DECLARE_DYNAMIC_DELEGATE due to not wanting to confuse a new user to concept of delegates and the fact that MULTICAST is a standard delegate on roids. The TL;DR differences between MULTICAST and standard delegate are: DECLARE_DYNAMIC_DELEGATE is used for defining single-cast delegates in Unreal Engine, which means only one function can be bound to the delegate at a time. DECLARE_DYNAMIC_MULTICAST_DELEGATE is used for defining multi-cast delegates, allowing multiple functions to be bound simultaneously, and when the delegate is invoked, all bound functions are executed. For most (if not all use cases) Multicast delegates are the preferred method as they give you more power and opportunities than a very binary singular Delegate, especially when dealing with complex systems in games. More bang for the same buck. Hope this helps.

​@@KITATUS 5.0.3 -when calling to Declare_Multicast_Delegate it's fine and this example works. The Dynamic delegates have serialization options. Your explanation of it in terms of normal calls is fine tbh. On the documentation page those includes are still listed when using Delegates. The example you showed is fine for the understanding of usage in a generic case. I was interested in why in many cases the normal cast works fine, but param ones mention an error in visual studio. I'm calling a few OneParams and Two Params, but it mentioned a definition missing concern. The includes I mentioned show a deprecated section for certain calls with those includes. They are listed in the search criteria, but implementation mentions a new conflict. I'm cross referencing between this vid, Ben UI topic on Advanced Delegates in C++, the unreal documentation and the Wadstein examples. Though I'll try a change on code side to confirm DECLARE_DYNAMIC_MULTICAST_DELEGATE_OneParam, DECLARE_MULTICAST_DELEGATE_OneParam I'll also check the TDelegate usage. Initially your Multicast One Param was commented out and the other call that does work was used. So let me double check some items.

It's a bit more tedious but should be possible. Once you've got the IK rigs, retarget the main Anim Blueprint (which should auto retarget the children) and try and recreate any references elsewhere. You'll have to adjust curves and whatnot that depend on the original mesh though.

It does not get crazy expensive like looping in an array would, you're most likely fine to take that approach. If you were really concerned about performance (or don't want to do "is it this? no then cast to this, is it this? no then cast to this, is it this" .etc) you could create an Interface and then you could either check if the actor has interface ("Actor has interface") or just directly fire the interface function (which would fail on actors that don't have the interface implemented). I hope that helps.

​@@KITATUS Good to know that casting is not that expensive, also already trying my best to use interface where ever possible and avoiding situations requiring loops. Thank you for all the free knowledge.

in ikr_als set the preview mesh to Anim_man

@XBcreations Not a super noob-friendly tutorial, then. All good I made my own IK rig from scratch. 👍

Original is a marketplace Blueprint project, Community version is a C++ version of that blueprint project aimed at improving performance and fixing bugs. The community version is made and maintained by the community and not the original creator.

@@KITATUS thanks) is this tutorial can be used on original version?

The overlay states still work as intended but it should be noted that they'd be using the original meshes transforms .etc anyway so they'll be offset. You can go into the overlay state code itself (exposed and implemented in Blueprint) to adjust the target to the new mesh.

I would wait an official 5.1 version but if you can't wait, edit the .uplugin file with your text editor and change engine version to empty instead of "5.0.0" - ensure the project this plugin is installed to has any c++ in it so it can force recompile the plugin.

@@KITATUS Ty im gonna try.

@@CsGrinders Let me know if it doesn't work and I'll investigate.

Nvm, I saw someone commented it as well.

Wow, great tip! I'll append the written version (with credit for your contribution) - thanks!

Once I set visibility to off, it was no more working. So I got to go back to transparent material.

@@koko-nl5tp you have to enable anothee option after that for it to work when it's not visible, it's in my comment too

@@gambello1195 My bad... Thank you to your reply.

wow man ...both variant are good but better a default engine one instead of tricky matherial :D ....thank you both for tips :D

If you didn't come off like a jerk I would tell you

3d scan it

You can customise every preset in the MHC, also look up Mesh 2 Metahuman!

Make it in UE5 then use it in UE5.1. That is what I do. Take it easy. It is on its way. You knew it. :)

you can 3d scan your face and then use it as a metahuman