#Collision not detecting
fickle trail
Show me the floor's inspector too.
I want to see if you have done anything different.
proud prism
here are screenshots of the walls inspector and player's inpector#💻┃code-beginner message
fickle trail
since it seems like you aren't falling through the floor
That includes the wall's inspector. I want to see the floor.
proud prism
a video of what's happening: https://streamable.com/vuubmi
the whole prefab's screenshot for context
fickle trail
Is the floor non-uniformly scaled?
Primitive colliders behave weirdly if they are rotated while parented to something with non-uniform scale.
an example
faint rapids
I'm more interested to see what the green box looks like when they select the wall
fickle trail
indeed
proud prism
Is the floor non-uniformly scaled?
huh im not sure honestly, i dont really know what uniformly-scaled exactly is
fickle trail
the whole prefab's screenshot for context
See how the Scale up here is 1, 1, 1.3 ?
That's non-uniform scaling.
Click on "GroundTile" and show me its scale.
proud prism
I'm more interested to see what the green box looks like when they select the wa...
it fits the wall perfectly, we had alreayd discussed it
fickle trail
ah, okay, I thought I saw this mentioned earlier
faint rapids
ah, didnt see it in the thread
proud prism
oh wow, yeah, huh, should it have the 1 1 1.3 scale as well?
fickle trail
oh wow, yeah, huh, should it have the 1 1 1.3 scale as well?
No. It is non-uniform, though, so it could cause colliders to skew a little.
proud prism
ah, didnt see it in the thread
yeah no sorry did not paste it here but the walls and wall colliders fit perfectly
fickle trail
But you said that selecting the wall shows that the box wireframe matches the mesh
this makes sense if it's rotated at some multiple of 90 degrees
fickle trail
Skewing happens if you are rotated so that your axes don't line up with the parent's axes
proud prism
wait so the problem could be in rotation?
faint rapids
rb.MovePosition ignores collisions doens't it?
fickle trail
does it? i was unsure about that
faint rapids
yea because you're moving it to a position
faint rapids
if you set the velocity it would most likely work
i'm not 100% sure on the move position thing
fickle trail
I'm pretty sure MovePosition respects collisions as long as you have "is kinematic" unchecked...
proud prism
I'm pretty sure MovePosition respects collisions as long as you have "is kinemat...
it is unchecked
proud prism
if you set the velocity it would most likely work
rb.velocity.Set() ?
faint rapids
then perhaps it's because they're constantly moving it to the position so it ignores it?
I know i've had problems with it in the past and generally just set the velocity nowdays
fickle trail
i will go test this.
fickle trail
rb.velocity.Set() ?
no, literally just rb.velocity = ...
proud prism
it says it accepts pn;y Vector3 values, but im not sure which ones to set there...
the player's position?
fickle trail
I'm pretty sure MovePosition respects collisions as long as you have "is kinemat...
tested. works fine.
this cube is firmly respecting the wall collider
faint rapids
interesting. Well, I've had issues with it myself so thought it would be worth testing
fickle trail
it says it accepts pn;y Vector3 values, but im not sure which ones to set there....
you would tell it how fast you want to go
proud prism
ðŸ˜
fickle trail
so, basically just calculate forward and horizontal speed without deltaTime and plug those in
proud prism
so, basically just calculate forward and horizontal speed without deltaTime and ...
why without the delta time though?
fickle trail
because you want a velocity
multiplying by delta time tells you how far you'd go in one frame
faint rapids
also do Vector3.ClampMagnitude probably if ur adding and not setting.
faint rapids
this cube is firmly respecting the wall collider
100% rb.MovePosition is making it rest against the wall like that??
fickle trail
the forward speed is unrelated to the player's input
fickle trail
100% rb.MovePosition is making it rest against the wall like that??
yes.
if I freeze rotation, then it still works fine
faint rapids
as in in an update loop pushing it that direction
fickle trail
I did it in FixedUpdate.
stray cradle
100% rb.MovePosition is making it rest against the wall like that??
MovePosition does respect collisions
But it can cause issues if too fast and the rb isn't set right
fickle trail
it's bumping into a mesh collider
faint rapids
Interpolation wouldn't affect MovePosition, would it?
fickle trail
It shouldn't change the actual physical behavior
fickle trail
i would sanity check this by trying to move the player into the floor
and seeing what happens
proud prism
i would sanity check this by trying to move the player into the floor
you mean move it down on the Z axis?
proud prism
oh sorry, i have blender in mind
aahh im sorry ive google about velocity but im still confused what to write for the rb.velocity
i get that it has to have vector3
proud prism
okay so the player goes through the floor as well when i move her down... means the problem resides with player?