VR Expansion Plugin

[anonymous_user_650f1d25]

@;721066

That would be correct, you can manually grip any object by calling the function, but if you are working off of the template then the cleanest method would be making a weapon base class from a grippable mesh. is because the template character has a ton of checks and balances that it runs with grippable / interfaced objects. You could also just implement the interface in any object even if it isn’t one of the grippable base classes but it would involve more effort generally due to having to overload the interface functions.

All time I’ve been seeing mention of grippable mesh. I thought it was in reference to any static/skel mesh that could be grabbed. I just now realized it’s an actual component/actor type. Thanks! I’ll get my feet wet with basing children off a GrippableSkeletalMesh Actor Base Class.

@;721066

If you are just using attachment for your object holding instead of the plugin grips you are free to have a boolean for each hand “Is holding” or something of the sort and just end the climbing check early if true.

Got it. That makes sense. I manually copied over almost all the gripping/climbing logic, so I’m aware of all the checks. It is indeed a ton. I think it’d be best to not add any more checks to the gripping/climbing. I’ll stick with your first suggestion (using GrippableSkeletalMesh Actor for Base Class).

Btw, I didn’t see much, if any, info on bitbucket regarding grippable Skeletal/Static mesh components/actors. You got all kinds of secret stuff in plugin, it’s ridiculous.

@;721066

Regardless for the holstering itself, you shouldn’t have to do custom logic on each object, Base class “Weapon” with child “Weapon.HolsterHeld” and implement the holstering logic there, then you can freely make further children like “Weapon.HolsterHeld.Pistol” that just has different mesh and properties but doesn’t have to re-do all of the holstering and base weapon logic.

I’ve recently had bad experience working with embedded inheritance actors in RR mods. It’s made me lean towards just inheriting once. By custom I was more or less just referring to gun logic VS locomotion logic. I’ll rethink my approach with “Weapon.HolsterHeld.Pistol” in mind. Or maybe HolsterHeld.Weapon/Tool.Pistol-Lasergun-Rocketlauncher/Rocket-Parachute-

Thank you very much for your time! Extremely appreciated!