Player getting stuck in procedural Mesh

[HibsStatement]

Lately I have tried to implement naive meshing, which is an algorithm that produces terrain similar to minecraft (cubes).

When the player starts jumping around the terrain, there is a chance it might get stuck in the terrain between a floor and a wall.

The entire mesh is a single meshCollider, and the player is a regular Capsule object with a capsule collider.

Does anyone know how this might be possible? Is there a chance there is a gap in the mesh collider, or is it something with the regular capsule collider that results in this issue?

[Kurt-Dekker]

Some possibilities:

• You’re spawning the player inside the mesh

• You’re building the mesh around the player

• you’re moving the player so much he fully penetrates a collider, making it impossible for the physics to resolve. You might try continuous collision checking instead of discrete (setting on Rigidbody)

• you’re moving the player incorrectly: 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…

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

[HibsStatement]

Thank you for pointing out these issues.

For the first 2, they are not the case.

changing the collision detection on the rigidbody on the player model from discrete to any other setting did not solve the issue.

Currently, while jumping, the player gets moved with rigidbody.AddForce(). when moving, the player gets moved with gameObject,transform.Translate(). When i change the movement to rigidbody.MovePosition(), the problem still occurs.