What's the difference between .AssemblyLinearVelocity and .Velocity?

[IFearTheSky (Sky)]

Title says it all, what’s the difference between .AssemblyLinearVelocity and .Velocity? I know that .Velocity is depracted but are there any differences between the two (eg. performance, accuracy)?

[VonsRevenges (Von)]

.AssemblyLinearVelocity is better for performance, accuracy and it is not deprecated too

[700000002 (Tenny)]

There are a few minor differences outlined here:

Release Notes for 464:

@tnavarts

What you should be doing, is just using the new AssemblyLinearVelocity property in the same places that you used to be using the Velocity property. Yes, AssemblyLinearVelocity has slightly different behavior, however, that behavior is what you probably wanted the whole time when you were using Velocity.

Specifically, AssemblyLinearVelocity has better behavior because it continues to work predictably even with a rotating object, while Velocity will wobble back and forth thanks to the rotation adding and subtracting from the effective velocity of the center of the object (objects tend to rotate around their center of mass, which is what AssemblyLinearVelocity is measured relative to, so rotation doesn’t affect it).

I find AssemblyLinearVelocity to be much more useful. For example, if a planet is revolving around the sun at 300 studs per second and I’m standing still on that planet, the Velocity.Magnitude of my HumanoidRootPart will be 300. With AssemblyLinearVelocity, it’ll instead read 0, because it isn’t blindly seeing how my position changes over time, it’s also taking into account relativity. From my perspective me and the planet I’m standing on are still and everything around us is spinning.

It also takes the assembly’s center of mass into account, among other things.

In conclusion, AssemblyLinearVelocity is a more realistic version of Velocity