How to make Body Velocity to go down

Help and Feedback Scripting Support
#1

Hello, I don’t know much about Body Velocity I just starting to learn about it and I was wondering if it’s possible to go up or down with it. Is it Body Velocity or something else I need to do?

Here is my current code, rn it just goes where the mouse is but I would like it to go down a bit so it touches the floor.

-- // BodyVelocity
local BodyVelocity = Instance.new("BodyVelocity")
BodyVelocity.Parent = ItemCloner
BodyVelocity.MaxForce = Vector3.new(math.huge, math.huge, math.huge)
BodyVelocity.Velocity = (MousePos - ItemCloner.Position).Unit * ObjectInfo[UserData.Data.EquippedObject].Velocity

– // Notes
ItemCloner = The cloned object I want (It’s one object)

#2

The .Velocity property of BodyVelocity is a Vector3 value, just like a part’s position. As you probably know, Vector3.new(x,y,z) is the basic constructor for a Vector3 value. You can read up on Vector3 values more if you’d like, but I can give you a simple explanation for this issue.

Vector3 values can be treated very similarly to numbers in that you can perform arithmetic on two Vector3 values:

local VectorValue = Vector3.new(1,1,1) + Vector3.new(0,10,0)

This would result in a Vector3 value with the coordinates [1,11,1].

Applying this to your issue, if you want the velocity to go “down a bit”, then (assuming by down you mean along the Y-axis), you can simply subtract from the velocity at the end:

BodyVelocity.Velocity = (MousePos - ItemCloner.Position).Unit * ObjectInfo[UserData.Data.EquippedObject].Velocity - Vector3.new(0,5,0)

Notice that only the Y value is being subtracted because that’s the up/down direction in workspace. You can always change how much slower/faster it is by adjusting the number.

#3

Sorry I might of explained what I wanted wrong but thanks anyways! What I ment is when I click it throws an object then it goes towards the floor. like throwing a paper, it throws and goes straight then it goes down to the floor.

#4

So basically you want it to be impacted by gravity?

If that’s the case, you can actually change a different property of the BodyVelocity. The MaxForce property is what determines how much force can be applied within each axis.

Again, up-and-down movement correlates with the Y-axis, so you would want to change the value from math.huge to something smaller. Changing it to zero wouldn’t allow the object to move upwards even when being thrown, so it can’t be too small, but it has to be small enough to be quickly impacted by gravity.

You can play around with what numbers to see what works best. Eventually, gravity should overcome the velocity and cause it to move downwards. I’d start with something like this:

BodyVelocity.MaxForce = Vector3.new(math.huge,100,math.huge)

And then you can adjust the number to be higher or lower until you’re happy with the result.

Also note that you’d need to adjust this number depending on how much mass the object has, so if you plan to use the script on parts of different mass, you can use part:GetMass() with some math to adjust appropriately without having to hardcode it. But you don’t have to worry about this at all if you’re always going to be using this script on parts of the same size and material.

2 Likes
#5

At the 2nd argument of vector3, make it “-math.huge()”

#6

It’s still going straight, it aint going down at all.

#7

Could you send the new code? If the MaxForce of the BodyVelocity’s Y-coordinate is small enough, it should move down from the force of gravity if nothing else is pushing it upwards.

#8

I tried with a small object and it just goes straight and if I did it with a bigger object it goes no where it just stops soon as I press.

-- // BodyVelocity
local BodyVelocity = Instance.new("BodyVelocity")
BodyVelocity.Parent = ItemCloner
BodyVelocity.MaxForce = Vector3.new(math.huge, 100, math.huge)
BodyVelocity.Velocity = (MousePos - ItemCloner.Position).Unit * ObjectInfo[UserData.Data.EquippedObject].Velocity

Nothing really changed I’m still trying to figure out what you was trying to explain to me.

#9

The Y value of MaxForce (currently at 100) needs to be changed to a lower number if the movement doesn’t stop, and it needs to be changed to a higher number if the movement barely happens or doesn’t happen at all. That is what I meant by this: