After applying ProcHit to a bone, other bones down the chain lose collision

[DemonicArthas]

After finding/hitting a bone through LineTrace and applying HitReact function to the said bone, the other bones below it (but not the one that got hit) lose their collision. For example, I shoot the lower arm just fine, then after shooting the upper arm once, lower arm is now invincible.

Video Demonstration

Sometimes the issue isn't present somewhere very far down the chain (I assume on bones that weren't actually hit). Works with any profile, with or without bone data. The issue is completely gone if I'm not applying HitReact.

[DemonicArthas]

I'm using Unreal Engine 5.5 and pre-compiled release of ProcHitReact for that version.
Physics asset is standart, automatically generated by Unreal for Unreal Engine 4 (Mannequin) skeleton.

[Vaei]

I'm unable to reproduce this behaviour. The turrets in the demo map never become unable to shoot a bone like that. I will require clear reproduction steps to be able to look at it.

[DemonicArthas]

1. Create a new project (or use whichever one you like);
2. Add ProcHitPlugin;
3. Add a Trace function from your camera inside the playable character of your choice (I've used ThirdPersonCharacter from the template and did a sphere trace for easier visualization). Or do the trace in any way you prefer. Just ensure it's set to visibility or camera (but that one is ignored in ProcHitCharacter) so that it can actually hit the mesh;
4. If said trace hits an actor, cast to ProcHitCharacter (or use an interface) and activate the TakeProjectileShot function;
5. Change ProcHitCharacter collision mesh so that it can receive traces (PhysicsActor preset is fine);
6. Drag'n'Drop ProcHitCharacter on the scene;
7. Start the game and shoot a trace at ProcHitCharacter in his lower arm to confirm everything works correctly;
8. Then shoot upper arm and then try a lower arm again. The trace goes through;
9. Shoot some more to confirm. Try shooting lower body and then upper body or head. Shoot upper body and then upper hand, etc. It's somewhat inconsistent, but bugs out very quickly

Video

Can't attach a project, it's around 1 GB with all the demo stuff, but I can upload it somewhere if needed.

[DemonicArthas]

After some more testing, it might be visual discrepancy between the character model and the actual hitbox/physics asset. After shooting for a while, I've noticed you can't hit the actual model, but some empty spaces are now being hit.

[Vaei]

I won't have time today to investigate but you could use this plugin: https://github.com/Vaei/SimpleAnimation

Specifically the function: USimpleAnimLib::DrawPawnDebugPhysicsBodies - call on tick

These will draw the physics bodies so you can see what they're doing vs the mesh

Enable for both server and local, see if there is any clue there. It is possible you're tracing on server that doesn't match local?

[DemonicArthas]

It's local singleplayer, no multiplayer involved.
It seems like that was, indeed, the problem.

Physical Asset is going bonkers (or, rather, hanging like a lifeless puppet) and never comes back after being hit once, while the actual model is behaving normally.

[Vaei]

I have reproduced it. I'm not sure how/why that can happen. I'll look into it when I find some spare time.

[Vaei]

I'll leave it open until I have solved it

[Vaei]

I did some digging. There are two issues. There is a rounding issue causing blends to remain active when they shouldn't. Once that is fixed the other issue should be a lot less severe. The other (main) issue is that the physics asset is applying full blending only to the asset itself if physics are simulating and its ignoring my blend weights. I don't have much time to do more atm, but I wanted to figure out the full scope of the task.

[DemonicArthas]

Hey! Was this ever fixed?

[Vaei]

Have had too many other priorities sorry, not yet

[NODARYN]

I'm facing the same problem.

[NODARYN]

I downloaded the old version of the plugin (commit c491674) and noticed that this problem does not occur on this version of the plugin. I will continue my research and let you know if I manage to fix the problem.

UPD 1: I found out that the changes in commit 3ce3a1f are causing this problem.