Input.GetAxisRaw("Mouse X") is too chunky

[derfetteboss]

Hi,
is there any way to make Input.GetAxisRaw(“Mouse X”) less chunky? Or do i have to change to the new Input System? Because my players y rotation is only going in 0.175 steps (i think). Below is the mouse part.

Thanks!

[SerializeField] float Sensivity = 3.5f;
private float mX, mY;

private void FixedUpdate() {
        mX += Input.GetAxisRaw("Mouse X") * Sensivity;
        mY -= Input.GetAxisRaw("Mouse Y") * Sensivity;
        mY = Mathf.Clamp(mY, minRotation, maxRotation);

        transform.rotation = Quaternion.Euler(0, mX, 0);
        camHeader.localRotation = Quaternion.Euler(mY, 0, 0);
    }

[Kurt-Dekker]

@derfetteboss

(i think).

Luckily it isn’t necessary to guess. You can debug!

By debugging you can find out exactly what your program is doing so you can fix it.

Unity - Manual: Debug C# code in Unity

Use the above techniques to get the information you need in order to reason about what the problem is.

You can also use Debug.Log(...); statements to find out if any of your code is even running. Don’t assume it is.

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

@derfetteboss

FixedUpdate

Don’t use FixedUpdate() unless you’re using physics.

And if think you’re using physics, by directly accessing transform.rotation you are bypassing the physics API an can reasonably expect glitching by doing so. See below.

Also, you have a scaling variable already (the one you call “Sensivity” above)… make it smaller if the final scaled result is too large.

---

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.

This means you may not change transform.position, transform.rotation, you may not call transform.Translate(), transform.Rotate() or other such methods, and also transform.localScale is off limits. You also cannot set rigidbody.position or rigidbody.rotation directly. These ALL bypass physics.

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…

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.…

[derfetteboss]

Hi, thanks for the VERY LONG RESPONSE!
i will put it in Update() later (I thought it wouldnt make a difference (hopefully it will))

[derfetteboss]

Thanks, Update() and times Time.deltaTime helped.

@Kurt-Dekker

Luckily it isn’t necessary to guess. You can debug!

I used print(…) which is the same, i said i think because i wasnt sure if it was .125 or .175, but Input.GetAxisRaw(“Mouse X”) was .05 when moving one pixel to the right