[Floating Pad]: Need help with sensitivity

I am having trouble getting my floating pad to do what I want it to do. What I am trying to do is make it so that my floating pad stays in one position and slightly tilt to the sides if the player is standing closer to the edges. However when I am trying to do this, my pads are either wayy to sensitive and go all over the place or the pads don’t move at all. I need some help getting my pads to be just right but I am not sure how to fully work AlignPosition and AlignOrientation.

Photo:

Video:

Model:
Pad.rbxm (12.5 KB)

Bonus question:
When I want to disable the pad, how can I make it float slightly downward to the ground with less force? When I change enabled to false it just free falls. That is not what I am looking for.



Take the mass of the model (mass of model is called AssemblyMass and is located inside any part inside the model that is welded to other parts I guess) and multiply it by the gravity of the the game. Gravity is located in the properties of workspace (which is 196.2 unless you changed it). This will give you the relative MaxForce required to allow your part to I guess, defy gravity. It’ll basically just float there until a player jumps on it, in which it’ll fall down.


11.2 * 196.2 = 2197.44, Change that to the MaxForce of the AlignPos.

Once you have that number down, you’ll need some extra force to take into consideration the player’s weight (I believe all R6 models have the same mass, with hats having no mass). I found adding 500 to the force makes it uhh, fally, I guess. You may want to add more.

One thing you might want to change for the AlignPos is the ForceLimitMode. Changing it to PerAxis allows you to control how much force is applied per axis (no duh). So if you want to make it fall down gently without swaying from side to side you can change the AlignPos ForceLimitMode to PerAxis and set the X and Z Force to a high number while having only the Y axis number be the required amount or a less number to make it fall down gently.


AS for the Orientation, I have absolutely no clue. It’s probably related to some other math thing but I can’t recall doing any math related to torque/angles. It’s also currently 11:00 for me so Ima go sleep and maybe update this post if I do remember some torque math blah blah blah.

If you need me to clarify something say so was typing this quickly so I can go sleep so I may have missed somethnig idk

I still dont understand because I tweak the values and anything I change it to does nothing what I want.

Have a similar setup with align position/orientation, this is how I’m doing it v

Part rbxm v
floatingPart.rbxm (5.5 KB)

Still need help. Can’t get the settings right

Adding onto my previous post agagaasduasksfjvuasdfj
(Forgot to set the settings for AlignOri so the thing is just gonna flail around)

As you can see, the part just floats there after setting the MaxForce to the Math thing I talked about earlier. Since it can only support itself, any slight touch causes it to, I guess, stop floating.

Code
-- You can do all this without using a script, just showing you the script to make it easier to visualize
local TweenService = game:GetService("TweenService")
local info1 = TweenInfo.new(3,Enum.EasingStyle.Quad,Enum.EasingDirection.In,0,true,0)

local Folder = script.Parent

local model = Folder.Model
local Follow = Folder.Follow
local AlignPos = Folder.AlignPosition
local AlignOri = Folder.AlignOrientation
local MoveTween = TweenService:Create(Follow,info1,{Position = Follow.Position+Vector3.new(0,5,0)})

local Gravity = workspace.Gravity -- 196.2
local AssemblyMass = model.PrimaryPart.AssemblyMass -- Assumes Model has PrimaryPart set, 48.125
local MaxForce = model.PrimaryPart.AssemblyMass*Gravity
AlignPos.MaxForce = MaxForce -- 9442.125

model.PrimaryPart:SetNetworkOwner(game.Players:WaitForChild("iATtaCk_Noobsi",100))

while true do
	MoveTween:Play()
	MoveTween.Completed:Wait()
	task.wait(1)
end

As such, to combat this, we add an extra amount of force to the MaxForce to fix that problem and make it fally.

AlignPos.MaxForce = MaxForce*1.017 + 400 

the amount of force you add is honestly pretty hard to find since the more AssemblyMass you have, the more mass you need. For the most part adding 400 to things that don’t have much AssemblyMass tend to work.

If you only want the Model to move up and down only so you can avoid this:


You can simply change the ForceLimitMode of the AlignPos to PerAxis and set the Y value to the specified value and the other axises to math.huge()

local AlignPos = Folder.AlignPosition
AlignPos.ForceLimitMode = Enum.ForceLimitMode.PerAxis
AlignPos.MaxAxesForce = Vector3.new(math.huge,MaxForce,math.huge)
-- math.huge is pretty much infinity


Now for AlignOri, again, still no clue. Since torque also depends on the length you’re standing from, which makes it all the more harder to calculate. Honestly I’d just set the torque to the MaxForce and hope for the best.

local MaxForce = model.PrimaryPart.AssemblyMass*Gravity
AlignOri.MaxTorque = MaxForce

Really when you use AlignPos and AlignOri it just becomes a “get close enough” guessing game