Object not touching ground on moving

[Unitkiv]

I have attached this code to the Player Object for following the Ball Object:

public class LookAtFollow : MonoBehaviour
{
    public Transform mTarget;
    float mSpeed = 1f;
    private Animator animator;

    const float EPSILON = 1f;

     void Start()
    {
        animator = GetComponent<Animator>();
    }

     void Update()
    {
        transform.LookAt(mTarget.position);

        if ((transform.position - mTarget.position).magnitude > EPSILON)
        {
            animator.SetBool("IsMoving", true);
            transform.Translate(0.0f, 0.0f, mSpeed * Time.deltaTime);

        }
        else
        {
            animator.SetBool("IsMoving", false);
        }
    }
}

However when the Player Object is following the Ball Object, the Player Object stands a bit high off the ground and stops like this. The Player Object has got rigidbody. How can I fix to make it stay on the ground?

[Jean-Jacque_Jiquenschwees]

Is gravity active on the rigidbody?

[PraetorBlue]

@Unitkiv

transform.Translate(0.0f, 0.0f, mSpeed * Time.deltaTime);

You cannot mix Rigidbody with direct Transform movement like this. Moving the Transform directly bypasses the physics engine. You should be using FixedUpdate and moving the object via the Rigidbody.

[Unitkiv]

@PraetorBlue

You cannot mix Rigidbody with direct Transform movement like this. Moving the Transform directly bypasses the physics engine. You should be using FixedUpdate and moving the object via the Rigidbody.

How can I use FixedUpdate and move the object via the Rigidbody? Could you please give example? I’m still new to Unity.

[Kurt-Dekker]

@Unitkiv

How can I use FixedUpdate and move the object via the Rigidbody?

The Rigidbody method is called MovePosition()

With Physics (or Physics2D), never manipulate the Transform directly. If you manipulate the Transform directly, you are bypassing the physics system and you can reasonably expect glitching and missed collisions and other physics mayhem.

Always use the .MovePosition() and .MoveRotation() methods on the Rigidbody (or Rigidbody2D) instance in order to move or rotate things. Doing this keeps the physics system informed about what is going on.

Collisions in high speed without unity physic / rigidbody

You say you're not using 2D physics but you're using queries therefore obviously colliders. This IS using 2D physics therefore you need to use it correctly so here are some basic rules: Don't ever modify the Transform if using 2D physics components If you want a 2D Collider to move then add a Rigidbody2D and use its API to move it; many ways to do this. Rigidbody2D don't make it "unresponsive". If you want explicit control then set the body-type to Kinematic; it's what it's for. When you qu…

OnCollisionEnter2D not being called

That’s not related to body-type. You should never drive via the Transform. The main thing to understand here is that the Rigidbody2D role is to write to the Transform after the physics simulation, not the other way around. It acts as a proxy to the Transform because you want physics behaviour. Does “it work” if you write to the Transform and force the Rigidbody2D to read from the Transform? Yes! It works like that because otherwise it’d be reported as a bug and so we’re forced to “support” it.…

[Unitkiv]

Thank you…

I have set the code like this:

  if ((transform.position - mTarget.position).magnitude > EPSILON)
        {
            animator.SetBool("IsMoving", true);
      
            Vector3 positionToMoveTo = rb.transform.position + new Vector3(direction * mSpeed * Time.deltaTime, 0f, 0f);
             rb.MovePosition(positionToMoveTo);
        }
        else
        {
            animator.SetBool("IsMoving", false);
        }

The Player Object seems like is touching on the ground now (it just runs where it is) but it isn’t moving towards to Ball Object. How can I move the Player Object to the ball?

[Kurt-Dekker]

@Unitkiv

How can I move the Player Object to the ball?

Start finding out which lines in the above code are actually running, perhaps print out the value of the position you are setting, etc, just basic good old plan standard everyday debugging.

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.

Doing this should help you answer these types of questions:

• 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)

Knowing this information will help you reason about the behavior you are seeing.

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

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:

Coroutine missing hint and error

This is so unnecessary. Use the beauty and power of instantly and immediately putting a Debug.Log() statement into the very start of the coroutine, right at the top. Do this always at the very first sign of trouble or question in your mind. The instant you did this you would see “Oh man, this code is simply not getting run!” And you could LASER-FOCUS 100% your efforts on studying what you expect to run it, eg., the call location, and isolate why it is not running. You would look at literall…

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

[Unitkiv]

It highlights this code in Console : Vector3 positionToMoveTo = rb.transform.position + new Vector3(direction * mSpeed * Time.deltaTime, 0f, 0f); as having error: NullReferenceException: Object reference not set to an instance of an object.

I really don’t have an idea what to do about this.

[Kurt-Dekker]

@Unitkiv

It highlights this code in Console : Vector3 positionToMoveTo = rb.transform.position + new Vector3(direction * mSpeed * Time.deltaTime, 0f, 0f); as having error: NullReferenceException: Object reference not set to an instance of an object.

Oh good lord… all this was just a stupid nullref?! That’s such a common trivial error we have a pinned post!

How to fix a NullReferenceException error

https://forum.unity.com/threads/how-to-fix-a-nullreferenceexception-error.1230297/

Three steps to success:

• Identify what is null
• Identify why it is null
• Fix that