- Home /
rigidbody movePosition behaves very differently from 2017.1.0f3 to 2017.3.0f3
I have basic 3D movement that worked perfectly in 2017.1 and behaves completely erratically in 2017.3.
This is the code:
_rigidbody.MovePosition(_transform.position + direction * moveMagnitude * moveSpeed * Time.deltaTime);
direction - The current model's forward which changes as you move around. Hold stick to the left --> the model will rotate to the left and that will become the new forward.
moveMagnitude - Range between 0-1 of how much input we are getting. This is a calculation on the axis input. When all the way in a direction this is usually 1.
moveSpeed - This is usually constant. Say 10 for walk and 20 for run.
Now I have perfectly good smooth movement in 2017.1. I upgraded to 2017.3 and movement is all over the place. You hold up and you get a bit of movement, then it stops, and then it moves a bit more, and then it stops, and then it continues to move normally. If you change direction it will stop and only sometimes move. It's hard to explain how erratic it is so here are gifs:
From 2017.1:
From 2017.3:
In the first gif everything is moving just fine. In the second please note I am constantly holding the movement down, it is simply not responding. When you see the box rotating - it is suppose to be moving in that direction but nothing is happening, and then sometimes it jitters forward and then moves, but not always.
I'm wondering what happened to the physics system to enact such a drastic change and what the hell is happening in 2017.3.
Your answer
Follow this Question
Related Questions
[Physics] Compensating for Moving/Rotating Terrain 0 Answers
Use MoveRotation to Look At Another Object 0 Answers
Player getting stuck in ground (3D) player has Rigidbody, and Box Collider, world is Mesh Colliders 0 Answers
Physic Torque Hinge joint problem 0 Answers
collision with floor fails when jumping,Player falls through floor 3 Answers