As a Roblox developer, it is currently too hard to make LinearVelocity apply velocity relative to an external attachment.
I recently discovered that when LinearVelocity.RelativeTo is set to Attachment1, the constraint will apply forces to both Attachment0 and Attachment1 to achieve the relative velocity. This is really inconvenient when Attachment1 is a part of a separate assembly.
I’m working on a wind ability where a wind tunnel can be aimed in any direction to push other players. The tunnel itself is just a part controlled by AlignPosition and AlignOrientation. When a character is inside the tunnel, I create a LinearVelocity with Attachment1 set to an attachment inside the tunnel part. This way, characters being pushed are always pushed in the tunnel’s current direction. However, due to forces also being applied to Attachment1, the tunnel itself is affected by the LinearVelocity which has undesirable effects.
The ability working: https://gyazo.com/9ba5bec147821fa1244a214c278acbc6
The ability not working: https://gyazo.com/33230abb800b17f3280f67b8c6072d9d
(I’m fairly certain the sudden change in direction is caused by the force applying to the tunnel instead of the dummy. I debugged for hours ruling out other causes)
I always assumed LinearVelocity only affected the velocity of Attachment0, and I’m surprised this isn’t the case. I think it would be great to have an additional property that explicitly determines which attachment(s) will be affected by the constraint.
If Roblox is able to address this issue, it would improve my development experience because LinearVelocity would be a much more versatile constraint. Thank you