Hover Platform Thingy

[Nophysicalbody]

Well, Lately I've been obsessed with this idea.
My idea consits of a 4x4 metal phx plate, which, by use of a set of hoverballs, rangers, and expression gates, stays a set distance away from the ground, on each corner.
I have explained it very badly, but what you're supposed to get is a plate that conforms quite accuratly to the ground underneath it.
Now, after i unfreeze the plate, the four hoverballs glitch, and the whole assembly spirals up in a messy spazz.
I have had success with a single ranger, expression gate, but It's not very "accurate" and it tends to crash on sudden slopes.
I thought that it might have been becuase when I'm building it, the hoverballs i wire up first tend to start working before the others- so i added a multiplication and a button.
The expression I've been using is:
<div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-spacere;overflow:auto'>
Inputs: Ranger Button
Outputs: H
R = Ranger * Button
A = R > 120
B = R < 100
H = -A + B
</div>
"Ranger" is obviously, the ranger,
"Button" is the button,
H is the hoverball velocity thing.

As i said, I have explained it pretty badly, but if you understand it, could you help me with this?
(Ps. it seems to be a craze to put "thanks for the expression gate!" at the end of these posts, so thanks for the expression gate!)

[Ikkonoishi]

I know exactly what the problem is I think.

When you have the object frozen in place the hoverballs are constantly recieving the Z velocity from your expression gate.

Because R is always less than 100 when the button is pressed B is always 1.

So all that time the hoverballs are trying to hurl themselves further and further downwards as fast as possible. As soon as you unfreeze it they pin themselves to the ground.

I&#39;ve had the same problem attempting the same thing since it is impossible to get or set the target height directly so you have to hope that the ball is near where it wants to be. Otherwise it is just churning its wheels so to speak.

I think this would be a better code setup since it precludes any movement by the hoverballs while the buttons is unpressed. The button should always be pressed when the object is frozen.

<div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-spacere;overflow:auto'>R = Ranger
A = R > 120
B = R < 100
VEL = -A + B
H = VEL * Button</div>

[Tad2020]

If you want to be cheap, hover drives do this.

[Nophysicalbody]

I know exactly what the problem is I think.

When you have the object frozen in place the hoverballs are constantly recieving the Z velocity from your expression gate.

Because R is always less than 100 when the button is pressed B is always 1.

So all that time the hoverballs are trying to hurl themselves further and further downwards as fast as possible. As soon as you unfreeze it they pin themselves to the ground.

I&#39;ve had the same problem attempting the same thing since it is impossible to get or set the target height directly so you have to hope that the ball is near where it wants to be. Otherwise it is just churning its wheels so to speak.

I think this would be a better code setup since it precludes any movement by the hoverballs while the buttons is unpressed. The button should always be pressed when the object is frozen.

<div class='codetop'>CODE

<div class='codemain' style='height:200px;white-spacere;overflow:auto'>R = Ranger
A = R > 120
B = R < 100
VEL = -A + B
H = VEL * Button</div>[/b][/quote]

That sound great! I&#39;ll try it tonight-