Animate weapon not parented to character

Help and Feedback Scripting Support
#1

We are using the default Roblox animation system (well animations are made with Moon) and the weapon is attached to the character via a Motor6D between the weapon’s Handle and the RightHand

The problem with parenting a weapon to the character is that when the player zooms into first person, the weapon becomes transparent
Also, it just feels messy to me overall, and I’d iust like to completely avoid it

When the weapon isn’t parented to the character, only the character part of the animation plays: the weapon’s motor6d and other joints basically just act like static welds

If it is impossible, I will modify the Roblox camerascripts to blacklist the weapon parts from changing their LocalTransparencyModifiers

Thanks

1 Like
#2

As far as I know, you have to use LocalTransparencyModifiers.

2 Likes
#3

This is definitely an XY Problem. You’re attempting to avoid transparency modifications of your pseudotools by not having them parented to the character, which is a terrible workaround.

If you’re looking to have a pseudotool not adhere to the visibility that’s gained from the CameraModule, you will have to create a blacklist feature. Naturally, this will also require forking of the CameraModule if such implementations don’t already exist (which I believe they do not).

There are three ways I know how to get this done:

CollectionService: You can fork the CameraModule and include a line where any parts tagged with a certain tag will ignore transparency modifications done by the script. From there, you can just tag the parts and everything will be taken care of you by the modified CameraModule.

Internal Blacklist: Similar to CollectionService, except instead you can make full use of CameraModule (and furthermore the fact that its a ModuleScript) by having it expose transparency blacklist functions upon require.

External Control: You can have an external LocalScript that uses BindToRenderStep on a priority higher than the one used in CameraModule, which will set the LocalTransparencyModifier of the descendants of the pseudotool to 0. I generally wouldn’t do this, since I can fork the CameraModule itself and append relevant functionality in there.

As for animations acting like “static welds” when they aren’t parented to the character, this is because you animated the pseudotool while it was in the character (most likely). Animations adhere to a very strict object hierarchy - naming convention and ancestry/descendants are important.

Animations are simply modifications of Motor6D Transform properties. That being said, animations cannot suddenly hold references to parts that exist in your game or make any assumptions - that is why they need explicit naming conventions. They need a pathway to the Motor6D by name before they can change the Transform property. Simply changing the ancestor of the pseudotool makes all the difference in what happens when you run the animation.

Overall, I think it’s messier to move the pseudotool out of the character to void transparency, when you can have the pseudotool in the character and opt to create a blacklist feature.

1 Like