Player can walk through walls

[jlorenzi]

(I’ve already posted this question on the XR forum but it doesn’t seem like anyone visits that one so I’m posting it again here)

So I’m making a VR game using the XR interaction toolkit but the continuous move provider will let the player glitch through a wall if he just walks in to it for long enough, even when I’ve increased the colliders to be huge, set the players rigid body to have continuous collision detection and googled everywhere looking for a fix.

Nothing besides the continuous move provider is moving my player, although I’m guessing the rigid body might be moving my player as well.

Here’s all the components on my player

[Kurt-Dekker]

I have no idea what those locomotion and movement components do above. Perhaps the VR/AR/XR group knows more if they are part of a common non-Unity library? I would start there.

Either way, if you want to investigate those movers, that’s likely where your problem is, and it is likely related to this:

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

[GuirieSanchez]

@Kurt-Dekker

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.

In my previous project, I was using Transform to move the player (2D sprite) with a rigid body 2D. It’s good to know that it is not recommended. I guess applying velocity should be fine.

[Kurt-Dekker]

@GuirieSanchez

I guess applying velocity should be fine.

That works, but is unrelated to setting position. You can replace transform position setting with MovePosition() calls for a simple one-to-one mapping between transform moving and proper physics.

[jlorenzi]

Thanks for the help guys but I fixed the issue by recording the players last position, then checking if the current position intersects with a wall, if so then move the player to the old position.