V I K O _ C A K E

Possible causes + resolvent

1. When the input method you use is ：Input.GetKeyDown(KeyCode.Space), You can try in Addforce Add parameters after the function ：ForceMode.VelocityChange, as follows ：

void jump()
    {
        if (Input.GetKeyDown(KeyCode.Space))
        {
            rb.AddForce(Vector3.up * force,ForceMode.VelocityChange); //1
        }
    }

2. With the above differences , When the input method you use is ：Input.GetButton(“Jump”) The following code does not need to add parameters , It should be noted that Input.GetButtonDown(“Jump”) It can't be

if (Input.GetButton("Jump"))
        {
            rb.AddForce(Vector3.up * force); //1
        }

3. If the code is rewritten as effective as the above code, it still has no effect , Try checking Rigidbody Whether the component has dynamic rigid bodies turned on ( Use AddForce This option cannot be turned on )

4. Code logic problems , When you check all parts but still have no effect, you can try to test whether there is other logic in the code . For example, the author adds a judgment to judge whether the character is on the ground , This leads to logical problems ：

private void Update()
    {

        // Jump monitor 
        if (Input.GetButton("Jump") && canJump )
        {
            ani.SetTrigger("isjump");
            rb.AddForce(transform.up * jumpForce);
            canJump = false; 
        }
    }
private void OnCollisionEnter(Collision collision)
    {
        if (collision.gameObject.CompareTag("Ground"))
        {
            canJump = true;
        }
    }

When you simply read the above code, you will find Update Medium Addforce Method will only execute One frame , It looks like Addforce No effect , This is obviously not in line with our expectations , How to modify , You guys can modify it as follows ：

private void Update()
    {

        // Jump monitor 
        if (Input.GetButton("Jump") && canJump )
        {
            ani.SetTrigger("isjump");
            rb.AddForce(transform.up * jumpForce);
            //canJump = false;  This sentence cannot be used here 
        }
        if (Input.GetButtonUp("Jump"))
        {
            canJump = false;
        }
    }
private void OnCollisionEnter(Collision collision)
    {
        if (collision.gameObject.CompareTag("Ground"))
        {
            canJump = true;
        }
    }

It involves API And analysis

1. For the first and second reasons , The author is looking up relevant materials GetButton and GetxxxDown The difference between the two is that they return true Duration ,GetxxxDown It will only return at the pressed frame time true, and GetButton Will return during pressing true.

And why right AddForce After using parameters GetxxxDown It can also work ？ First, according to logic , Use GetxxxDown It will only be executed for a short time , Therefore, the effect of parameters should work in an instant, rather than gradually changing with the implementation .

Unfortunately, the official documents do not explain this ForceMode Some characteristics and differences of . The above pictures are translated as ： The acceleration , impulse , Speed change . After testing, impulse and speed changes can take effect instantly .

2. For the third case , In official API It is described in ：

It should be noted that the active state here does not mean that the object needs to move , It's the object itself Setactive attribute .

3. For the last logical problem mentioned by the author , There are many ways to write code , Can't take into account all possible situations , The author here shares the method of personal testing process , The first is to use more Debug.Log Method , Used to judge whether the code is executed smoothly , The second is to delete , Delete some logic , Test again if the function is normal , This method should be very easy to use for finding problems .

If it helps you , Can you like it ~(●ˇ∀ˇ●)