Filter unwanted mesh sockets

[Lopyl14]

Hey. Same question as I posted on the marketplace, but I thought you want prefere it here. I just have one question about one of its core feature. "Due to the fact that the system is scanning for a first matching skeletal mesh where defined sockets exist (etc...)". The system scans for the sockets we want to use without us having to do anything. Which means, if I have a duplicate of a weapon (Like, if i'm dual wielding the SAME source sword mesh), it's impossible for the system to know I want to use the sockets from the left hand sword, or the right hand sword. I understand that a workaround would be to have two different source meshes, as so : RightHandSourceSword with RightSockets, and LeftHandSourceSword with left sockets. This is a shame though, as there is no way (to my knowledge) to just have two different instances of the same source mesh, only with different sockets. You also can't use the "remove sockets" built-in unreal, as it removes sockets from the source mesh, not just from your current copy. So here's my question : Is there a way to implement an actor filter to filter out unwanted meshes before the socket scan without modifying the plugin itself ? If not, I guess it would be a cool feature in the future, as it would make any kind of multi-wielding much easier to setup ! Cheers

[rlewicki]

Hi! First of all, thanks for reaching out here, I appreciate it. 

I have encountered the problem you are describing in the past and in fact I have described this use case in the wiki: https://github.com/rlewicki/MeleeTrace/wiki#double-sword-attack

This is the only solution I can suggest for now. I’ll have a think about your proposed solution and will come back to you with any updates.

Cheers, Robert

2.06.2024 o 05:19 od @.***:

Hey. Same question as I posted on the marketplace, but I thought you want prefere it here. I just have one question about one of its core feature. "Due to the fact that the system is scanning for a first matching skeletal mesh where defined sockets exist (etc...)". The system scans for the sockets we want to use without us having to do anything. Which means, if I have a duplicate of a weapon (Like, if i'm dual wielding the SAME source sword mesh), it's impossible for the system to know I want to use the sockets from the left hand sword, or the right hand sword. I understand that a workaround would be to have two different source meshes, as so : RightHandSourceSword with RightSockets, and LeftHandSourceSword with left sockets. This is a shame though, as there is no way (to my knowledge) to just have two different instances of the same source mesh, only with different sockets. You also can't use the "remove sockets" built-in unreal, as it removes sockets from the source mesh, not just from your current copy. So here's my question : Is there a way to implement an actor filter to filter out unwanted meshes before the socket scan without modifying the plugin itself ? If not, I guess it would be a cool feature in the future, as it would make any kind of multi-wielding much easier to setup ! Cheers

— Reply to this email directly, > view it on GitHub https://github.com/rlewicki/MeleeTrace/issues/16> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/ACRKEWUKIXKS6HF52E3OYGDZFKFM5AVCNFSM6AAAAABIUVZ3P6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDSNBUGQ2DINY> . You are receiving this because you are subscribed to this thread.> Message ID: > <rlewicki/MeleeTrace/issues/16> @> github> .> com>

[matanshukry]

@rlewicki why not simply remove the "return" statement? That is, add the traces for all the meshes that matches the socket; so you would essentially run 2 traces, 1 for the left and 1for the right sockets - which is what we want.

Should be very simple as well - you only need to handle the ensureAlwaysMsgf (which honestly is quite annoying at this point anyway).

The return line I'm speaking about: https://github.com/rlewicki/MeleeTrace/blob/master/Source/MeleeTrace/Private/MeleeTraceComponent.cpp#L264