# Rigidbody.Addforce... everywhere the same force value

Hi! I am working on a simple water physics script. Normally, the up-force should increase, if it goes deeper into the water. and if the physic point / position is outside the water, there shouldnt be any forces. I have no idea, why all the forces are the same. thanks for helping, Jonas.

``````    public Bounds[] FloatAreas;
public int physics = 4;

public float forcefactor = 1f;

Rigidbody rb;
AnimationCurve forcecurve;

// Start is called before the first frame update
void Start()
{
rb = GetComponent<Rigidbody>();
forcecurve = new AnimationCurve(new Keyframe(0, 50), new Keyframe(3, 50), new Keyframe(10, 1));
}

// Update is called once per frame
void Update()
{
foreach (Bounds bound in FloatAreas)
{
for (int i = 1; i <= physics; i++)
{
float diffz = bound.size.z;
float interval = diffz / (physics + 1);

Vector3 pos = new Vector3(0, 0, (interval * i) - bound.size.z / 2);
float posy = bound.center.y + transform.position.y;

float upforce = (posy * posy * posy * (rb.velocity.magnitude + 1) * forcecurve.Evaluate(posy) * -rb.mass) / physics;
upforce = Mathf.Clamp(upforce, 0, rb.mass * 25);

Vector3 worldForcePosition = transform.TransformPoint(pos + bound.center);
rb.AddForceAtPosition(Vector3.up * upforce * forcefactor, worldForcePosition);

Debug.DrawLine(Vector3.up + worldForcePosition, Vector3.up * upforce * 0.03f + worldForcePosition, Color.red);
if (posy < 0) rb.drag = 1f - posy;
if (posy > 0) rb.drag = 0.01f;
}
}
}
``````

First, I recommend NEVER using anything related to Bounds. It rarely works the way people expect.

If you insist on using Bounds, hereâ€™s how to debug it:

Welcome to debugging! Hereâ€™s how to get started:

First, simplify your data to perhaps two separate float areas.

You must find a way to get the information you need in order to reason about what the problem is.

Once you understand what the problem is, you may begin to reason about a solution to the problem.

What is often happening in these cases is one of the following:

• the code you think is executing is not actually executing at all
• the code is executing far EARLIER or LATER than you think
• the code is executing far LESS OFTEN than you think
• the code is executing far MORE OFTEN than you think
• the code is executing on another GameObject than you think it is
• youâ€™re getting an error or warning and you havenâ€™t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling `Debug.Log()` statements through your code to display information in realtime.

• is this code even running? which parts are running? how often does it run? what order does it run in?
• what are the values of the variables involved? Are they initialized? Are the values reasonable?
• are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as `Debug.Log("Problem!",this);`

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Hereâ€™s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

When in doubt, print it out!â„˘

Note: the `print()` function is an alias for Debug.Log() provided by the MonoBehaviour class.

1 Like